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-114875 · Issue 171313

Enhanced error handling for WebSphere class conflicts

Resolved in Pega Version 7.1.8

An error caused by a class conflict issue in WebSphere was being generated when exporting Process Flow as XPDL. In order to clarify the limitations in this use, changes have been made to the XSLTRANSLATE Activity to add an extra catch that handles any style sheet errors explicitly and provides an informative error message.

SR-117877 · Issue 178627

Report on implementation classes corrected for descendant class

Resolved in Pega Version 7.1.8

Report definition was not using implementation class even when 'report on descendant class' was checked. This was caused by an access group changed in RAQ not being reflected into DAQ. When a Data-Admin-Requestor has a Access group which isn't the default, the default authentication doesn't occur and as such the application data page isn't created for the requestor. The lack of an application page causes the code to not determine the associated implementation class for the report definition. This has been changed to use the access group from DAQ only if it is newer than RAQ.

SR-117877 · Issue 175972

Report on implementation classes corrected for descendant class

Resolved in Pega Version 7.1.8

Report definition was not using implementation class even when 'report on descendant class' was checked. This was caused by an access group changed in RAQ not being reflected into DAQ. When a Data-Admin-Requestor has a Access group which isn't the default, the default authentication doesn't occur and as such the application data page isn't created for the requestor. The lack of an application page causes the code to not determine the associated implementation class for the report definition. This has been changed to use the access group from DAQ only if it is newer than RAQ.

SR-118224 · Issue 182305

Report Definition "Pick Value" list resolves to correct layer

Resolved in Pega Version 7.1.8

When a report definition in the framework layer has "Report on descendant class instances" checked, running the report from the implementation layer should retrieve pick list values for "Available Values" on filter popup from the implementation layer. Instead, it was getting the values from the framework layer. This was caused by the code that generates the SQL query to populate the "Pick Value" list resolving to the wrong work class name, using the framework layer work class rather than the implementation layer work class. There was a workaround of performing a 'Save As' of the affected reports to each implementation layer, but this has been fixed.

SR-118224 · Issue 182203

Report Definition "Pick Value" list resolves to correct layer

Resolved in Pega Version 7.1.8

When a report definition in the framework layer has "Report on descendant class instances" checked, running the report from the implementation layer should retrieve pick list values for "Available Values" on filter popup from the implementation layer. Instead, it was getting the values from the framework layer. This was caused by the code that generates the SQL query to populate the "Pick Value" list resolving to the wrong work class name, using the framework layer work class rather than the implementation layer work class. There was a workaround of performing a 'Save As' of the affected reports to each implementation layer, but this has been fixed.

SR-118283 · Issue 180166

Create New Work functionality smoothed for flows across multiple windows

Resolved in Pega Version 7.1.8

The Create New Work functionality in IAC was intermittently rendering incorrect data when opening a workflow in multiple windows. This was found to be a problem with PostDataId generated duplicate IDs for the different requests and has been changed to generate unique IDs.

SR-118795 · Issue 180517

MaxLength enforced for attached notes in properties

Resolved in Pega Version 7.1.8

If a MaxLength was given in the Advance tab for a pynote property from data-workattach-note class, it was still possible for attachments to exceed the MaxLength with no error generated. This was caused by a missing step, and the system will now check if there are any page set messages on Note page before saving.

SR-118902 · Issue 178085

Updated PDF conversion for latest versions of Microsoft Internet Explorer

Resolved in Pega Version 7.1.8

When using the Out-Of-The-Box Flow Action called "ConvertAttachmentToPDF", no error was generated at runtime but the new file attached to the case was not correctly converted. The root cause was the HTML rule called "ActionConvertAttachmentToPDF" which contained JavaScript code that was not fully compatible with the newest releases of the Microsoft Internet Explorer browser. This has been changed.

SR-119160 · Issue 176869

Accessibility enhancement added to case manager portal

Resolved in Pega Version 7.1.8

Some key areas incuding the search field were missing ARIA roles when the landmark menu on the case manager portal was brought up while using NVDA / JAWS screen reader. To remedy this, the landmark menu has been provided with a search field to quickly navigate to search field in Case Manager portal in accessibility mode. A future enhancement is planned for adding ARIA roles to auto generated sections.

SR-119213 · Issue 178963

Updated flow default for SAE-I course

Resolved in Pega Version 7.1.8

The PRPC: System Architect Essentials I training course shows how to create draft process outlines. An SAE exercise where Stage "Decision" has steps "Background Check" and "Assess Candidate" which run in parallel was not working as expected. The first step is an assignment, and the second is a multi-step process with a decision shape which points to a decision tree. If that decision shape referenced an undefined decision record, the process would not execute and there was no way to proceed with the case. This was traced to the DRAFTMODECHOICE flow rule in which "Process commander internal flow" was checked by default. This was not the preferred work flow behavior, and the default is now to leave "Process Commander Internal Flow" unchecked so the flow is not marked as internal. In addition, the instructions for DraftModeChoice assignment were modified to reflect this change.

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