Question
WIPRO
IN
Last activity: 21 Jan 2023 18:13 EST
Organization layer built-on Strategic apps affect new vennila applications
Hi
In my application, I have an application hierarchy as A extends B extends C extends PegaRules where A is the implementation layer, B is the organization layer and C is PEGA KYC/CLM.
Now I want to create a new simple application X and I need to re-use organisation assets by extending application B but I dont want the KYC/CLM for the application X.
How can I fix this problem? Should I move the KYC/CLM as a built-on application to A and, B directly extends the PegaRules?
Or
Create another application rule B1 with all the organisation layer rules and built-on PegaRules?
Note: Application A is already running in production.
***Edited by Moderator Marije to add Capability tags***
Bits In Glass
IN
Moving the KYC/CLM as a built-on application to A and, B directly extends the PegaRules should solve your issue.
Just make sure to check operator profile once you update the built-on apps hierarchy, so that the applications rulesets are in the expected order.
Updated: 29 Nov 2022 20:14 EST
Agriculture Victoria
AU
@MOHANRAJS7274 Assuming that rules in B are not going to need to use KYC/CLM at any point, you can do this
A -> built on B, KYC
B -> built on PegaRules
X -> built on B
WIPRO
IN
@PraveenPuri_old Thanks for the reply. Unfortunately B has some rulesets which uses KYC/CLM which ideally should not be. So we are moving those specific rulesets in B to A and everything else as you mentioned.