Check in
Using the check-in feature, a team of application developers can work on the pieces of an application (associated with a RuleSet Name) without interfering with or overwriting each other's efforts.
Check in has two flavors:
- Standard check in — In standard check in, a developer has a checked-out rule, and checks in that rule to replace the original base rule.
- Private check in — Private check in is a special case of the standard check-in feature. When a developer has performed a private check out on a rule at an earlier point in time when the rule was unavailable for a standard check out (such as when another user has the rule checked out, or the rule is in a locked RuleSet version), the developer can check in that rule if the conditions that prevented a standard check out are no longer present, and if there is an unlocked RuleSet version or branch RuleSet into which to check in the rule. For example, if developer A checks out a rule, and developer B does a private check out of that rule, and developer A then deletes his checked-out rule, developer B has the opportunity to check in his private checked-out rule using the Private Check in button (
).
After you do a standard check out of a rule, the Check in button (
) appears in the toolbar when you open the rule form for that rule. To check in the rule, click .
After you do a private check out of a rule, the Private Check in button () appears on the toolbar, and you can click to check in the rule. If the base rule changed in the time between when you performed your private check out and clicking to check it in, the system displays a notification message to alert the developer of the risk of overwriting the base rule.
The Use checkout? checkbox on a RuleSet Name rule determines whether the check-out/check-in features apply to that RuleSet. A similar checkbox on the Security tab of the Operator ID form lets users use the check-out/check-in features. In addition to the two checkbox settings, to use the private check-out/check-in features, a developer needs the pxAllowPrivateCheckout privilege. This privilege is typically granted to a user by adding it to a role used in the user's access group. The standard access role PegaRULES:SysAdm4 provides this privilege.
See Understanding checkout and your personal RuleSet for a description of how to use the check-out/check-in features.
To view all recently checked-in rules, select 
> Application > Development > Recent Actions.
Definitions — C