We have there application, named “AppCase”, “AppA” and “AppB”
Both App and AppB builds on AppCase application and reusing a case type saved in AppCase.
The case type has two steps (Create and Review). Review assignment is set to a worklist of particular operator.
When a user creates a case on AppA, the assignments routes to the worklist of the operator and accessible but only if the user logs in the same application (in case it is AppA). If the user logs in AppB, then there is no assignment.
What I would like to be able to access the assignment from AppB as well but somehow worklist filters the assignments based on the application they got created (even If the case gets created on the build on app)
I tried to add workpool definition of AppA and AppCase to the access group of AppB but it didn’t helped.
I also tried to create an overarching application and set AppB and AppA as build on apps, given all the access roles but still no result.
My questions are,
1- Why it is not getting listed from the worklist when we login to AppB?
2- Is the approach we are taking is feasible or not ?
3- We are build on cosmos theme and so remote case types are no option. Do we have any other method with out creating integration in between them (like creating a “Review” case from AppA on AppB via PegaAPIs and waiting the result of review on AppA) … ?
This widget shows all the cases If we set to a work party. I couldn’t managed to make it work as I miss that detail.
If you populate a workparty (which in general we do, but miss as experimental work) and add the operator who is going to perform to workparty, you are able to see the assignment on My Cases widget and open it as well.
Will above approach work when App A & B are not the built on applications. In this case I am able to view the assignment in “My cases” widget but not able to open or take action on it. Any workaround to submit the assignment from different application as workparty? pls suggest if you have tried already
@topra It opens the workobject in review mode, but after that complete session is getting stuck. I need to log off and login to perform any action in the portal. There are no errors till the work object is opened in review mode and post that no action is possible, so i dont have anything to see in tracer. Only action that i can perform is log off, could not even click other navigation menu to launch the respective screen.
I created ApplicationA and ApplicationB (both build on Cosmos Theme only) .. created two case types (CaseA and CaseB) on each one. I am setting current user to “Person” participant on both case type during case initiation. Cases gets created and work party (Person) get populated respectively.
I have then created ApplicationAB and added both ApplicationA and ApplicationB to this application as build on apps. Added both case types to app definition and saved.
With this setup, I managed to complete both cases I created from ApplicationA and B without any issues.
Is this setup makes sense to you ?
By the way, without ApplicationAB, I couldn’t managed to see the cases from the other apps. So having an overarching app looks mandatory to me. (I will test more)
@toprai guess that’s the only way to access different app cases in same place using myCases widgets or with out any integration. Thanks for checking this out!
@Surendar MyCases is the OOTB widget that you can use it in Theme-Cosmos. You have the process factory solution, which is almost a defacto approach for Constellation. It is worth to check that process factory is available for theme cosmos as well. These are both OOTB solutions that requires no integration.