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-C89504 · Issue 435567

Multi-Select values visible in read-only

Resolved in Pega Version 8.1.5

The Selected Multi-Select values were not seen on the read-only review screen. This has been corrected.

SR-C89628 · Issue 430886

Correct values are selected in auto-complete in list configuration after scrolling

Resolved in Pega Version 8.1.5

When a value from the second page of the source list in the auto-complete was selected, the prior value was getting selected and posted. As an example, if the (n)th value was selected by scrolling down the results in the list, the (n-1) value was getting selected and posted to clipboard. Investigation showed this occurred if autocomplete was configured with allow free form input ' no', and that results were not getting selected properly after first scroll when using list configuration. This has been corrected.

SR-C89985 · Issue 435725

pzEmailActions button colors correctly reflect styling

Resolved in Pega Version 8.1.5

The default Styling for the buttons defined in pzEmailActions was not taking effect as expected to show an "APPROVE" button as green and a "REJECT" button as red in an email body with attachments. This was traced to the 'if' condition not being satisfied for the color change due to the UIkit handling the evaluation via the pyApproveInternal flow action instead of pzApproveInternal. This has been corrected.

SR-C90358 · Issue 433297

Updated Attach Content Control for use in repeat grid

Resolved in Pega Version 8.1.5

When using Attach Content Control in a repeat grid, selecting a file via attachcontent control and submitting the page resulted in the message "The operation completed successfully, but returned no content". This was traced to the newassignPage being removed after closing the modal, causing finishassignment to fail. To resolve this, the Attach Content Control function has been modified to set the needed grid attributes for desktop implementation to ensure newAssignPage will be available to the attach content modal action.

SR-C90418 · Issue 436018

Exception handling improved for pxAdjustSLA, pxAdjustSLATimes, and pzAdjustSLATimesInBulk functions

Resolved in Pega Version 8.1.5

If the SLA Deadline days were updated from 0 to 1, the SLA agent did not trigger the deadline escalation activity and the error "com.pega.pegarules.pub.context.PRQueueException: Instance of class Queue not found: SYSTEM-QUEUE-SERVICELEVEL.SYSTEM-QUEUE-SERVICELEVEL" was generated. This has been resolved with the addition of better failure handling to the pxAdjustSLA, pxAdjustSLATimes, and pzAdjustSLATimesInBulk functions for cases where an exception is generated.

SR-C91220 · Issue 430364

Modified pzpega_ui_dynamiccontainer to resolve issue with editing the Operator rule form when using IE

Resolved in Pega Version 8.1.5

The Operator rule form was not opening a second time after being updated in IE. The form worked as expected with other browsers. This has been resolved by modifying the openRuleByKeys function in pzpega_ui_dynamiccontainer to pass a new cloned object to the JSON.stringify function instead of the embedded object.

SR-C91264 · Issue 433440

Localization fixed for dropdown sourced with pystate

Resolved in Pega Version 8.1.5

When pystate was used to source a dropdown, the options were all uppercase but in the review harness used lower case for IN and OR. This difference caused a failure in localization. This was caused by the Field value instance being defined in lowercase in PyCaption while the UI was treating the active value as an instance of pyCaption, leading to instances of both "in" and "IN" being present. This has been resolved by consolidating the field value to use a single case in the pega-eventprocessing ruleset.

SR-C91898 · Issue 435424

Resolved Rich Text Editor display in popup windows

Resolved in Pega Version 8.1.5

The Rich text editor was not displaying in popup windows although it did display otherwise. Investigation traced this to the harness context APIs used in "pega.contro.IRTE.init" (pzpega_control_richtexteditor.js rule) returning rteTextArea as null, leading to the RTE scripts failing to bind the ckeditor dom. This has been fixed by replacing the harness context APIs with ones better suited to this use.

SR-C91930 · Issue 439847

Corrected focus issue after form submit for SPA portal

Resolved in Pega Version 8.1.5

When a form was submitted in the SPA portal and the next form appeared after launching the case, if the second form's height was more than the screen size the vertical scroll bar was automatically moving to the bottom and the focus was given to the submit button. This has been corrected to the expected behavior of the focus staying on the first editable field.

SR-C92000 · Issue 437303

Updated date time format used pyPostEmailContent section to resolve exception

Resolved in Pega Version 8.1.5

When a pyPostEmailContent section in the Pega-Social ruleset was being referenced, the error messages "pub.util.PRDateFormat) ERROR - Cannot create format "MMM dd, yyyy hh:mm A", default format is used; java.lang.IllegalArgumentException: Illegal pattern character 'A'" was logged.This has been resolved by modifying the date time format used for the pyPostEmailContent section.

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