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-115896 · Issue 167322

Corrected flow handling for failed tickets

Resolved in Pega Version 7.1.7

Raised flow tickets using pre-existing flow-ticketed utility shapes were intermittently failing to transfer to the expected place in the flow. This was found to be an improper copy action in the task, and has been corrected. The error message has also been clarified.

SR-115912 · Issue 168208

Updated failure handling for Word editing with IE

Resolved in Pega Version 7.1.7

When using IE, failure to load correspondence for editing in Word generated the message "Error: Loading Open Authoring Control". This was caused by the carried-over use of a span tag that is not valid under HTML5, and has been corrected with updated JavaScript.

SR-115931 · Issue 169804

Fixed read-only cascading dynamic select in Google Chrome

Resolved in Pega Version 7.1.7

The cascading dynamic select was not working in Google Chrome with ReadOnly Mode. This was traced to an error in the dynamicselect.js, and has been corrected.

SR-115934 · Issue 170092

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

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-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.

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