Ruleset list is formed
Hello,How a user’s ruleset list is formed ( the logic ).
Thanks
Rajesh
Updated: 9 Jul 2024 1:35 EDT
Eclatprime Digital Private Limited
IN
The ruleset list, also known as the ruleset stack, determines which rules are available to a Pega application during runtime. Application Ruleset: This is the main ruleset referenced on the application form itself.
Built-in Applications: Pega has built-in applications like PegaRULES that provide core functionalities.
Personal Ruleset (Optional): If the operator has checked out rules, their personal ruleset gets included.
Access Group: The operator's access group might also reference a versioned application rule that contributes to the list.
Formation Process: PegaRULES Foundation: When an operator logs in, Pega starts by adding the PegaRULES application's ruleset list to the foundation.
Built-in Applications Stack: Pega then iterates through all built-in applications, including the application referenced by the access group (if applicable). For each application, its associated ruleset is added on top of the existing list. Imagine stacking building blocks, with PegaRULES at the bottom.
Personal Ruleset (Optional): If the operator has checked out rules, their personal ruleset containing those checked-out rules gets placed on the very top of the stack.
For more information use this link: https://academy.pega.com/topic/ruleset-list/v3
Regards,
Sai G
Updated: 9 Jul 2024 7:12 EDT
Eclatprime Digital Private Limited
AU
In Pega, a user's ruleset list defines the order and priority of rule resolution when the system searches for a specific rule instance that matches a given circumstance. Here's how a user's ruleset list is typically formed:
1. **Access Group Ruleset List**: The primary source of a user's ruleset list is their assigned access group. An access group in Pega specifies which rulesets and versions are available to the user. When a user logs in, Pega determines the effective ruleset list based on the access groups assigned to the user.
2. **Inheritance**: Users inherit their ruleset list primarily from the access group they are assigned to. This means that the ruleset list defined in the access group is directly applied to the user, unless overridden by specific user settings.
3. **User-Specific Overrides**: In some cases, users may have ruleset lists configured specifically for them, either through direct configuration or through their operator record settings. This allows for customization of ruleset lists for individual users independent of their access group settings.
4. **Rule Resolution**: When a rule is requested during runtime (for example, a section, activity, or data transform), Pega uses the ruleset list of the user to determine which ruleset versions to search for the specific rule. The search follows a specific order (usually from top to bottom in the ruleset list), and the first matching rule instance found is used.
In Pega, a user's ruleset list defines the order and priority of rule resolution when the system searches for a specific rule instance that matches a given circumstance. Here's how a user's ruleset list is typically formed:
1. **Access Group Ruleset List**: The primary source of a user's ruleset list is their assigned access group. An access group in Pega specifies which rulesets and versions are available to the user. When a user logs in, Pega determines the effective ruleset list based on the access groups assigned to the user.
2. **Inheritance**: Users inherit their ruleset list primarily from the access group they are assigned to. This means that the ruleset list defined in the access group is directly applied to the user, unless overridden by specific user settings.
3. **User-Specific Overrides**: In some cases, users may have ruleset lists configured specifically for them, either through direct configuration or through their operator record settings. This allows for customization of ruleset lists for individual users independent of their access group settings.
4. **Rule Resolution**: When a rule is requested during runtime (for example, a section, activity, or data transform), Pega uses the ruleset list of the user to determine which ruleset versions to search for the specific rule. The search follows a specific order (usually from top to bottom in the ruleset list), and the first matching rule instance found is used.
5. **Dynamic Changes**: Changes to a user's ruleset list can occur dynamically based on changes to their access group assignments or specific user settings. Pega ensures that these changes are reflected in real-time to maintain consistency in rule resolution across the application.
In summary, a user's ruleset list in Pega is formed primarily through their assigned access group, with potential overrides or customizations at the user level. This structure ensures that users have access to the appropriate rulesets and versions needed for their work while maintaining flexibility for customization when required.