Changing the scope of rules
Adjust your application to your specific business needs by changing scope of rules. For example, you can move a rule to another ruleset or class, so that you can reuse the rule in a different part of your application.
- Moving rules
When a rule is moved, all of the old instances are automatically removed from the system, including their references and indexes.
- Setting rule status and availability
Set rule status and availability to elaborate on the usage information that you provide, and ensure that users interact with the correct version of your rule at run time. By setting rule status and availability, you also define application behavior during rule resolution, and how users can interact with rules at design time. As a result, you ensure that your application works correctly even if users apply extensions and make modifications.
- Creating a rule specialized by circumstance
Create a rule specialized by circumstance to provide a variant of the rule that your application triggers only conditionally under specified conditions. By creating specialized or circumstance rules, you address dynamic business requirements without changing the core logic of your application.
- Creating a rule specialized by a class or ruleset
Provide a version of a rule that your application triggers only during resolution of rules that belong to a specified class or ruleset. When you define the conditions for a rule resolution, you ensure that users interact with actions and the application behavior that are relevant in a given scenario. You also save time and resources because you promote reuse across your application.
- Defining the input parameters of a rule
Control the type of information that users can pass to a rule by defining input parameters. By referencing these input parameters in your rule logic, you can use run-time data to make decisions.
- Defining the pages and classes of a rule
Many types of rules can access or update information on various clipboard pages when they run. Most of these rule types include a Pages & Classes tab that you can use to provide important information about what your clipboard pages will look like during execution.
- Rule skimming for higher ruleset versions
Skimming is an operation of copying rules from your rulesets into a ruleset of a higher version. Skimming improves the performance of your application because the system filters out rules that are unavailable for rule resolution. Because the new ruleset contains only the highest rule versions, skimming simplifies rule resolution and minimizes the rule data that you ship to a different version of your application.
- Adding a custom field
Associating custom fields with rules provides a flexible way to supplement your application with metadata, such as a change order number or log file attachment.
Previous topic Using pattern inheritance for rule resolution Next topic Moving rules