To ensure that your application meets the unique needs of your customers, you can modify a rule that is unavailable for regular checkout by performing a private edit. Check out rules as private edits to edit rules that belong to locked rulesets.
Private edits are useful for quick debugging without interrupting other team members, because during a private edit other system architects can edit a rule at the same time.When you perform a private edit, you edit a rule in an isolated sandbox, in which you can make and then test your changes. As a result, you maintain a good quality application and avoid creating errors, because during a private edit the original ruleset that contains your rule remains unchanged.
-
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.
-
In the rule form, click Private edit.
-
In the dialog box that appears, click Continue with private edit.
The system saves a copy of the rule in your personal ruleset. Rules in your personal ruleset do not affect other users’ run-time experiences, or the actions that they can perform on this rule.
-
Edit the rule.
-
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.
- Project Management Framework (PMF)
Integration with PMF is deprecated. You can set up integration with another project management tool, such as Pega Agile Studio, from the Application rule form.
- Checking out a rule to a branch
You can check out a rule to a branch so that you can make changes to a rule and then save it in the branch ruleset.