The Check In feature lets a team of application developers work on an application (associated with a RuleSet Name) without interfering with or overwriting each other's efforts. Only one developer can have a specific rule checked out at any one time.
On the toolbar, the check in button () identifies the check in operation. (This button is
visible only when check in is possible for the currently displayed rule
instance.)
The Use checkout? checkbox on a RuleSet Name rule determines whether the check out/check in feature applies to that RuleSet.
To update a rule instance that belongs to such a RuleSet:
CTRL
+ ALT
+ C
to check out the
rule instance into your private RuleSet. The system marks the so that
no one else can check it out.To view all recently-checked in rules, select > Application > Development > Recent Actions. BYRNB 2/16/10
If the Project Management interface is enabled for this
application, a dialog box displays when you click . For the project ID that defaults in the display:
When checked in, the Project Explorer displays a link to this rule under the Task Group referenced by the task or bug item you select making it easy to find rules worked on as a part of the task or bug fix. Updates and effort hours are recorded in corresponding task or bug in the Project Management Framework. If the task or bug is marked complete, the item is resolved.
See About the
Project Explorer and the project management interface and the Pega Developer Network article Tracking development activity in a project.
The standard activity
Rule-.SetApprovalDependency contains no steps; it is an
extension point activity. To customize check-in, override this empty
activity with an activity in your application.