Rebase rules on your development system to obtain the most recently committed rules from the system of record (SOR). Rebasing allows development teams working in separate development environments to share their changes and keep their local rule bases synchronized. Having the most recently committed rules on your development system decreases the probability of conflicts with other development teams.
The following prerequisites must be met so that you can rebase rules:
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.
In the Designer Studio click the name of your application, and then click Definition.
On the Definition tab click Get latest ruleset versions.
From the Select repository list, select the repository from which to retrieve rules to see a list of ruleset versions that will be rebased.
Click Rebase.
Optional: 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:
For each ruleset, click the Download Archive link and save the .zip file.
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 by using the Import wizard.
In the wizard, specify whether you want to use the older version of the ruleset or overwrite the older version with the newer version that is on the SOR.
After all conflicts are resolved, restart the rebase process by starting from step 1.