To make your changes available to your development team after you check out and edit a rule, check in the rule. When you check in edited or updated rules, you contribute to the efficient development of your application and avoid errors that might occur when other developers work on the same rule.
- In the navigation pane of Dev Studio, click Records, expand the category that contains the rule that you want to check in, and then click the rule.
- In the header of the form, click Check in.
- If you perform a check in after a private edit, in the Check In
window, in the Destination section, specify where you want to save
- To save a rule to an unlocked ruleset, select Ruleset, and then specify a ruleset and a ruleset version.
- To save a rule to a branch, select Branch, and then specify the branch.
- In the Check-in comments field, enter a comment that describes your changes to the rule.
- Optional: To override the default work item that your application
associates with this development change, press the Down arrow key in the Work
item to associate field, and then select a work item.For more information about your default work item, see Setting your current work item.
- Click Check in.
- Configuring the rule check-in approval process
To turn on controlled check-in for a ruleset, complete the following tasks:
- Rule check-in process
The optional rule checkin facility allows you to use a Pega Platform flow rule to manage change to your application. Use this facility to coordinate the efforts of large development teams or to control changes to sensitive applications.
- Checking in rules in bulk
Save time and improve your management of the rules that you edit in your application by performing a bulk check-in. When you perform bulk actions, you can view all of the rules that are currently checked out in your application, and then you can check in several rules at once.