|
|
About RuleSet rulesPurpose
Create a RuleSet to identify, store, and manage the set of rules that define an application or a major portion of an application. Generally, you may need five to eight RuleSets per application. Typically, these are created as you use the Application Accelerator; you do not need to create them with the RuleSet form.
How you use RuleSets in your application has important design and deployment consequences. For large and complex applications, several RuleSet may be appropriate. Before you create a RuleSet, think carefully about the purpose, use, and dependencies of current RuleSets and the new RuleSet.
Select 
> Application > Structure to view a list of RuleSets in your application (including those your application is built on), and a list of prerequisites for each RuleSet.
In versions before V6.1, you used New RuleSet and New RuleSet Version forms to create RuleSet and version rules, respectively. Beginning with V6.1, you simultaneously create both rules in the New RuleSet Version form. You can create versions for a given RuleSet from the Versions tab.
Access
Use the Rules Explorer to list all RuleSet rules in your system.
Development
As a best practice, create the initial set of RuleSets you need using a wizard, such as the Application Accelerator.
When you create a new RuleSet, an initial RuleSet version 01-01-01 is also created.
After you create a RuleSet and version, enable developers to create and modify rules in the new RuleSet by referencing the new RuleSet version in an application rule and an access group that is available to yourself or to other users.
Category
RuleSet Name rules are part of the SysAdmin category. A RuleSet rule is an instance of the Rule-RuleSet-Name class.
|
check in, check out, delegated rules, personal RuleSet, rule management facility |
|
About RuleSet Versions Application Structure landing page |
|
Atlas — Standard RuleSets |
SysAdmin category
Help Home