List rulesCompleting the Create, Save As, or Specialization form

You are here: Reference > Rule types > Lists > List rules - Completing the New or Save As form

List rules Completing the Create, Save As, or Specialization form
About New Fields History More...

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 using the following Developer Help topics:

Completing the Create form Designer Studio – Completing the Create form
Completing the Save As form Completing the Save As form
Completing the Specialization form Completing the Specialization form

This help topic help topic identifies the key parts and options that are applicable to the record type you are creating.

Create a list rule by selecting List from the Technical category.

Key parts:

A list rule has two key parts:

Field

Description

Apply to

Select a class that this list rule applies to. Choose:

A concrete class to report only on instances of that class, stored as rows in a database table.
An abstract class that is parent of concrete classes, to define a rule that at run time can retrieve instances of a single class that is derived from the abstract class.
A concrete class that corresponds to a view of the PegaRULES database, to report on the rows of that view.

Identifier

Enter a list name that is a Java identifier. Begin the name with a letter, and use only letters, numbers, and hyphens. See How to enter a Java identifier.

Rule resolution

When searching for rules of this type, the system:

Filters candidate rules based on a requestor's ruleset list of rulesets and versions
Searches through ancestor classes in the class hierarchy for candidates when no matching rule is found in the starting class

Time-qualified and circumstance-qualified rule resolution features are not available for this rule type.

Related information

Open topic with navigation