Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Requirement to provide links to access specific assignments

SA-9879

Summary



The requirement is the ability to provide links (for example in emails) that lead to PRPC user portal with an assignment opened in it.

If the user is logged out, the link should open the portal with assignment in it without asking for a login and password, this information is implied to be provided in the link along with assignment handle.

If user is logged in and has a PRPC portal opened in one of his tabs, preferably the link should use said tab.

After completing this assignment user should be able to continue using the portal as usual.

What has been managed so far is to create links which open assignments, but without portal, so the user cannot continue after processing said assignment and also to provide links to the portal, but without any assignments opened in it:

What is needed accessing the portal and having the assignment opened in it, pretty much combining these 2 things.



Resolution


 

There is no way to configure the exact functionality which is requested.

The PDN article "How to create a process that opens a portal from an assignment link" does not provide the functionality.  The article describes using openWorkByHandle, but this opens the work item in a new window.

A choice must be made whether to open the assignment without a portal or to provide a link to a portal.

For the former, there is Directed Web Access (DWA) which is part of the product which will accomplish this.

How To Implement Directed Web Access
 https://pdn.pega.com/correspondence/how-to-implement-directed-web-access

This method does not require that the customer log into PRPC.

If a link to the portal is provided in an email, the existing authentication processing can be used.
Trusting that the person with access to an email is indeed the correct person appears to be a weakness in the described authentication processing and is not recommeded.

Published June 12, 2015 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us