Potential conflicts between Pega Sales Automation and other strategic applications
Hello everybody,
we are building applications on top of two Pega strategic applications (Onboarding for FS and Customer Service for FS) and we have found that sometimes there are conflicts between rules with same name and same AppliesTo class that are resolved "wrongly" (picking up the rule from one FW instead of the other one, due to the ruleset order in the ruleset pile). We have workarounded this by resaving the appropriate rule at application level.
Now we want to add Pega Sales Automation to leverage the integration with Microsoft Exchange and we would like to know if somebody has already faced any similar issues with this framework in order to anticipate future problems that could delay our development.
Thank you very much,
Víctor
Pegasystems Inc.
IN
Hi All,
We support multiple strategic applications (CS & SA) on a single stack. And we have addressed all the known issues and its working fine. Infact all our vertical applications are using the same way.
You can have it on your environment and if you face any issues let us know.
regards,
Raghav
Corner Banca
CH
Hi,
how have you addressed the rule conflict? By resaving the rule that you need to be executed at an application level or have you found a way that would avoid re-copying a rule at a higher level?
Thanks,
Víctor