Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Bas Groeneveld (BasRulesMatter! )
Ordina
Pega Developer
Ordina
NL
BasRulesMatter! Member since 2019 23 posts
Ordina
Posted: Jun 21, 2022
Last activity: Jul 7, 2022
Posted: 21 Jun 2022 11:40 EDT
Last activity: 7 Jul 2022 12:09 EDT
Closed
Solved

Ruleset validation and runtime polymorphism

Hi, 

Say we have an application called 'Sales' with a built-on application 'SalesBase'. If we have a section in 'SalesBase' that refers to another rule in 'Sales', this is throwing a validation error. Pega does not allow traversing in the stack in this direction. However, if we then create a placeholder rule in 'SalesBase', it is validated and we can save it. Furthermore, runtime polymorphism / rule resolution will pick the version in 'SalesBase'.

I tried to find a good explanation for this behaviour, but the topics on polymorphism are a little bit thinner.

To see attachments, please log in.
Pega Platform
Low-Code App Development
Consumer Services
System Architect

Accepted Solution

Posted: 2 years ago
Updated: 2 years ago
Posted: 7 Jul 2022 4:24 EDT
Updated: 7 Jul 2022 12:08 EDT
Byshu Ayyappaswamy (Byshu_Ayyappaswamy)
IQZ Systems
Director
IQZ Systems
US

@BasRulesMatter!

Design time will look for rule in 'SalesBase' ( rule in same application or lower level applications) while in runtime, system will find a more contextual rule is available in the top most ruleset of the logged in operator (Sales ruleset in Sales application)

 

Is there any scenarios you are looking for more clarification ?

 

 

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice