Skip to main content


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

Map Values

Updated on May 17, 2024

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 map value by selecting Map Value from the Decision category.

Key parts:

A map value has two key parts:

FieldDescription
Apply to Select a class that this map value applies to.

The list of available class names depends on the ruleset that you select. Each class can restrict applying rules to an explicit set of rulesets as specified on the Advanced tab of the class form.

Map value rules can apply to an embedded page. On the Map Value form, you can use the keywords Top and Parent in property references to navigate to pages above and outside the embedded page. If you use these keywords, include the class and absolute name — or a symbolic name using Top or Parent — on the Pages & Classes tab.

IdentifierEnter a name that is a valid 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 instances of this rule type, the system uses full rule resolution which:

  • 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
  • Finds circumstance-qualified rules that override base rules
  • Finds time-qualified rules that override base rules

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