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 the rule:
Note: Checking in a private edit to a branch could result in loss of work if another user checks in changes to the same rule. You receive a warning message if your check-in might result in lost work.
- 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.
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:
- 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.
- Checking out a rule to a branch
You can check out a rule to a branch so that you can make changes to a rule and then save it in the branch ruleset.
- Checking out a rule
To avoid accidental rule changes or conflicts that might result from multiple developers working on the same rule, perform a check out, so that you can lock the rule and safely make changes to it. By checking a rule out before editing, you avoid unwanted rule changes, and as a result save time and maintain a better quality application.