Posted: 10 Jan 2019 10:33 EST Last activity: 14 Jan 2019 14:07 EST
Opening another application's harness in portal
we have a portal which is shared by several applications defined on a base applications rulesets. Due to company's policy we have a default application which is set for each user when each user logins to Pega PRPC Portal. And from that portal each user can see different types of cases (work items) that belong to different kinds of applications and when user opens any kind of work item Pega itself handles application context of opened work item.
So that in the portal even user has aplication selected A user can process a case which belongs to another application for instance called B. However we have a different custom harness which works with rules of application B. In order to open that harness which requires to application B User needs to change application from portal to B and need to open the harness from that menu.
Now the client requires this harness which belongs to application B to be opened from other applications such as A, C, D. We know that pega can handle this situation by opening another tab with different context but we couldn't manage to do it. When we try to open a harness that depends on the rules of application B, and the currently application is not B we have errors because of rule resolution. We do not want to move the rules of the harness to the base applications because there are lot's of rules and each of them are spesific to application B.
any help will be appreciated, thanks in advance
***Edited by Moderator Marissa to update platform capability tags****
I'm not aware of any OOTB features which can do what you are suggesting. The closest that comes to mind is a multi-tenant setup, but it sounds like that might be overkill for your needs here. But in theory the use case could match.
But ultimately no matter what approach you choose, I think the common theme here or the hurdle you will always be solving is a rule resolution one. If the rule in question is saved into an application specific ruleset stack/class then unless other applications can inherit from this, I do not see how you will be able to cross applications seemlessly.