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 update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

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.

SR-A22107 · Issue 241929

Empty workbasket names localized

Resolved in Pega Version 7.2.1

In the dashboard of the Case Manager portal, the names of empty Workbaskets were not visible due to missing initialization in the localization. This has been fixed.

SR-A22147 · Issue 244096

Autogenerated prconfig sets v6 or v7 based on detection

Resolved in Pega Version 7.2.1

The autogenerated prpcUtils prconfig.xml file was setting the database/storageVersion to 6. In order to facilitate other setups, a flag has been provided in prpcUtils.properties as pega.storageVersion which will set the value in generated prconfig.xml to an empty string so the engine handles setting this to 6 or 7 in the same way that is possible when running the system.

SR-A22152 · Issue 247716

Report Def Filter using .pxObjClass returns all results

Resolved in Pega Version 7.2.1

Using .pxObjClass as a filter in Report Definitions resulted in different and/or incomplete Class arrays being built depending on how the Value field was populated. This was traced to an incorrect "if" check in objClassOptimizer causing class names to be missed, and has been fixed.

SR-A22198 · Issue 244738

Empty access groups handling added for organizational instance

Resolved in Pega Version 7.2.1

If an unauthenticated access group was configured in the organizational instance, errors occurred because the organization instance access groups are only considered for session authorization once the user is authenticated. This will now be handled through a validate activity change in the Data-admin-organization to honor the emptiness of access groups

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