Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Declare Index rules - Completing the New or Save As form

Updated on July 8, 2022

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 can copy data instances but they do not support specialization because they are not versioned.

Based on your use case, you use the Create, Save As, or Specialization form to create the record.

Create a Declare Index rule by selecting Declare Index from the SysAdmin category.

A Declare Index rule has two key parts:

FieldDescription
Apply to Select a concrete or abstract class that defines the scope of the indexes. At runtime, a clipboard page of this class must be a top-level page. Concrete objects in classes derived from this class are candidates for indexing under this rule.

Note these restrictions:

  • Choose an internal class. You can't index an external class.
  • You cannot use @baseclass or the Rule- base class, nor any class derived from the Rule- base class here. You cannot use a class derived from the Code- or Embed- class here.
  • You can choose a class derived from the Data- base class, but limitations apply. See More about Declare Index rules.
Identifier Enter a name for this Declare Index rule. Begin the name with a letter and use only letters, numbers, and a hyphen.

No other rules explicitly reference this Identifier value. However, based on class inheritance, a Declare Index rule named ByChild at one level in the class structure may override and therefore prevent execution of a Declare Index rule named ByChild at a higher level in the class structure.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us