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

PEGA link with session data would not be launched properly

SA-45318

Summary



When launching Pega Express portal from Bookmarks, the portal appears incomplete. The portal does not display a header, logout options, or menu (on the left side).


Error Messages



Not Applicable


Steps to Reproduce

  1. Launch the Pega Express portal.
  2. Navigate to the Cases tab (ensure that there is at least one case in the list) > Reports tab.
  3. Click the Cases tab again. Bookmark this URL.
  4. Open an incognito window. From the bookmarks open this URL. The portal does not display correctly.


Root Cause



A defect in Pegasystems’ code or rules.

URL masking was not working correctly for the affected portals such as, pyPega7Express, pxExpress, Case Worker, and Case Manager portals.



Resolution



Pega does not support bookmarkable URLs in its portals. The out-of-box portals use a dynamic container to host different documents in the portal. The portal panels (such as, top banner, left navigation, etc.) and work items are retrieved from different harnesses. Based on the dynamic container configurations, the URL may contain information related to the current harness displayed in the portal. The session information is not backed into the URL. The Case Worker portal uses different dynamic container configurations in Pega 7.2.2 (single document mode (no-iFrame) mode) and Pega 7.3.1 (Single Page mode – introduced in Pega 7.3). These two modes are similar but are different. The single document mode navigates the whole page to a different URL. The newer single page mode uses AJAX requests to replace the center panel content of the portal. Both these modes maintain browser history in that session (that is, the Back or Forward buttons in the browser). These URLs are not intended nor are they designed to work through bookmarks.

Hence, this is an expected behavior in Pega 7.2.2.



Suggest Edit

Published March 22, 2018 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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