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-123440 · Issue 186550

JSP expressions supported as parameter IDs

Resolved in Pega Version 7.1.8

Support has been added to GridSectionBodyElements for using JSP expressions as a parameter ID for a layout configuration in the ID field of free form layout cell properties.

SR-123478 · Issue 186770

Defined order of execution for FinishAssignment and pyDeleteDocumentPg

Resolved in Pega Version 7.1.8

In an application in which a page-level message was to be output if a certain field was left blank, sometimes the page-level message did not display when the condition was met. This problem was due to the random order in which pyDeleteDocumentPg and FinishAssignment were issued by the Browser. Both are issued simultaneously to within the same 1000th of a second (according to Fiddler), but sometimes one is issued first, sometimes the other is issued first. Whether or not the function succeeded depended on whether or not pyDeleteDocumentPg was processed first by the server. In order to ensure the proper behavior, the submit and harnessOnBeforeUnload methods defined in pega.u.d object have been modified to send the finishAssignment request after processing the pzDeleteDocumentPg request.

SR-123486 · Issue 186635

Resolved access denied autocomplete error

Resolved in Pega Version 7.1.8

An 'access is denied' error generated while accessing the autocomplete was traced to a JavaScript error in the popup window handling, and has been fixed.

SR-123608 · Issue 186749

Local action launch corrected for CPMFS frameworks

Resolved in Pega Version 7.1.8

An issue in CPMFS framework generated the error "Local actions are available only when you are performing the assignment" on selecting any local action from the Perform harness. ActionAreaContent adds a parameter' actionsection' using '; //--> . When the above section is included in pyCaseActionAreaTabbedScreenFlow, that param was being populated, but not in case of CaseActionArea. This was due to local actions being available only when performing the assignment. A check has been added for the presence of actionSection in processActionDefault, and checks whether it's empty or not.

SR-123615 · Issue 183551

DateTime localization enhanced

Resolved in Pega Version 7.1.8

Previously, language packs were literally translating items like datetime format without regard to the proper grammar of that language. For example, the date time format "4 days ago" came up as an "4 Tage vor" in German, which is not correct usage. A localized parameter-based API with 54 different field values has been added to the pxFormatDateTime RUF to allow field values with arguments so the proper localization text can be displayed.

SR-123615 · Issue 183745

DateTime localization enhanced

Resolved in Pega Version 7.1.8

Previously, language packs were literally translating items like datetime format without regard to the proper grammar of that language. For example, the date time format "4 days ago" came up as an "4 Tage vor" in German, which is not correct usage. A localized parameter-based API with 54 different field values has been added to the pxFormatDateTime RUF to allow field values with arguments so the proper localization text can be displayed.

SR-123617 · Issue 183668

Corrected label issue for language pack

Resolved in Pega Version 7.1.8

When a language pack was imported, the labels on the expand and collapse pane were appended with translated values instead of being replaced. This was caused by the presence of an extra space at the end of the string "Click to expand " and "Click to collapse " in workformstandard that caused a JS mis-match, and has been corrected.

SR-123642 · Issue 187841

Resolved MultiSelectList control issues for Microsoft Internet Explorer 9+

Resolved in Pega Version 7.1.8

The MultiSelectList control was no longer working for Microsoft Internet Explorer 9+. When a user attempted to select one or multiple items in the MultiSelectList control, the values were not captured when going to the next screen and a JavaScript exception was thrown. This was due to an API change in newer versions of the Internet Explorer (Microsoft Internet Explorer) browser. Microsoft Internet Explorer is following a more strict standard about how the createElement function is used, which caused the JS error to be thrown, and the system has been updated to resolve this issue.

SR-123678 · Issue 185155

Resolved issue with duplicate thread creation

Resolved in Pega Version 7.1.8

In Designer Studio, a new thread was created on every click of New Item in the recent list. This was due to the contentID generated not being passed at the document launch time, and the APIs have been updated.

SR-123741 · Issue 186119

Collapsible header text updated for accessibility

Resolved in Pega Version 7.1.8

When a UI layout/section used a collapsible header, JAWS read the field values "Click to expand" and "Click to collapse." Using the word "Click" is not optimal for accessibility, and this field has been changed to "Disclose contents" and "Hide contents."

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