Navigation rules -
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 new Navigation rule by selecting
Navigation
from the
User Interface
category.
Key parts:
A Navigation rule has three key parts:
| Field | Description |
| Apply to | Select the class to which this Navigation rule applies. |
| Identifier | Choose a unique name that indicates the purpose of the rule. Begin the name with a letter and use only letters, numbers, and a hyphen. |
| Type | The Type field appears if your RuleSet list contains the
Pega-Mobile ruleset. The type is used as an indicator for display
of fields specific to mobile devices. If your application will be accessed by standard
and mobile devices, create a navigation rule for each and specify the correct
navigation rule in the appropriate portal. Select:
|
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
- About Navigation rules
Use a Navigation rule to construct a multi-level XML document to be used in navigation and context menus.
Previous topic Hierarchy rules Next topic Modal dialog box