how to return control back to default user portal page
In my application, we are using single work space for all the harness, When user open a work object and completes processing, we are closing the work object and from this control should automatically navigate back to Home screen/default portal page.
Below article illustrates this is a OOTB feature but is there a way to override the same.
SA-8079
Thanks,
Charu
Accepted Solution
Wells Fargo
IN
Fixed my issue by following below approach:
Solution-2) Change the DC configuration of your portal to create top navigation(no frame) portal. In this portal on close/cancel of the document, it takes you to the home page.
Since mine is a single thread/doc application, i configured my dynamic container with mode as single document with Section. Now, OOTB cancel/close will take me back to home page.
Single Document with Harness does not work in PEGA 7.1.7. Thefore, had to go with round about solution of using Section inside DC instead and changing rest of the code to handle it.
Pegasystems Inc.
IN
HI ,
Give a try to configure the new document (launching a new document) ,on click in the menu ,instead of using replace current Harness.
Wells Fargo
IN
Hi , In my application , i am working on a single document/tab/workspace so if use New Document as an option then the Harness open in pop-up window. This is OOTB.
In my workobject, after the last Submit button, work object should get resolved( achieved using finish assignment) and control should go back to default portal screen.
Pegasystems Inc.
IN
By the details you provided we think your portal is configured like casemanager7 portal, on this portal when you close the current document, it takes you to the previous active document. This is expected behavior.
Solution-1) Configure pega.desktop.activateDocument(0); and Cancel OOTB actions on the close button.
Solution-2) Change the DC configuration of your portal to create top navigation(no frame) portal. In this portal on close/cancel of the document, it takes you to the home page.
Wells Fargo
IN
Yes, you got it right. My application should behave like casemanager7 but with this modification.
Could you please elaborate on your solution 1 which sounds better.
How do i configure pega.desktop.activateDocument(0); ?
One more question- I have 2 links on my Portal Header
1. Search 2. Create Transaction.
When i click on Search , i have configured "pega.desktop.showHarness" and call my Search Harness with passing Param.replaceCurrent=true. This replaces existing thread.
When i click on "Create Transaction" , i have configured "Create Work" passing my flow and flow params. This is creating a new thread. Is this OOTB? If yes, how do i change to ensure system works only in one single thread?
Accepted Solution
Wells Fargo
IN
Fixed my issue by following below approach:
Solution-2) Change the DC configuration of your portal to create top navigation(no frame) portal. In this portal on close/cancel of the document, it takes you to the home page.
Since mine is a single thread/doc application, i configured my dynamic container with mode as single document with Section. Now, OOTB cancel/close will take me back to home page.
Single Document with Harness does not work in PEGA 7.1.7. Thefore, had to go with round about solution of using Section inside DC instead and changing rest of the code to handle it.