Rebasing rules to obtain latest versions

If you are using a continuous integration and continuous delivery (CI/CD) pipeline with Deployment Manager or third-party tools such as Jenkins, after you merge branches on a remote development system, you can rebase your development application to obtain the most recently committed rulesets through Pega repositories.

Before you begin: You must have the pxCanRebase privilege so that you can rebase rules. This privilege is associated with the sysadmin4 role. If you do not have this privilege, you can add it to your role. For more information, see Specifying privileges for an Access of Role to Object rule.
To rebase rules, you must merge branches to make changes to rules. Changes made to rules in an unlocked ruleset version will not be visible by the rebase functionality. For more information about merging branches, see one of the following documents:

To rebase rules, complete the following steps:

  1. If you are using Pega repositories with third-party automation servers such as Jenkins, ensure that the Pega repository type is enabled. You do not need to enable Pega repositories if you are using Deployment Manager. For more information, see Enabling the Pega repository type.
  2. Ensure that you have a connection to a Pega type repository that supports ruleset version artifacts. For more information, see Creating a repository connection.
  3. Enable ruleset versions for Pega repositories by configuring the HostedRulesetsList dynamic system setting on the system of record. For more information, see Enabling ruleset versions for Pega repositories for rebasing.
  4. In Dev Studio click the name of your application, and then click Definition.
  5. On the Definition tab, click Get latest ruleset versions.
  6. From the Select repository list, select the repository from which to retrieve rules to see a list of ruleset versions that will be rebased.
  7. Click Rebase.
    • If there are no import conflicts, your development application is refreshed with the rules.
    • If there are import conflicts, the system displays them. For example, a conflict can occur if you made a change to the same ruleset version on your local development system or if you modified a non-resolved rule in the ruleset, such as the Application record. To resolve a conflict, complete step 8.
  8. If you have conflicts, you must resolve them before rebasing continues, either by overwriting or rejecting the changes on your development system. Complete the following steps to import the ruleset and either overwrite or reject the changes that you made to the ruleset on the development system:
    1. For each ruleset, click the Download Archive link and save the .zip file.
    2. Click the Click here to launch the Import wizard link at the top of the Rebase rule form to open the Import wizard, which you use to import the .zip files. For more information, see Importing rules and data from a product rule by using the Import wizard.
    3. In the wizard, specify whether to use the older version of the ruleset or overwrite the older version with the newer version.
    4. After you resolve all conflicts, restart the rebase process by starting from step 1.