Performing a private edit
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.
- Ensure that you have the pxAllowPrivateCheckout privilege, which is typically granted through a role on your access group. The standard access role PegaRULES:SysAdm4 provides this privilege.
- Ensure that the rule is not available for regular checkout, usually because the rule is already checked out to another user or because its ruleset version is locked.
- Ensure that the rule belongs to a ruleset that has the checkouts enabled.
- Ensure that your Operator ID is allowed to check out rules. For more information, see Defining security information for an operator.
- 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.
Previous topic Standard rule checkout Next topic Checking out a rule to a branch