INC-188605 · Issue 673597
Missing property added for permission check on CanPerformAssignment Go button
Resolved in Pega Version 8.7
With the introduction of the pzCanPerformAssignment When Rule to control the visibility of the Go button in the Assignment lists, the context for checks is now within the D_CaseAssigments Data Page. One of the checks executed by this When Rule is performed by the function @pzCanPerformAssignment() which calls an API to examine the RARO configuration for the Assignment Class in question. When the Read permission is controlled by the canPerform Access When Rule, a function is called which relies on the presence of the .pxRefObjectClass to check the privileges; In the new D_CaseAssignments Data Page the .pxRefObjectClass was not mapped during construction and as such the value for workClass passed to the API method was "" meaning the relevant checks were not executed. This has been resolved by adding the missing property pxRefObjectClass that is needed for execution permission checking.
INC-189047 · Issue 674759
Session timeout adjusted for use with Apple Safari
Resolved in Pega Version 8.7
A configured browser session logout timer was not working with the Apple Safari browser. This was traced to browser-specific handling for self.location.href and has been resolved by adjusting the logic and moving it inside a setTimeout to improve cross-browser compatibility.
INC-189214 · Issue 675959
Improved backwards compatibility for sendmail notifications
Resolved in Pega Version 8.7
After upgrading from Pega 7 to Pega 8, sendmail notifications were not working for email addresses that included the to-form "Lastname, Firstname'. This was caused by a difference in handling within the activity "@baseclass.SendEmailNotification", and has been resolved by shifting the reliance to InternetAddress.parse for validating and splitting email addresses in order to handle special characters, commas, and semi colons in display name.
INC-189935 · Issue 684504
Drag and Drop works as expected on mobile
Resolved in Pega Version 8.7
After opening a case assignment on a mobile device and selecting an option on the correct fields to make the drag and drop section visible, dragging the object vertically the caused the entire page to scroll up and down. Horizontal dragging worked as expected. This has been corrected.
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.