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.

INC-191533 · Issue 676100

Lifecycle widget added to Cosmos

Resolved in Pega Version 8.6.3

On opening the Cosmos portal and trying to modify the dashboard widgets, the UI-Kit widgets were visible and and those section's css styles were not getting added. This has been resolved by adding a lifecycle widget on Cosmos.

INC-191674 · Issue 681577

Cosmos Stakeholders menu updated to prevent loss of work party change

Resolved in Pega Version 8.6.3

The Stakeholders menu for adding work parties to cases available in Cosmos Utility panel was not saving work party changes as expected when the case was also open for performing assignments. When the assignment was completed, the work parties were reset to the values present when the case was opened. The list of stakeholders is saved as a property in work page. When an assignment is opened there are two threads, and any stakeholder added is then added only in the first thread. Because it was not added in the second thread (acprimary Ajax container - processing assignment) the stakeholder addition was lost due to the second thread overriding the first thread. To resolve this, if an assignment is being processed while trying to open the stakeholders model, an additional modal will be displayed with the following options: resign from opening stakeholders modal and continue process assignment or, resign from processing assignment (all unsaved changes will be discarded) and open stakeholders modal

INC-191725 · Issue 678863

"Close" icon shown in App Studio preview

Resolved in Pega Version 8.6.3

The 'Close" button was missing from the Marketing portal/CDH studio Content -> Actions details page. This was due to previous work that added a visibility condition to the close icon, and has been resolved by updating the condition to show the close icon in preview in App Studio.

INC-191785 · Issue 680931

Edit Validate Rule works after mobile section collapse

Resolved in Pega Version 8.6.3

It was possible to collapse a section of the UI on the mobile app and then proceed to the next page without entering valid data. This has been resolved by updating the validation condition to handle the mobile sections edit validate rule correctly.

INC-191985 · Issue 686765

Description field handling updated for delegated table

Resolved in Pega Version 8.6.3

A delegated table could not be accessed for work if the description was added in multiple lines. Investigation showed that during execution, the multiple lines of description caused the data transform pzManageDataModel to not be able to find the pyRuleName. This has been resolved by escaping the newline character so the description is treated as a single line during execution.

INC-192813 · Issue 684736

A setTimeout has been added before focusing the element to address the issue in Microsoft Edge, and

Resolved in Pega Version 8.6.3

When a value was changed in a section where the source of the section was defined as a property, the page refreshed without any announcement and focus was disrupted. Investigation showed this happened when using paragraph control where an anchor tag was used without any Name attribute. An update has been made to explicitly set the gFocusElement property after the processAdditionalFields activity to resolve this issue. Because the Name attribute is needed to query the particular element from the DOM to focus back, there were also intermittent issues when using the Microsoft Edge browser with Windows OS even after adding Name in the paragraph control link. A setTimeout has been added before focusing the element to resolve this.

INC-193047 · Issue 694049

Added handling for nested clipboard pages

Resolved in Pega Version 8.6.3

On save of sections that have items (cells) nested more than one layer deep and have either "Show menu" or "Run data transform" actions, silent errors were found in the tracer indicating "Attempting to access a rule with a bad defined-on class: Trying to open rule ... of class "Rule-Navigation", but no defined-on class (pyClassName) was specified". This was due to the pzActionShowMenu Rule-Utility-Function and pzActionRunDataTransform Rule-Utility-Function assuming the clipboard page structure was only one layer deep, and has been resolved by using findRulePageFromCurrentPage from SectionUtils.java .

INC-193650 · Issue 687903

Corrected focus for changing optimized table density

Resolved in Pega Version 8.6.3

Corrected focus for changing optimized table density

INC-193775 · Issue 686646

Action Sets in Sections working as expected

Resolved in Pega Version 8.6.3

When adding actions to a table, the action sets were not always saved correctly. Sometimes actions from one actions set were moved to a new action set without any event, which seemed to occur when there were multiple actions defined for each action set. This was traced to the open of the table property panel in the activity Embed-Harness-SectionBody-Grid.pzGridActionSets activity. This activity sets data for the action set display, including setting a “pyKeyCode” property. The “pyKeyCode” property is not set correctly in certain scenarios, causing the selected action/behavior to not be saved correctly. This has been resolved by changing the local param-pzGridActionSets: TempKeyCode to string.

INC-193947 · Issue 684138

Focus corrected for dynamic layout in mobile

Resolved in Pega Version 8.6.3

When any new item was added to a repeating dynamic layout in mobile or if the grid one of the items was expanded, the entire UI refreshed and the focus moved to the top. This has been resolved by adding a check for isMobileFullScreen.

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