Question
Self
IN
Last activity: 23 May 2024 3:08 EDT
application validation vs ruleset validation
Hi All, can you please explain me in detail what is the difference between application validation and ruleset validation
-
Reply
-
Share this page Facebook Twitter LinkedIn Email Copying... Copied!
Accepted Solution
Updated: 23 May 2024 3:08 EDT
Eclatprime Digital Private Limited
AU
while application validation focuses on the overall application's compliance with business requirements and standards, ruleset validation concentrates on ensuring the quality and consistency of individual rules within the application. Both types of validation are essential for maintaining a robust and reliable PEGA application.
Maantic Inc
IN
Application validation validates a ruleset only within the application context. When you configure a ruleset to use AV, Pega Platform determines which rules are valid to reference at design time without using ruleset prerequisites.
Ruleset validation validates a ruleset based on the prerequisites that you define in another ruleset.
Lantiqx Systems India Private Limited
IN
Application Validation: verifies the application ruleset stack and built in application and does not see for any ruleset prerequisites. Ruleset Validation: verifies the rulesets and its prerequisites. If the rule is not available in the ruleset, then it will show throw an error
Eclatprime Digital Private Limited
IN
Hi @EmmaW096,
Key differences:
- Scope of Validation: Application Validation checks rules against the whole application stack, whereas RuleSet Validation checks rules within the RuleSet and its declared dependencies.
- Dependency Management: Application Validation simplifies dependency management by using the entire application context, while RuleSet Validation requires explicit dependency declarations.
- Flexibility vs. Control: Application Validation offers more flexibility by allowing cross-RuleSet references within the application, whereas RuleSet Validation provides more control by enforcing stricter dependency management.
When to use:
- Use Application Validation when you want to validate rules in the context of the entire application, especially if the application has many interdependent RuleSets.
- Use RuleSet Validation when you are developing reusable RuleSets or components that need to be validated independently and possibly used across different applications.
Infosys Limited
IN
When an application validation mode defined for a ruleset, whatevr the rules that are present in that ruleset can acess the rules within the application rulesets (which can be either be configured with application validation mode or ruleset validation mode).
Lets say i have the flowaction rule in
Ruleset1: 01-01-01 which is configured with application validation mode in the current application and it can refer the section rule with in the application/ builton application ruleset which can be either configured with Application validation Mode or Ruleset validation mode.
Ruleset validation mode:
If any of the application configured with ruleset validation mode you have to define the prerequisite rulesets. Only the rules in the prerequisite rulesets can be accessed.
Lets say you define Aplha: 01-01-01 with beta:01-01-99 as the prerequisite. Only the rules in beta can be acccessed by aplha, NO OTHER RULES CAN BE ACCESSIBLE which means you can not access the rules in the other rulesets except the rules of the pre-requisite rulesets.
Lets say a flow action rule exists in the aplha:01-01-01, it can the section only from the beta ruleset. It can't acess the section from the other application rulesets.
Final point is rulesets configured with AV mode can access the rules in the rulesets configured with AV or RV mode if it is defined in the application ruleform.
When an application validation mode defined for a ruleset, whatevr the rules that are present in that ruleset can acess the rules within the application rulesets (which can be either be configured with application validation mode or ruleset validation mode).
Lets say i have the flowaction rule in
Ruleset1: 01-01-01 which is configured with application validation mode in the current application and it can refer the section rule with in the application/ builton application ruleset which can be either configured with Application validation Mode or Ruleset validation mode.
Ruleset validation mode:
If any of the application configured with ruleset validation mode you have to define the prerequisite rulesets. Only the rules in the prerequisite rulesets can be accessed.
Lets say you define Aplha: 01-01-01 with beta:01-01-99 as the prerequisite. Only the rules in beta can be acccessed by aplha, NO OTHER RULES CAN BE ACCESSIBLE which means you can not access the rules in the other rulesets except the rules of the pre-requisite rulesets.
Lets say a flow action rule exists in the aplha:01-01-01, it can the section only from the beta ruleset. It can't acess the section from the other application rulesets.
Final point is rulesets configured with AV mode can access the rules in the rulesets configured with AV or RV mode if it is defined in the application ruleform.
But rulests configured with RV mode can access the rules from prerequisite rulesets.
Generally, rulesets which can be shared with the applications within the organization can be configured with RV mode for example org rulesets
Accepted Solution
Updated: 23 May 2024 3:08 EDT
Eclatprime Digital Private Limited
AU
while application validation focuses on the overall application's compliance with business requirements and standards, ruleset validation concentrates on ensuring the quality and consistency of individual rules within the application. Both types of validation are essential for maintaining a robust and reliable PEGA application.