At one point, I recall that work objects opened in separate popups instead of the main window if they required a different access group due to differing ruleset or privilege/role requirements, so the popup was needed to isolate a separate thread or requestor that represented that work object with its required access group. So you may want to check that. /Eric
To eliminate possible causes, I tried not to log in through SSO and log in directly through regular pega log in screen. I still can see the problem.
Use case is to create an WO immediately after user logs in to pega. This is a requirement for external customers. As soon as they click on a button in company portal, they are logged in through SSO and shown the pega screen for them to work (WO is created behind the scene).
Steps to create this issue -
1. Create a operator ID. In the Harness for its portal, include a panel set. In the panel set include a section A. Inside Section A include a non auto generated section with below script.
I can create WO through the authentication activity, but the question is since the WO is the only screen shown to the user (no worklist), showing the same WO on screen is difficult. How will I know which WO ID to show for the user.
Followed the way specified in the pdn link you had sent. I am able to open the WO in the main screen. This gives me another issue. The Screen layout of screen flow doesn't show correctly. Attaching a screen shot. I will try using a regular flow instead of screen flow and see how it behaves. Will update soon.