About RuleSet rules
About  New  Versions  Security  Category  History  More...

Purpose

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 Express; 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.

Access

Use the Records Explorer to list all RuleSet rules in your system.

Development

When you create a new RuleSet, you also create a RuleSet version; the default is 01-01-01

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, checkout, delegated rules, personal RuleSet
	About RuleSet Versions Application Structure landing page

Atlas — Standard RuleSets

SysAdmin category
Help Home