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-D24318 · Issue 494059

Dom API updated to resolve Microsoft Internet Explorer 11 not loading async data with refresh when

Resolved in Pega Version 8.1.6

The browser was continuously showing "loading" if Microsoft Internet Explorer 11 was used for a section which was sourced from a data page and configured to load the data asynchronously from a external service while calling an activity and using a 'refresh when' rule to refresh the section if a property changed. Investigation showed that the initial data load was successful and the section with the data was visible, but if the property changed and the section loaded once again due to the 'refresh when' condition, the browser was unable to render the defer loaded section case because the dom returned had the wrong value. To resolve this, the API used to check for the dom element has been updated.

SR-D16074 · Issue 485882

Additional language options added to Language Wizard dropdown

Resolved in Pega Version 8.1.6

An enhancement has been added to the “select a language” dropdown in the Language Wizard that extends the available options to include Latin American Spanish (es_XL), Brazilian Portuguese (pt_BR), and Korean (ko_KR).

SR-D17418 · Issue 498722

Attached note header displays properly in Hebrew locale

Resolved in Pega Version 8.1.6

With the locale set to Hebrew, the whole portal is presented correctly from right to left, but when opening a case note (attached email) the header was not displayed as right to left. This has been resolved by updating the 'DisplayNote' HTML of class 'Data-WorkAttach-Note' and 'Show' HTML of class 'Data-Corr-Email' to use locale information from the operator.

SR-C96680 · Issue 483764

Reject changes in approvalRuleChanges flow will clear cache and reassemble rules

Resolved in Pega Version 8.1.6

When a paragraph rule with "need approval" checked in the ruleset version was delegated, previewing the data in the paragraph rule via a button and making changes worked as expected. However, after the changes were made and sent to the approver to accept or reject the changes and the private copy was deleted, it was observed that rejected changes still showed in the paragraph rule and the cache was not cleared. The Rule Approval process allows checkouts to be approved or rejected: when not using rule approval process, a Checkin from the personal ruleset results in a Delete operation (from WBCheckIn & RuleCheckIn) that will remove the rule from the personal ruleset. However, with Rule Approval process setup, the rule in the personal ruleset is not deleted. Instead it is simply moved to the CheckInCandidates ruleset. The pyRuleset on the rule page changes, but the Inskey remains the same. Because there was no delete operation, there was no noteChange event and the cache was not cleared. To resolve this, the system has been updated to now enable NoteChangeInternal to invalidate rules that are part of the personal ruleset only if they have the correct setting in their prconfig.xml. This fix also forces re-assembly of rules after check-in and approve/reject so that pressing preview will ensure the correct rule gets displayed.

SR-D22210 · Issue 496435

Submenu is correctly hidden

Resolved in Pega Version 8.1.6

While creating any new case item from the navigation menu, the menu was not displaying the actual list of options after selection. Instead, it remained in the expanded menu form. This was traced to an incorrect menu status due to an error in checking the value and has been corrected.

SR-D13533 · Issue 488346

Grid generation updated to facilitate button with on-click action

Resolved in Pega Version 8.1.6

An issue with an on-click event not getting fired was traced to an issue with Action generation on a button in a grid cell. This has been corrected by removing the code that set the parameter "isTemplatizedGrid" in runtime during grid generation.

SR-D21266 · Issue 489799

Corrected mathematical operations in mobile offline data transforms

Resolved in Pega Version 8.1.6

Mathematical operations such as *, /, or % were not working in mobile offline data transforms. This has been corrected by updating pzpega_ui_datatransform_generator.js to support all mathematical operations and actions.

SR-D6947 · Issue 444603

Email AttachmentPage updated to support use of Data-WorkAttach

Resolved in Pega Version 8.1.6

Attachments were not getting appended in the email sent by the Agent SendCorr. This was traced to a null Page that resulted if the attachment was of type custom Data-WorkAttach, and has been resolved by modifying the condition check on the objclass of AttachmentPage to change it from equalsIgnoreCase(Data-WorkAttach-File to startsWith(Data-Work-Attach-) .

SR-D6261 · Issue 486482

Enhancement added to support mobile offline multiple assignments for single workitem

Resolved in Pega Version 8.1.6

After completing stage1 of creation, a case generated two assignments intended for another user. That user was then unable to open the screenflow assignment in mobile offline. Investigation showed that the system was using one--to-one mapping of a workitem to assignments for offline. If multiple assignments were created for the same work object, only the first one was packaged. Changes have now been added to support more than one assignment for single workitem.

SR-D18217 · Issue 489811

Corrected PDF generation when an image filename has special characters

Resolved in Pega Version 8.1.6

When using Export to PDF with an uploaded image file that had special characters in its name, the images were missing from the generated document. This has been corrected by updating the decoding of the URL to not remove the checksum when using RTE.

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