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-A19539 · Issue 239366

Email listener updates related to DSS settings

Resolved in Pega Version 7.2.1

When sending email with .txt, .png, .docx, or other attachments, the file attachment name was not inlining with other attachment names in the body. This has been fixed. In addition, text attachment names were not listed in the attachments list if DSS was set. The code has now been modified to add the attachment name irrespective of the DSS setting.

SR-A19551 · Issue 240032

LightweightList disabled for dynamic ObjClass + blob

Resolved in Pega Version 7.2.1

If the ObjClass was a property, UseLightWeightList was checked, and the page property .ActivityStatus (data access = Manual) was put in the query to get the blob, Obj-Browse failed with "The property .ActivityStatus was of mode Page List while Read-Only Virtual List.initialize was expecting String mode". Prior to this fix, useLightWeightList was disabled only when the pxObjClass was constant. Since dynamic ObjClass cannot determine the property mode, LightWeightList will be disabled in this scenario to avoid this error.

SR-A19705 · Issue 246975

Hash table logic fixed for invokeMQConnector

Resolved in Pega Version 7.2.1

Logic issues were found and fixed related to hashtable usage for invokeMQConnector.

SR-A19811 · Issue 241385

Enhanced column supports in 'Export to Excel'

Resolved in Pega Version 7.2.1

Reports using functions in columns were not working with 'Export to Excel'. This has been fixed. Support has also been added to display all the report column localized values in pzListViewExcelData while doing Export to Excel: Simple Column, Joins, Declare Index, Associations, Sub Report, Functions and Embedded Properties.

SR-A19811 · Issue 239285

Enhanced column supports in 'Export to Excel'

Resolved in Pega Version 7.2.1

Reports using functions in columns were not working with 'Export to Excel'. This has been fixed. Support has also been added to display all the report column localized values in pzListViewExcelData while doing Export to Excel: Simple Column, Joins, Declare Index, Associations, Sub Report, Functions and Embedded Properties.

SR-A19858 · Issue 236943

Dialogue handling updated for WS-Security Profile password

Resolved in Pega Version 7.2.1

The presentation format for the password field of the WS-Security Profile outflow page has been changed to no longer display the password in the clear in any resulting dialogue.

SR-A19871 · Issue 237975

MS Transport supports Global Resource Settings

Resolved in Pega Version 7.2.1

Documentation indicated that the JMS Transport data instance supported GRS syntax, but attempting to do so generated an error. That support is now available as indicated.

SR-A19972 · Issue 238961

Expanded search re-indexing submit methods

Resolved in Pega Version 7.2.1

When creating an index in the 7 series, the Search Landing Page for indexing did not indicate that the page needed to be submitted to enable the indexes before attempting to start the re-indexing process. An error was thrown in the tracer, but nothing was displayed on-screen to indicate why the system hadn't started indexing. To ensure the expected results, the indexing will begin after the "Submit" button is clicked or if the enable indexing check box has been checked to indicate the system has permission to start indexing without having an explicit submit.

SR-A19980 · Issue 242374

Added RunShortCut security for reporting

Resolved in Pega Version 7.2.1

Unauthorized users were able to run out-of-the-box reports through pxRunShortcut by updating the address URL and executing the final "pxRunShortcut" activity. pxRunShortcut now includes the function "pyCheckSecurity" for customers to write their own privilege conditions, and Page-Set-Messages will display a message created in the pyRuleSecurityErrorMsg HTML.

SR-A19986 · Issue 242898

getAppHashForApplication API updated

Resolved in Pega Version 7.2.1

When logged in from an end user portal, editing a decision table and clicking on the gear icon to add a function would show the Function's headers (Example, Activity, string, etc.), but the functions list would not be loaded. This was traced to a timeout resulting from having numerous functions running on the portal combined with a configuration that returned an unowned AppHash when calling a ruleset from the production layer rather than the application layer, and has been resolved by adding logic to write out the AppHash when the appInfo is created from opening the application.

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