Why Pega-ProcessCommander : 07-10-99 promoted as default/fallback prerequisite for RSV?
Hi Community Members,
I have seen in many post/articles we have promoted Pega-ProcessCommander : 07-10-99 to be used as default prerequisite for any rule-set in our app stack having Ruleset Validation as selected radio button.
When i opened Pega-ProcessCommander : 07-10-99, it does not have any rules, whereas Pega-ProcessCommander rule-set have UIKit related application rules. I am not able to understand the reason behind this kind of setup.
Hi Community Members,
I have seen in many post/articles we have promoted Pega-ProcessCommander : 07-10-99 to be used as default prerequisite for any rule-set in our app stack having Ruleset Validation as selected radio button.
When i opened Pega-ProcessCommander : 07-10-99, it does not have any rules, whereas Pega-ProcessCommander rule-set have UIKit related application rules. I am not able to understand the reason behind this kind of setup.
Plz clarify this.
Also this statement is not very clear for bold lines :
There is a 99 patch version available of the Pega-ProcessCommander ruleset in the product. Use that ruleset version as a prerequisite to avoid having to update the ruleset after product updates.
--
Thanks for helping!
Pegasystems Inc.
US
Rulesets that say they are dependent on 07-10-99 are essentially saying they are dependent on the 7.1 version of the PegaRULES application.
07-10 patch versions can be added that are lower than 99 without you having to change every ruleset that says it is dependent on 07-10-99..
Every ruleset in your Ruleset Validation mode application does not have to say it is dependent on 07-10-99. You only need one ruleset that declares this dependency, for example, the OrgInt ruleset. The Org ruleset can then say it is dependent on the OrgInt ruleset, so on and so forth.
What you could do is create a small application that only contains the Org and OrgInt rulesets, call it the "Enterprise", "Org", or "OrgEnt" application. Then have other applications built on that OrgEnt application use Application Validation mode.
Pega began support for multiple built-on applications (MBOAs) in 7.2.2.
Rulesets that say they are dependent on 07-10-99 are essentially saying they are dependent on the 7.1 version of the PegaRULES application.
07-10 patch versions can be added that are lower than 99 without you having to change every ruleset that says it is dependent on 07-10-99..
Every ruleset in your Ruleset Validation mode application does not have to say it is dependent on 07-10-99. You only need one ruleset that declares this dependency, for example, the OrgInt ruleset. The Org ruleset can then say it is dependent on the OrgInt ruleset, so on and so forth.
What you could do is create a small application that only contains the Org and OrgInt rulesets, call it the "Enterprise", "Org", or "OrgEnt" application. Then have other applications built on that OrgEnt application use Application Validation mode.
Pega began support for multiple built-on applications (MBOAs) in 7.2.2.
With MBOAs you can continue the same pattern, i.e., OrgEnt being the only application that uses Ruleset Validation mode, every other application using Application Validation mode.
If you attempt to use the same non-Org ruleset in multiple non-Enterprise applications, a Warning will be generated.
Ideally a ruleset would only be mentioned in one and only one application. You should never have two applications that include the same ruleset.