Last activity: 6 Jul 2016 9:29 EDT
Work area upgraded to dynamic container with no tab
We are upgrading our application from 6.2 to 7.1.5.
We have users log in through SSO and system creates WO automatically. We used to use workarea in 6.2 with no tabs. There was an option in work area to create WO when it loads.
After upgrade we have to use dynamic container instead of work area. Dynamic container does not provide option to create WO OOTB. So I have created a non auto generated section and using
pega.desktop.createNewWork("ClassName", 1, "FlowName"); to create WO automatically. I have included this section in the dynamic container.
WO is created when user logins through SSO. But the WO is opening in a pop up. We would want it to open in the main screen rather than a pop up.
Note: Flow is a screen flow.
Any suggestions? Thank you.
Message was edited by: Marissa Rogers - added categories
What browser are you using now? Is the behavior same across browsers (IE and Chome)?
I use IE. I see the same behavior in chrome too.
And are you using IE 11 or an older version?
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
I am using the same access group in Data-admin-appid as the external operator's accessgroup. Please let me know if you meant access group to be checked in any other place. thank you.
Would really appreciate If somebody can suggest any kind of approach. Thank you.
Can you please help me understand the use case a bit ?
I understand the point that users are logging in via SSO
I also understand that you are using your custom HTML to create a workobject
The thing I am not able to understand is what you mean by creating workobject soon after logging in via SSO ?
If you can give me a use case details or may be screenshot then it can help me to think of some alternatives etc. for you
Updated: 27 May 2016 14:21 EDT
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.
pega.desktop.createNewWork("ClassName", 1, "FlowName");
2. Log in through regular pega screen. As soon as user logs in, WO is created, but the flow starts on a pop up.
Note: its a screen flow.
Updated: 28 May 2016 12:44 EDT
Hi Shruti, Good morning!
>>> Use case is to create an WO immediately after user logs in to pega
we may need to either customize...
- 'Starting activity to execute' under security tab of operator ID rule [Data-Portal.ShowDeskTop] OR
- Code-Security.LDAPAuthentication, RULE-OBJ-ACTIVITY CODE-SECURITY AUTHENTICATIONLDAP
- to create workobjects as soon as user login to pega.
Please share your thoughts/comments, Thank you!
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.
Nothing would be OOTB then.
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.
Try using openSpace("Work",url,"formbyurl"); instead of createNewWork.
Shanth : I already had tried openSpace. Same result.
Please include the below in non autogenerated section and include the section in Dynamic Container.
pega.desktop.createNewWork("ClassName", '1', "FlowName" );