|
![]() |
A circumstance definition rule has three key parts.
To create a Circumstance
Definition rule, access the PegaRULES database with a database
account that has specific grants (capabilities). These grants
may not be available to all users. They can be provided by a DB
Admin account, which can be identified on the Database tab of the Database Name instance for
the PegaRULES database or in the
prconfig.xml
file. See
Database Name form — Completing the Database tab.
If you do not have these database grants, a warning appears when you save the Circumstance Definition rule. The Circumstance Definition rule saves correctly, but you may not be able to define a report on rules with this circumstance (such as the View > Rule > Find by Circumstance report). .
Field |
Description |
Type |
Select |
Applies to Class |
|
Template Name |
|
Purpose |
Enter a unique name for this rule within this class, beginning with a letter and using only alphanumeric, underscore, and dash characters. |
The definition rule is class-based and rule-resolved. It cannot be qualified by circumstances or date ranges.
When performing a Save As using the
same Applies to Class and Template
Name, the new and the original instances will, by
default, have identical properties and values in the
Apply this Definition table in the
Definition tab on the rule form.
This creates conflict errors that prevent the new instance from
being saved. Change the property values in either form to
successfully save the new rule.
For general information about the New form, see Completing the new rule dialog box. For general information on the Save As form, see How to enter rule keys using Save As.
For information on how circumstance template and
circumstance definition rules are used in multivariate
circumstancing, see the Pega Developer Network article
PRKB-25272 How multivariate circumstancing works.