|
|
Agents rulesRecords can be created in various ways. You can add a brand new record to your application or copy an existing one. Existing rules can be specialized by creating a copy into a specific ruleset, against a different class or (in some cases) with a set of circumstance definitions. Data instances may be copied but do not support specialization as they are not versioned.
Based on your use case, the Create, Save As or Specialization form is used to create the record. The number of fields and available options vary by record type. Start by familiarizing yourself with the generic layout of these forms and their common fields:
This help topic then identifies the key parts and options that are applicable to the record type you are creating.
Create an agents rule by selecting Agents from the SysAdmin category.
Key parts:
An agents rule has a two-part key:
Field |
Description |
| RuleSet Name |
Select the name of a RuleSet. Because the name of the RuleSet is the name of the agents rule, there can be only one agents rule per RuleSet. If necessary, you can create different versions of the agents rule in different RuleSet versions. NOTE: You cannot create an Agents rule in a personal RuleSet. Additionally, you cannot check out an Agents rule. |
| RuleSet Version |
Select a version of the RuleSet. Test each activity carefully before modifying an agent rule. Although you can save multiple versions of an agents rule, the internal Master Agent process always runs the highest-numbered version. This restriction means that an agents rule you create (with Availability set to |
Rule resolution
When searching for an Agents rule requested by a developer, the system filters candidate rules based on a requestor's RuleSet list of RuleSets and versions. However, the internal Master Agent process always runs the highest-numbered version, not rule resolution.
Circumstance-qualified and time-qualified resolution features are not available for agents rules.
About Agents rules