INC-190847 · Issue 676677
Preview link aligned under item
Resolved in Pega Version 8.7
The preview option was not showing below the link control configured to open the case, but instead was displayed elsewhere on the page. This was traced to changes made in Google Chrome v.93+, and has been corrected by changing the perspective to none instead of 0 so the link is displayed in the expected location.
INC-190901 · Issue 683841
Corrected datetime placeholder handling
Resolved in Pega Version 8.7
On desktop, date fields values selected were displayed in placeholder color instead of the black color. Date fields placeholders were not displayed in the offline mobile app. Before the refresh section call happened, the date selected color for the datetime input was black since the placeholder class was being removed from the span tag after selecting the date. After the refresh section calls, the Span tag which was generated for date time control was being appended with the placeholder class, which was an incorrect behavior. To resolve this, a check has been added which will only add the placeholder class if the datetime inputvalue is empty.
INC-191533 · Issue 676103
Lifecycle widget added to Cosmos
Resolved in Pega Version 8.7
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 681576
Cosmos Stakeholders menu updated to prevent loss of work party change
Resolved in Pega Version 8.7
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 678862
"Close" icon shown in App Studio preview
Resolved in Pega Version 8.7
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-191933 · Issue 684576
PDF generation corrected
Resolved in Pega Version 8.7
Issues with PDF generation have been resolved by upgrading the PD4ML libraries to version 4.0.9fx5.
INC-191985 · Issue 686764
Description field handling updated for delegated table
Resolved in Pega Version 8.7
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-193650 · Issue 687904
Corrected focus for changing optimized table density
Resolved in Pega Version 8.7
After selecting an option on the density filter button inside of an optimized table, the focus was set to the top of the browser rather than remaining inside the table layout. This has been resolved.
INC-193775 · Issue 686645
Action Sets in Sections working as expected
Resolved in Pega Version 8.7
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-193861 · Issue 683114
PDF generation corrected
Resolved in Pega Version 8.7
Issues with PDF generation have been resolved by upgrading the PD4ML libraries to version 4.0.9fx5.