URL Mapping - Open assignment in operator's portal
Hi team,
Checking for options using URL mapping to open case assignment on portal for authenticated operators.
I have already implemented 2 "working" solutions, but none of them satisfy 100% of the requirement :
1) Using Assign-.ProcessAssignment activity : The assignment is shown without portal header and navigation sidebar, but all case actions case processing works fine (including "go back" feature that allow navigation on previous assignment in standard flow and between différent flows).
2) Using pyMobileSnapStart activity : The assignment is shown correctly in the portal but some case processing feature as the "go back" is not working. Also when using navigation menu (to show MyWork landing page for exemple) the portal header and menu sidebar are lost.
Are there other options with URL Mapping to open assignment on operator's portal ?
Also, curious to know if there is an explanation, why snapstart could change some case processing and portal navigation behavior ?
USU GmbH
DE
Have you found a solution for you this?
I have a similar demand, where I need to open a new case in the user portal based on the resource path.
The user portal has screen form with header, content and footer. The content section provides an ajax container where the case should be displayed.
I thought to use URL mapping for that. But now I'm struggling to implement a solution which works like when I open the case from the portal navigation.
When I open a harness from the portal navigation the harness is only opened once, so I can switch between the active ajax containers.
But when I initiate two click events, like described below, the harness will be opened twice.
My setup:
The portal header contains a hidden text input control with an onClick action set triggering a new harness action which calls an activity to prepare the case.
CreateMyCase(activity)->Work-.New
-> I Skip Work-.New if the pyWorkPage already exists not to create another case by browser refresh.
In the header I have an embedded not auto generated section with the following code:
Have you found a solution for you this?
I have a similar demand, where I need to open a new case in the user portal based on the resource path.
The user portal has screen form with header, content and footer. The content section provides an ajax container where the case should be displayed.
I thought to use URL mapping for that. But now I'm struggling to implement a solution which works like when I open the case from the portal navigation.
When I open a harness from the portal navigation the harness is only opened once, so I can switch between the active ajax containers.
But when I initiate two click events, like described below, the harness will be opened twice.
My setup:
The portal header contains a hidden text input control with an onClick action set triggering a new harness action which calls an activity to prepare the case.
CreateMyCase(activity)->Work-.New
-> I Skip Work-.New if the pyWorkPage already exists not to create another case by browser refresh.
In the header I have an embedded not auto generated section with the following code:
<pega:choose>
<pega:when name="ShowFirstRessource1" >
<script>
document.querySelector('input[data-test-id="2021011417583203041514"]').click();
</script>
</pega:when>
</pega:otherwise>
</pega:choose>
The difference in the browser network is that by clicking a second time with the mouse on the navigation control, the case SWITCH ActionTypes gets triggered in pzpega_ui_redux_impl.js.
But, when I execute the click event on the control two times from java script, both times the ActionType ADD will be triggered the java script file inpzpega_ui_redux_impl.js.
I hope someone has a much better and easier idea.