Table of Contents

Rule development in branches


Only available versions of this content are shown in the dropdown

To add rules to branches, when you create a rule, you can select the branch where you want to save your rule. Branch rulesets are automatically created.

Working with rules in the branch ruleset is the same as in standard rulesets, except for the following differences:

  • Final rules – You can typically modify final rules only in the ruleset and class in which they are declared final. This limitation means you cannot normally copy final rules to another ruleset that either has the same Applies To class or is located within the subclass of the ruleset of the final rule. For branch rulesets that are branched from the originating ruleset of the final rule, this limitation is removed. You can check out a final rule from its original ruleset into a branch ruleset that is branched from the owning ruleset. For more information, see Checking out a rule to a branch.
  • Utility functions – Some function references in the system use the ruleset name as part of the reference. To allow for rules to appropriately reference functions that exist in rules in a branch ruleset, the system's function lookup considers the branches in your ruleset list when resolving the references.
  • Developing branches with libraries and functions

    Libraries hold custom functions for your application, which can supplant and extend standard functions. For example, the OperatorHasPrivilege function verifies that a user has a specific privilege.

Did you find this content helpful?

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.