INC-189844 · Issue 673736
Scroll bar appears consistently
Resolved in Pega Version 8.6.3
The scroll bar was not consistently appearing beside the menus containing vertical overflow. This has been resolved by setting the correct max-height on the menu all the time.
INC-189935 · Issue 684505
Drag and Drop works as expected on mobile
Resolved in Pega Version 8.6.3
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-190609 · Issue 681325
Added null check for routeToParent in Mashup
Resolved in Pega Version 8.6.3
After update, mashup was loading in a different context. This has been resolved by adding a null check in routeToParent in webwb_pega_desktop_support.
INC-190708 · Issue 688134
Save works on Ajax container without Dynamic container
Resolved in Pega Version 8.6.3
After opening a work object and making changes to a required field, pressing the save button did not give any visual indication that the save was performed. Hitting cancel generated a dirty pop up saying changes will be discarded, indicating no save was done. When an Ajax container is configured without a Dynamic Container, all the content is rendered inside a fieldset tag instead of a form tag. While performing the save, the API was looking for the form element in the document and could not find any, and the save failed. This has been resolved by updating the submitWhenFail() API to handle both fieldset and form elements in the dom.
INC-190847 · Issue 676678
Preview link aligned under item
Resolved in Pega Version 8.6.3
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 683842
Corrected datetime placeholder handling
Resolved in Pega Version 8.6.3
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-191013 · Issue 683757
Number fields display the $ and % signs correctly
Resolved in Pega Version 8.6.3
After configuring a table with source as a page list and the fields with number control the symbol constant $ and % symbols were showing up as separate from the amounts in a cell. The $ symbol was all the way on the left of the field, and not aligned correctly with the number. The % symbol showed below the cell. This has been resolved by adding code for displaying the symbol inside the text input when the symbol alignment is configured as right.
INC-191160 · Issue 685379
Empty caption value not shown in dropdown list
Resolved in Pega Version 8.6.3
An update has been made to template_dropdown to restrict an empty value from being added to the list.
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