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-115808 · Issue 169924

Instantiation logic enhanced

Resolved in Pega Version 7.1.7

In an application with a parent case (CaseInstancePOC) and two lower levels of cases (Case_Level2 and Case_Level3), the top level case starter flow CaseInstancePOC creates multiple subcase instances of type Case_level2. This is caused by automatic case instantiation of Case Level3 based on Case level2 Work Status - Open being configured. In some cases, this may not be the desired behavior. For example, when there are two Case_Level2s and one work status is changed to Open, the user may want a child case to be instantiated for only that particular Case_Level2and not the other Case_Level2. To allow more flexibility, an enhancement has been added to limit scoping through the AddChildWork setting.

SR-115839 · Issue 166347

Corrected radio button visibility behaviors

Resolved in Pega Version 7.1.7

Previously, some erroneous behaviors were seen with the visibility of a mandatory radio button when used in conjunction with a conditional read-only option. This has been resolved by a recent change that makes the "Required" checkbox a dropdown, fixing the design time issues.

SR-115896 · Issue 167002

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-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-115955 · Issue 167257

Enhanced task queue handling for custom applications

Resolved in Pega Version 7.1.7

In some situations, a custom agent would periodically fall over when processing a large backlog of queued items. This was caused by an exception thrown when placing a task in the queue when it is already present. The system has been updated to better handle this situation and allow agents to continue to execute with the present schedule when a duplicate task is found.

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