Question
Pegasystems Inc.
US
Last activity: 28 Feb 2019 13:32 EST
Transitioning between cases is generating second tab instead of reusing the existing one
I am working with CSHC 7.21 and am having trouble getting it to transition from one case to another within the same tab within the interaction portal. Here is the setup:
I am creating a new non-interaction case within the interaction portal. After the first step in the non-interaction process, I am creating an instance of an interaction based class, an outbound interaction. After I create the new interaction case, I save its pzInsKey to the originating case. Then, within the originating case's process flow, I am having the originating case run a flow on the child case (not as a spin off). Outside of CPM, what normally would happen is that the work object would be replaced with the work object from the subflow and I would be automatically working on the subflow. When the subflow steps were complete, the system would automatically transition back to the originating case and resume the original flow at the next step after the one where the child case's flow was launched.
In CPM, what is happing is that the originating case is being left open with a review type harness and a task on the left that allows me to close the work object. The new case is being opened on a separate tab. What I want to have happen is that the new case replaces the old case in the portal and that I don't see the new case until I finish the child flow.
I am working with CSHC 7.21 and am having trouble getting it to transition from one case to another within the same tab within the interaction portal. Here is the setup:
I am creating a new non-interaction case within the interaction portal. After the first step in the non-interaction process, I am creating an instance of an interaction based class, an outbound interaction. After I create the new interaction case, I save its pzInsKey to the originating case. Then, within the originating case's process flow, I am having the originating case run a flow on the child case (not as a spin off). Outside of CPM, what normally would happen is that the work object would be replaced with the work object from the subflow and I would be automatically working on the subflow. When the subflow steps were complete, the system would automatically transition back to the originating case and resume the original flow at the next step after the one where the child case's flow was launched.
In CPM, what is happing is that the originating case is being left open with a review type harness and a task on the left that allows me to close the work object. The new case is being opened on a separate tab. What I want to have happen is that the new case replaces the old case in the portal and that I don't see the new case until I finish the child flow.
I have tried some of the suggestions on other posts related to Calling CAClearAllClipboards and CPMClearPortalRecent, but the originating tab will not auto close or auto replace itself with the content from the subflow.
***Updated by moderator: Lochan to move post from PSC to Pega Applications community***
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Pegasystems Inc.
US
I discovered the issue: On the child flow there is a "Supporting Process Settings" section with a checkbox marked "Look for an Assignment to perform after add". Unchecking this box resolved the issue.
Pegasystems Inc.
US
On further evaluation, I found that this selection worked only for the case where a non-interaction work object was calling an interaction work object and the interaction work object subsequently became the interaction object for the session. When I am not ready to use an interaction object within the confines of the interaction portal, I keep getting tabs left open when I have one case create a child case within another, launch the case and then return to the parent case upon conclusion of the child case.
I have tried many different things to get around this, but it appears that within the interaction portal, it is trying to manage a bit of a nested relationship within a single thread which is manifesting as two visible tabs.
Pegasystems Inc.
IN
Hi Chris, I've not tried but i think this can be work around by updating D_CPMPortalRecents page at necessary stages. This is good requirement w.r.to flow processing. CPM handles the tabs differently and apart from that flow processing should be same.