Checking out a rule

To avoid accidental rule changes or conflicts that might result from multiple developers working on the same rule, perform a check out, so that you can lock the rule and safely make changes to it. By checking a rule out before editing, you avoid unwanted rule changes, and as a result save time and maintain a better quality application.

You can only check out rules that belong to an unlocked ruleset. If you want to edit a rule that belongs to a locked ruleset, perform a private edit. For more information, see Performing a private edit.
Note: When you make updates to your application in App Studio, Pega Platform automatically manages the check-in and checkout process.
  1. In the navigation pane of Dev Studio, click Records, expand the category that contains the rule that you want to edit, and then click the rule.
  2. In the header of the rule form, click Check out.
    Your application places a copy of the original or base rule in your personal ruleset. No other user can check out this rule until you check in your changes.
  3. Modify the rule as appropriate.
  4. Click Save.
    Your application saves your changes into the checked-out version of the rule. These changes are visible only to you. When you run rules in your application, they resolve to only your checked-out version.
What to do next: Make your changes available to other developers of your application by checking in the rules that you edit. For more information, see Checking in a rule.
Note: You do not have to check in your changes immediately. You can log out and return to a checked-out rule later or click Discard to remove the rule from your personal ruleset.