Records can be created in various ways. You can add a new record to your application or copy an existing one. You can specialize existing rules by creating a copy in a specific ruleset, against a different class or (in some cases) with a set of circumstance definitions. You may copy data instances but they 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
Create an agents rule by selecting Agents
from the SysAdmin
category.
An agents rule has a two-part key:
Field |
Description |
RulesetName |
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. |
RulesetVersion |
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 |
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.