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.
- Creating a specialized or circumstance rule
You can create a specialized or circumstance rule to create a variant of the rule that can be triggered only conditionally. The created rule is resolved and active only when the specified conditions are met. Create specialized or circumstance rules to address dynamic business requirements without changing the core logic every time. For information about rule resolution exceptions and how they might affect circumstance rules, see .
- Defining the input parameters of a rule
You can define input parameters to control the type of information that users can pass to a rule. 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.
- Skim to create a higher version
Skimming creates rules for a major or minor RuleSet version by copying selected rules of lower numbered versions of the same RuleSet on the same Pega Platform system.
- 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.