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.
Before you begin: Check out, and then update a rule. For more information, see
Checking out a rule.
CAUTION:
Use
caution when you check in rules after you perform a private edit, because you may overwrite
changes from other developers. For more information about private check out, see
Performing a private edit.
-
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:
- 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.
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.
-
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.
-
Click Check in.
Result: If your edits do not require approval, your changes immediately
affect rule resolution and run-time behavior for all users.