Rebasing rules to obtain latest versions

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

Note: 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 Branch merging.

The following prerequisites must be met so that you can rebase rules:

To rebase rules, complete the following steps:

  1. In the Dev Studio click the name of your application, and then click Definition.
  2. On the Definition tab click Get latest ruleset versions.
  3. From the Select repository list, select the repository from which to retrieve rules to see a list of ruleset versions that will be rebased.
  4. 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 5.
  5. 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 a file using the Import wizard.
    3. In the wizard, specify whether you want to use the older version of the ruleset or overwrite the older version with the newer version.
    4. After all conflicts are resolved, restart the rebase process by starting from step 1.