We have already 10 different applications in production. Each of these applications have their own rulesets and own case types.
We want to create a new application(Dispatcher application) and a new case type(e.g. Dispatcher case). By using Dispatcher case type, we would like to enable user to select an existing applications' case type and be able to create an instance of this case type.
We implemented this feature just with 1 application(AppA) by setting AppA as the build on application for Dispatcher application. So that we are able to work with AppA's rulesets and use their starter flows to create a case of AppA. However we want to achieve this feature for other applications as well.
We have an approach to do this, for each application we may create a service rule to create specific application's case and call these services from Dispatcher case type.
However, it would be better to have a non service solution. What would be you solution for this issue?
In the Dispatcher application, add all the other application as built on applications from the application definition landing page. This adds all the required application ruleset to the dispatcher application.
Now, from "Cases & data" tab in the application rule form add the case type classes that you would like to create.
Now, the cases added will be available under "Create" new cases list.
Attached screen shot for the same.
Posted: 5 years ago
Posted: 26 Jul 2017 1:46 EDT
Burak Ataman (BurakA90)
Thank you for your response. We are using Pega 7.1.7 and it seems that one application may only have a single built on application. Is multiple built on application feature is available in a higher release or is there any other place to configure this?
I attach a sample built on configuration from our environment.
Posted: 5 years ago
Posted: 26 Jul 2017 11:09 EDT
Avnish Kumar (kumaa21)
Principal Software Engineer
I understand. We will also try adding app rulesets to same application approach for 2 different applications.
However, there is an issue about ruleset priority. There may be some rules in organization level classes and these rules may be defined in app specific rulesets. If we add all rulesets into same application, it may distort some application's behaviour, because rules in higher prioritized rulesets may be selected and in reality these rules might not be the right ones.
It would be better if there would be a solution without any chance for spoil specific cases' behaviours.
Maybe we can also change current thread's access group from dispatcher app to specific app that we want to create case from. And we can create cases directly from that application. Is it technically possible? Or are there another solutions?