Check out Check outThe check-out feature lets a team of application developers work on an application (associated with a RuleSet Name) without interfering with or overwriting each other's work. A rule can be checked out to only one developer at a time.
Check-out is optional feature controlled by two check boxes:
A developer can check out a rule only if both boxes are selected.
At the top right of a rule form, a padlock image (
) indicates that a rule
is checked out.
When check-out is possible for a rule, the Check Out button
(
) appears on the toolbar. This button does not
appear if the rule belongs to one of the few types that
don't support check-out, or if the rule is already checked
out to you or to another developer.
To check out the current rule, click the toolbar Check Out
button (or type the keyboard shortcut CTRL +
ALT + C).
Use the
Checked-out button (
) on the Find area or select
View > Rules > Checked Out By Me to quickly
see a list of rules checked out to you. To list all the
rules checked-out by anyone, select View > Rules >
All Checkouts.
To report
on checked-out rules, create a list view or summary view rule
with Data-Rule-Locking as the Applies
To class. Create this rule using the List View or
Summary View rule form; you can't use the Report wizard for
this.
For best
performance on a production system, minimize the number of
distinct users who can check out rules. Even when a
personal RuleSet is empty — the operator has not
checked out any rules — each user who has this
capability has a unique, distinct RuleSet list. As a result,
Process Commander assembles and compiles each rule this user
executes (upon first use only). Such rules assembly and
compilation requires CPU resources, database access, and memory
in the rules assembly cache.
Rules in an
override RuleSet can't be checked out.
 | override RuleSet, rule management facility, check in, private RuleSet |
 | Working
with checkout and your private RuleSet Working with the Checked Out by Me report |
Definitions
— C