Application stack hierarchy for multiple built-on applications

I’m reading through the article given below, while I understand most of it, I didn’t understand how the system determined “Underwriting app” should be above “Pricing app”. Why not “Pricing app” above the “Underwriting app” ?

Can anyone help me understand this ?

@ravi9779 You will understand it better if you could try with actual built on list from the product as below. Even though product link says mortplus is built on 2 applications - Underwriting & pricing, in Pega we’ll be mentioning them like below (Treat ByshuDev as mortplus)

So stack will be built like below ( You can rely on the order/numbering)

ByshuDev

UnderWriting

Pricing

Hope this helps. If you understand this concept with this explanation, please accept the solution.

@Byshu thanks, so this is because you have ordered built on applications in that way. if you flip pricing as the built on application 1, the ruleset stack will change accordingly.

I still didn’t understand how the design time application stack presented in Pega article is possible, unless it’s just trying to depict which version of uPlusFin takes precedence when your multiple built on applications have different version’s of “their own” built on apps.

@ravi9779 In the provided article 3 things are the core points

  1. Pega builds linear stack using depth first algorithm when there are multiple built-on with PegaRules at the bottom.

  2. For duplicate applications in the stack, only bottom most app will be used

  3. For duplicate applications with different versions, higher version will be considered.

You can refer below image for easier understanding of how its done

Please let me know if you are still have doubts, if so in which step you need more clarification.