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-115934 · Issue 174331

Corrected deadline escalation for reassigned work

Resolved in Pega Version 7.1.7

When reassigning work with an escalating deadline, the reassignment flowed properly but the corresponding SLA queue item was deleted after reassign and passed deadline events defined in the SLA rule were not triggered. This was traced to the new queuepage being created with a different processEvent activity, meaning Queue Manager could not locate it. A check has been added to ensure the correct queuepage is attached to reassigned work.

SR-115985 · Issue 169316

System updated to handle partially encrypted URLs

Resolved in Pega Version 7.1.7

With URL encryption enabled, certain work types could not be loaded due to an inability to process the partially encrypted URLs. The JavaScript has been updated to correctly handle these URLs.

SR-116025 · Issue 174180

Corrected ability to add rows to a Row Repeat Grid Layout

Resolved in Pega Version 7.1.7

Previously, an error was generated when attempting to add more than 51 rows to a Row Repeat Grid Layout with two more layouts containing other fields. This was caused by a duplicate call to invoke the list section, and has been fixed.

SR-116042 · Issue 170124

Updated newline character for HTML

Resolved in Pega Version 7.1.7

On click-submit, some text paragraphs were being displayed without breaks between them. This was caused by a missing HTML tag and has been corrected.

SR-116153 · Issue 165729

CaseTypeValues correctly created for child cases

Resolved in Pega Version 7.1.7

CaseTypeValues were not being properly set on the child case when it was added to the cover through agent creation, causing the trigger not to execute because the change was not detected. Manual creation was detected properly. This inconsistency was traced to the agent using the AddToCover activity vs. the manual creation using AddChildWork, and has been corrected.

SR-116209 · Issue 166698

Backslash '\' now showing as expected in autocomplete and search

Resolved in Pega Version 7.1.7

The AutoComplete control was filtering out backslash '\' characters when displaying the values in the list of matches, causing failures with search and autocomplete. The Rule-Utility-Function for the getProperty has been corrected to allow '\' to be handled properly.

SR-116242 · Issue 171896

Work item correspondence loading fixed for IE11 Enterprise

Resolved in Pega Version 7.1.7

When trying to view correspondence attached to a work item, using IE11 in Enterprise mode, an error "Error: Loading Open Authoring Control" is generated. This was caused by the Open Authoring ActiveX control APIs used by the correspondence viewing functionality: the currently used method of verifying that an ActiveX control has been successfully loaded into the HTML page was not working in IE11 Enterprise mode, and has been updated.

SR-116272 · Issue 168880

Java error resolved for Smartinfo in list view

Resolved in Pega Version 7.1.7

A JavaScript error was being generated in IE8 after viewing the Smartinfo popup with a list view. This was caused by calling the focus API on top of an invisible element, and has been fixed.

SR-116347 · Issue 166799

Error resolved for adding Stage Step Specifications using RTE and Google Chrome

Resolved in Pega Version 7.1.7

While configuring a stage behavior in Google Chrome, if a user had focus within the Rich Text Editor for a specification and submitted the modal, an error was generated. This was caused by an invalid post-value check, and the unnecessary post value has been removed.

SR-116359 · Issue 169895

Dynamic select modified to use display value instead of property value

Resolved in Pega Version 7.1.7

If two different properties were used for display and values in Dynamic select, the value property was shown instead of the display value. This has been corrected.

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