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 a service-level agreement by selecting Service-level agreement from the Process category.
A service-level agreement has two key parts:
Field |
Description |
|
Apply to |
Select a class to which this service-level agreement applies, typically a subclass of the Work- base class or Assign- base class. The list of available class names depends on the ruleset you select. Each class can restrict applying rules to an explicit set of rulesets as specified on the Advanced tab of the class form. |
|
Identifier |
Enter a name for this service-level agreement. Begin the name with an alphabetic character, and use only alphanumeric and dash characters. You can override a standard service-level agreement in your application to fit the needs of your application. However, overriding, rather than choosing a distinct name in the Identifier field, may in some cases make it difficult to detect and debug whether the standard rule or the rule you created is executing. For example, if you override the standard rule Work-.NotifyManager in your application RuleSet version Alpha:04-01-23 with a rule Alpha-Finance-Order.NotifyManager, the Pega-ProCom agent may nonetheless execute the standard rule rather than your rule as desired, unless this agent has an appropriate access group that provides access to Alpha:04-01-23. |
Choose both key parts of a service-level agreement carefully, especially on PRPC systems hosting multiple applications. Normally, the Pega-ProCom agent evaluates service-level agreements. This agent typically has access to RuleSets from all applications on the entire system.
When two service-level agreements in different RuleSets are both named Delta-Work-Object-.Platinum (for example), the Pega-ProCom agent finds and executes onlyone of the two, the one that appears in the RuleSet that is higher on the agent's RuleSet list.
When searching for instances of this rule type, the system uses full rule resolution which: