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:
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.