Defining the security of a ruleset

Complete the Security tab on the Ruleset form to update security information for a ruleset. For example, you can control who can change rules in a ruleset, and prevent potential conflicts when two or more users attempt to change one rule at the same time.

1. In the Records explorer of Dev Studio, click SysAdmin > RuleSet, and click a rule to open it.
2. Click the Security tab.
3. If you defined a password that a user must match to update the ruleset, in the Enter password values section, in the To update this RuleSet field, enter the password to unlock the ruleset.
4. To indicate that this ruleset contains rules that tailor, override, and extend an application, rather than define an application, in the Rule management section, complete the following fields:
   1. To specify that a ruleset is not intended to be moved to other Pega Platform systems, select Local customization?.
      This setting is advisory only and does not affect the ruleset functionality.

      Note: If you select this option, do not select Use check-out?.
   2. To enable developers to check out this ruleset when updating it, select Use check-out?.
      As a best practice, select this option to avoid the risk of multiple developers updating a ruleset and overwriting each other's changes.
   3. Optional: To use a flow rule to manage development and check-in on this ruleset, in the Work class used for approval process field, enter the work type to which the flow rule that controls check-ins applies.
      Note: Leave this field blank if you did not select Use check-out? in step 4.b. The Work class used for approval process field supports advanced rule management features, which are 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 rule is checked in.

      For more information about checking in rulesets, see Configuring the rule check-in approval process.
   4. Optional: In the Work flow to use for approvals field, enter the name of the flow rule that controls rule check-in for this ruleset.
      Note: Leave this field blank if you did not select Use check-out? in step 4.b. The Work flow to use for approvals field supports advanced rule management features, which are 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 rule is checked in.
5. Optional: Use the Define passwords section to prohibit users from adding or updating versions of this ruleset, or updating this ruleset.
   Lock the setting by entering passwords in the following fields. When you save the rule, the field is replaced by a check box. If you leave a field blank, no password is required.
   1. In the To Add a Ruleset Version field, enter a password that the user must match before creating (beneath the version array) or copying a version for this ruleset on the Versions tab.
   2. In the To Update a Ruleset Version field, enter a password that the user must match before updating a version on the Versions tab.
   3. In the To Update this Ruleset field, enter a password that a user must match when updating this ruleset. This restriction includes updates to the versions on the Versions tab.
      Note: To unlock the To Add a Ruleset Version and To Update a Ruleset Version settings, clear the check box and save the rule.

      To unlock the To Update this Ruleset setting, clear the check box, enter the password in the To Update this Ruleset Name field, and save the rule. Lock this setting to prevent changes to the To Add a Ruleset Version or To Update a Ruleset Version settings.

6. Click Save.