Skip to main content

Creating library rules

Suggest edit
Updated on March 16, 2022

Completing the Create, Save As, or Specialization form

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.

Create a library rule in Dev Studio by clicking CreateTechnicalLibrary.

Key parts

A library rule has two key parts:

FieldDescription
Identifier Enter a name for this library. Begin the name with a letter and use only letters and digits. The name must be a valid Java identifier; see How to enter a Java identifier.
  • Do not choose a name that matches a standard library unless you intentionally plan to override functions in that standard library.
  • The library name Default is deprecated and should not be used.
Ruleset Name Select a ruleset name. A library is available to all versions of a ruleset. However, the functions in the library might differ from ruleset version to ruleset version. Note: You cannot create a new library rule in a branch ruleset.

Rule resolution

When searching for library rules, the system filters candidate rules based on a requestor's ruleset list of rulesets (but not versions).

Note: Time-qualified and circumstance-qualified rule resolution features are not available for library rules. The class hierarchy is not searched.

About Library rules

Did you find this content helpful? YesNo

Have a question? Get answers now.

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

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