Ruleset validation and runtime polymorphism

Blueprint and App Design
, , ,
1

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.

2

@BasG0629

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 ?

3

@Byshu Clear explanation, thanks! :slight_smile: