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-124944 · Issue 186362

Handling added for 'agentinfoupdate' map exceptions

Resolved in Pega Version 7.1.8

The function 'agentinfoupdate' updates a distributed map (provided by Hazelcast) for the purpose of an agent landing page. This distributed map was throwing exceptions which did not have proper handling, resulting in the agent scheduler being terminated and thereby stopping agent functionality. The required handling has been added to prevent this situation.

SR-124952 · Issue 189563

Resolved HTMLtoPDF font load error

Resolved in Pega Version 7.1.8

When using a Fonts directory during HTMLToPDF conversion, the StaticContent folder resolved to an incorrect properties file and generated an error that appeared to indicate the fonts had not correctly loaded even when they had indeed loaded. The error was traced to the function used to open the Static Content folder with the direct file handle, and this has been updated to resolve correctly.

SR-124952 · Issue 189565

Resolved HTMLtoPDF font load error

Resolved in Pega Version 7.1.8

When using a Fonts directory during HTMLToPDF conversion, the StaticContent folder resolved to an incorrect properties file and generated an error that appeared to indicate the fonts had not correctly loaded even when they had indeed loaded. The error was traced to the function used to open the Static Content folder with the direct file handle, and this has been updated to resolve correctly.

SR-124971 · Issue 188628

Button type filter added to Report Browser

Resolved in Pega Version 7.1.8

After navigating to the Report Browser and then back to another tab, clicking on any input field and clicking enter caused the columns filtering pop-up to appear even if the user was not on the Report Browser tab. This issue only occurred with the FireFox browser due to FireFox treating elements as the 'default action' of the form and using them as submits, causing a press of the enter key to fire off the onclick event for those buttons. In order to correct this, the type='button' attribute has been added to the filter

SR-124989 · Issue 188104

Added error handling for passivated dashboard tab

Resolved in Pega Version 7.1.8

If the dashboard tab has been ide for 30 minutes or more, clicking on links on the tab generated 'not found' errors and NPE exceptions . This failure was traced to the passivation process, which does not save read-only pages and has been resolved by modifying change tracker logic to not send null values when read-only data page is not present.

SR-125028 · Issue 187645

List View filter corrected

Resolved in Pega Version 7.1.8

When enable filtering is turned on in the display fields, the ListView filter tab failed to retrieve the record. This was traced to the Keycode 32(space bar) being conditionally added in pega_ui_listview, and has been corrected.

SR-125042 · Issue 193350

Corrected decimal field validation for special characters

Resolved in Pega Version 7.1.8

The '&' symbol was not being parsed correctly when entered into a decimal field. This was a tooltip issue with the ampersand character when the harness setting was set to full error text, and has been resolved.

SR-125044 · Issue 187842

Ampersand(&) handled as text and not parameter for data transforms

Resolved in Pega Version 7.1.8

When passing a parameter to a data transform, if the parameter value contained an ampersand ('&') or certain other non alphanumeric characters, an error was generated (visible in tracer) and the task failed. This was a case where an '&' character was not not handled as literal text, causing the RunActionWrapper to explicitly parse it and create params out of it. There was a local-change solution to directly reference a property value containing the required text value instead of passing it in via a parameter, but the system has been updated to encode ampersand(&) in the file pzpega_ui_events.

SR-125070 · Issue 186577

SOAPRequestEnvelope parameter added for custom Auth Activity

Resolved in Pega Version 7.1.8

In some cases, the SOAP request envelope content was not available to the authentication activity called by the auth service protocol. Since the operator ID is derived via a decision table from a different value in the SOAP request envelope, there was no way to use that value as an input to the new authentication activity. To correct this, SOAPRequestEnvelope is now made available on the parameter page of customAuth Activity with name "pxReqSOAPEnvelope".

SR-125079 · Issue 187143

Fixed HTML title error in tooltip

Resolved in Pega Version 7.1.8

The tooltip of the error icon on a tab in a tab group was showing as "null" in the HTML title attribute. This has been resolved by adding the data-taberror attr to the td with id = 'tabcontainer', which is used to find the title of an error element in js.

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