How to export all the change from TEST to UAT
Hello-
I am looking for a way to export all the change have been made in one environment in past 7 days and package to Jar file to move to other environment.
What is the best way to accomplish that?
thanks all your advice ---
Incessant Technologies
AU
In the Data-Rule-Summary class, there is a List view report UpdatedRecentlyByMe, where you can filter out with the date range and respective operators to get the list of rules that got modified in Last 7 Days.
Then RAP and promote the code to the other environment.
Thanks
Sandeep P V
Frontier Communications
US
Hi Sandeep-
Are there a way we can export the list of Product Rule under RAP?
Larry-
Pegasystems Inc.
US
The following tool compares rulesets within two different environments:
Designer Studio >> System >> Refactor >> Rulesets >> Rulebase Compare
This approach relies on the remote environment being the reference as opposed to trying to analyze the local database for every rule modified in the past 7 days.
It is poor practice to move rules that are not contained in locked ruleset versions. If not careful, and deciding to move rules one-by-one regardless their version, you can easily get into a situation where the same rule with the same version exists but with an older timestamp within the rule's pzInsKey. The result is time wasted trying to determine why a downstream QA environment contains a bug that cannot be replicated in Dev.
Dealing with data changes is trickier since those records are not versioned. Recommend having a DBA assist.
The following tool compares rulesets within two different environments:
Designer Studio >> System >> Refactor >> Rulesets >> Rulebase Compare
This approach relies on the remote environment being the reference as opposed to trying to analyze the local database for every rule modified in the past 7 days.
It is poor practice to move rules that are not contained in locked ruleset versions. If not careful, and deciding to move rules one-by-one regardless their version, you can easily get into a situation where the same rule with the same version exists but with an older timestamp within the rule's pzInsKey. The result is time wasted trying to determine why a downstream QA environment contains a bug that cannot be replicated in Dev.
Dealing with data changes is trickier since those records are not versioned. Recommend having a DBA assist.
FYI: In newer and newer versions of Pega deployment will become more and more automated with its emphasis on DevOps support.
Pegasystems Inc.
US
More information on Dev Ops as of Pega 7.3.1: