RuleSet form
Completing the Security tab

Field

Description

Optional. Enter a password that a user must match before creating any additional RuleSet versions in this RuleSet. If this field is blank, no password is required.

Optional. Enter a password that a user must match before updating any RuleSet version in this RuleSet. If this field is blank, no password is required. When updating a RuleSet version, users must enter a value that matches this value in the To Add/Update this Version field on the Security tab of the Version form.

Optional. Enter a password that a user must match in the Enter Password Values area below when updating this RuleSet Name rule, including any of the passwords. If this field is blank, no password is required.

To update this RuleSet Name rule, a user enters the same password in this field as the one you specify in the field of the same name in the Define Passwords section above.

Users only enter the password in this field when they want to update an existing RuleSet Name rule. Therefore, don't enter a value in this field when first creating the RuleSet Name rule.

Select to record your intent that this RuleSet contains rules that tailor, override, and extend an application, rather than define an application. A local customization RuleSet is one not intended to be moved to other Process Commander systems. This is advisory only, this field has no functional effects.

If you select this box, do not select Use check-out?.

Don't confuse local customization RuleSets, defined by this box, with localization or language-specific RuleSets, which support language-specific text.

Select to enable rule management facilities for this RuleSet. The Check in () and Check out () buttons appear on the toolbar for rules in a RuleSet that is subject to rules management. The Save button does not appear until the rule is checked out.

To save a rule, users who have the Allow rule check out? box selected in the Advanced tab of their Operator ID data instances) can check the rule out, make changes, save the rule, and, when finished with the rule, check it in. Checking the rule in saves the rule, but you can also use Save independently before you check in the rule.

Clear this box if this RuleSet is not to use the rule management facility. For such RuleSets, if developers modify a rule, the Save button appears on the toolbar. See How to use the developer toolbar.

When check-out is enabled, the system saves the entire previous rule each time you check in a new one, supporting the Restore () operation. See How to restore the earlier state of a rule.

You can't clear (deselect) this check box if anyone has one or more rules checked out from any version. Select View > Rules > Checkouts by RuleSet Version to see which rules are checked out.

As a best practice — even for a RuleSet to be used only by yourself or by a small development team — select this check box. When a team of developers together work on a RuleSet that does not use checkout, rules are not locked as they are updated, so a risk of simultaneous updates exists; one user's changes may be overwritten. In addition, when checkout is not used, updated rules take effect immediately after a Save operation, which can be disruptive to other developers on a team, However, leave this box cleared for a RuleSet for Local customization, or one that is to contain only rules delegated to application users.

Rules in an override RuleSet can't be checked out. Leave this box unselected.

Optional. Leave these two fields blank if the Use check-out? box is not selected. They support advanced rule management features, useful when a large development team is involved or when a development leader wants to review each change made by others on the development team before the changed rule is checked in.

To use a flow rule to manage development and check-in on this RuleSet, enter the work type to which the flow rule that controls check-ins applies. The standard work type named Work-RuleCheckIn is designed to support this process. See Using the Rule Check-in approval process.

Optional. Enter the name of the flow rule that is to control rule check-in for this RuleSet. A standard flow rule named ApproveRuleChanges is the default. See Using the Rule Check-in approval process. Click the pencil icon ( ) to review or edit the flow.