Question
Capgemini
SE
Last activity: 24 Sep 2018 1:34 EDT
Technical difference between Manager portal and Worker portal
How case manager and case worker portals work so differently even though they looks so similar. My application uses both the portals. I had a requirement to put few new link in the left navigation pane. It should be common for both the portals . Strangely some work fine in both the portals while some work fine in one but not in the other.
The most strange behaviour I saw on case worker portal was that, on click of a link in navigation pane I opened a harness. Within harness there was a section which has a link to open a modal window. In worker portal the modal was not popping up. Instead showing the busy indicator. But in manager portal same link was working perfectly fine.
I noticed in manager portal, each link in the navigation is creating a new thread when clickef but in worker portal only a single thread exists and get overriden on subsequent clicks.
***Edited by Moderator Marissa to update platform capability tags****
Accepted Solution
Capgemini
SE
Manager's portal is pyCaseManager7 which includes a harness pyCaseManager7 which in turn includes a section pyCaseManager7. pyCaseManager7 section has a dynamic container which includes harness pyDashboard7. While including a harness in dynamic container, there is an option to select Mode (Single Document or Multi Document). Here all the difference comes between a manager portal and worker portal.
Manager portal has Multi document selected while Worker portal has single document selected. The effect of this selection is realized when we launch a portal from left navigation pane. If an item in navigation pane has an action to launch harness and if the target is selected as Replace Current then the content of the current thread is replaced with new data. If "New Document" target is selected then a new thread is spawned.
New thread will only be spawned in Manager portal because it has multi document option selected in dynamic container. In worker portal only one thread exists and same will be replaced over and over again.
That is the reason when we open a work item in manager portal and try to open the same again, it gives a javascript alert that "case-xxxx is already open. Do you want to refresh?". But the same is not observed in worker portal.
Please correct me if anything is wrong in my understanding.
CollabPartnerz
IN
HI,
Below link might help you.
Accepted Solution
Capgemini
SE
Manager's portal is pyCaseManager7 which includes a harness pyCaseManager7 which in turn includes a section pyCaseManager7. pyCaseManager7 section has a dynamic container which includes harness pyDashboard7. While including a harness in dynamic container, there is an option to select Mode (Single Document or Multi Document). Here all the difference comes between a manager portal and worker portal.
Manager portal has Multi document selected while Worker portal has single document selected. The effect of this selection is realized when we launch a portal from left navigation pane. If an item in navigation pane has an action to launch harness and if the target is selected as Replace Current then the content of the current thread is replaced with new data. If "New Document" target is selected then a new thread is spawned.
New thread will only be spawned in Manager portal because it has multi document option selected in dynamic container. In worker portal only one thread exists and same will be replaced over and over again.
That is the reason when we open a work item in manager portal and try to open the same again, it gives a javascript alert that "case-xxxx is already open. Do you want to refresh?". But the same is not observed in worker portal.
Please correct me if anything is wrong in my understanding.
Adaps
IN
Below link might help you