Skip to main content

Resolved Issues

View the resolved issues for a specific Platform release.

Go to download resolved issues by patch release.

Browse release notes for a selected Pega Version.

NOTE: Enter just the Case ID number (SR or INC) in order to find the associated Support Request.

Please note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

SR-A21908 · Issue 245505

Eliminated new case creation on browser refresh

Resolved in Pega Version 7.2.1

When using the tabbedscreenflow7 harness, refreshing the screen caused a new Case to be created. This was seen in a no-frame portal with the top navigation for every action set to createNewWork, and the same new work URL was hit during the refresh. This has bene fixed by modifying replaceHistory in dynamiccontainer_lite.js to add a condition to skip returning when strHarnessMode is not action.

SR-A21917 · Issue 243020

Added calendar conversion support for Thai locale

Resolved in Pega Version 7.2.1

With locale set to Thailand, the date/time returned caused a substitute operator to be selected. This was an issue with the action time being calculated in the Buddhist calendar used in Thailand whereas the goal time was calculated in the Gregorian calendar. The Buddhist calendar is 543 years ahead of Gregorian, so the isAvailable RUF will convert this date by subtracting the difference.

SR-A21931 · Issue 242711

XY chart Dashboard reports updated to handle empty data

Resolved in Pega Version 7.2.1

Dashboard reports were not loading when using RD as the source for XY charts if the data returned was completely empty. RUF: pzControl ? pzRuntimeFusionXYDataJSON has been updated to handle this missing use case.

SR-A21931 · Issue 233188

XY chart Dashboard reports updated to handle empty data

Resolved in Pega Version 7.2.1

Dashboard reports were not loading when using RD as the source for XY charts if the data returned was completely empty. RUF: pzControl ? pzRuntimeFusionXYDataJSON has been updated to handle this missing use case.

SR-A21935 · Issue 247142

Corrected data page Lookup logic

Resolved in Pega Version 7.2.1

While trying to source a Datapage with Lookup, a "No records found" error was generated by the fetch using the pyClassName from parameter and considering that as primary page class instead of the data page page class. This has been corrected by using the pxObjClass from the parameter page, which is an actual data page class.

SR-A21997 · Issue 246052

Double quotes encryption handling now configurable

Resolved in Pega Version 7.2.1

When a property type of TextEncrypted was used, the apostrophe in a string was being changed to "'" due to XSS security filters. A parameter to ShowTextEncryptedPropertyValue control to support escaping double quotes has been added and is configurable based on need.

SR-A22016 · Issue 242244

Removed screen flicker when editing WorkObject

Resolved in Pega Version 7.2.1

Whenever a DynamicContainer action was invoked from the master details of an RDL row, a new harness was opened and dismissed, causing the RDL to momentarily appear on the screen. This has been fixed.

SR-A22067 · Issue 243520

Corrected passing Current Parameter Page in Collections

Resolved in Pega Version 7.2.1

When attempting to call a rule in a Response Actions entry on a Collection flow, the configuration panel would not submit when "Pass Current Parameter Page" was checked and there were required parameters on the rule being called. This was traced to an unneeded validation being performed, and has been resolved.

SR-A22074 · Issue 245363

Auto-logout updated to close browser window

Resolved in Pega Version 7.2.1

After upgrade, the pxSessionTimer was giving a timeout warning, but users were not automatically logged out as expected and the countdown timer showed a negative value. This was traced to the use of an old implementation of the pxSessionTimer rule which previously would trigger a browser window close when the time expired. This close function is not implemented in v7.2, causing the unexpected behavior. This has been fixed by updating the LogoffTimer HTML Rule to call the closeModal API by passing the correct dialogArguments.

SR-A22090 · Issue 243573

Activity method loading works with encryption

Resolved in Pega Version 7.2.1

Activity method loading was not working with URLEncryption enabled. This was a problem with populating the parameters with the encryption function in use, and has been fixed by making use of SafeURL to prepare the querystring of the URL.

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

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us