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-A17070 · Issue 239464

Accessibility added for field level validation messages in Microsoft Internet Explorer

Resolved in Pega Version 7.2.1

Server-side validation error messages were not read aloud in Microsoft Internet Explorer11 when the accessibility user tabbed to the field with the error. The API has been updated to resolve this.

SR-A17159 · Issue 235008

Year range calculation updated

Resolved in Pega Version 7.2.1

If a datetime control was configured as a dropdown list for a Date field in a screenflow, selecting a date and clicking "Next", then traversing back to the Date screen changed the year, ex. at run time, Year range is from 2006 to 2026, but became 1996 to 2016 when the focus returned. The current logic of year calculation was based on the year already set, and changes have been made to pzGenerateDatePicker to consider the current year when populating the year dropdown.

SR-A17175 · Issue 234726

Corrected results display for upgraded pysearchResultWork filters

Resolved in Pega Version 7.2.1

When applying the pysearchResultWork filter on the native work objects search bar, some results were not displayed as expected after upgrade. This was caused by an error in setting the property for ad hoc cases inside a child activity, and has been fixed.

SR-A17183 · Issue 241734

Swimlane flow connectors visible after upgrade

Resolved in Pega Version 7.2.1

After upgrade, some of connectors between the flow shapes were not appearing as expected when opening flow rules forms designed with Swimlane even though the flows ran as expected. Attempting to amend the flow rules by reconnecting the shapes caused the ruleform save to fail. This issue stems from problems opening the Decision Tree rule Data-MO-Connector-Transition.pyBuildLabel on a Pega 7.1.8 system. This has been fixed.

SR-A17193 · Issue 236190

Custom height settings retained for progress bars

Resolved in Pega Version 7.2.1

After upgrade, the settings contained in the final rule pzjquery_ui_progressbar_dotluv CSS were overriding custom height settings for progress bars. The code has been updated to ensure custom settings are retained.

SR-A17217 · Issue 234378

Security enhanced for RelayState

Resolved in Pega Version 7.2.1

Transport layer security (enabling SSL/TLS for all the communications) has been added to RelayState handling.

SR-A17223 · Issue 238044

Fixed JS error for Date Calendar changes

Resolved in Pega Version 7.2.1

Using Microsoft Internet Explorer, the Date Calendar was intermittently throwing a JavaScript error when trying to select another date from the date picker. This was caused by the rapid changing of dates overwhelming the onChange refresh section configured on the date input and leaving a stale input element, and has been fixed.

SR-A17278 · Issue 232804

Corrected file output override of Manifest path

Resolved in Pega Version 7.2.1

If a path was indicated by selecting the 'Include Manifest' check and the rule was saved, the manifest output directory path was overridden by the value of File Output directory the next time the rule was opened. This has been fixed with changes to pzCopyContentstoManifest DataTransform that will auto-populate the Manifest file directory and Manifest file name with the output file directory, and then output the file name of the extract only if the Manifest file directory and Manifest file name are empty.

SR-A17288 · Issue 237095

Email listener leaves empty text body untouched

Resolved in Pega Version 7.2.1

When Email Listener received a new email of Content-Type: text/plain with a subject line but an empty message body, it copied the email's subject to the email's body. This was traced to code explicitly performing this copying, which has been removed.

SR-A17313 · Issue 246970

Function added to XML manifest that includes empty pagelists for count

Resolved in Pega Version 7.2.1

If a PageList with empty properties is extracted to XML, it still appears in the XML file with empty tags but the entry is not counted for the pxTotalClassInstanceCount pagelist nodes count in the manifest file. This is as intended. As an enhancement to help with validation of the extract, an additional function pxTotalInstanceCount has been added to summarize all of the entries that are included in the XML regardless of whether or not they are populated with data. This will equal the pxTotalClassInstanceCount plus the number of empty tag entries.

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