Rule management
facility Rule management
facilityProcess Commander applications can be developed by a small team working side-by-side, or by a large team who may be physically separated.
The optional rule management facility supports an application developer team by allowing multiple members of the team to evolve one application, in a coordinated way. It offers two levels of coordination:
This type of rule management takes effect for a RuleSet Name if a developer's Operator ID instance and the RuleSet-Name instance have an appropriate check box setting:
Like many source code control systems, this facility allows only one person to check out, work on, and modify a rule instance at a time.
If check out is in effect, application developers check out a rule before modifying it, and later check it in when finished modifying it. While a rule is checked out, other users and developers continue to see and execute the original version. Checking out a rule causes Process Commander to make a copy in the developer's private RuleSet.
Check-out does not apply to some rule types, even when the Use check out? box is selected:
The check-out feature described above lets each developer team member decide when a revised rule is tested enough to check in. No other developer can review or test the revised rule while it is checked out. Additionally, developers check in related rules in one by one; potentially some users could execute some the updated rules before other related rules are checked in.
For greater control over development, your team can create or identify a flow rule that applies to rule check in. This feature may be valuable to ensure that changes to the rules in a production system, in a sensitive development effort, or in any large or distributed team effort are properly controlled.
Often, developers modify two or more rules to support an application change. From the My Checked Out Rules report you can check in several rules in a single operation.
Definitions — R