SR-D3604 · Issue 439097
Parameter support added for openAssignment
Resolved in Pega Version 8.1.5
An enhancement has been added that will allow leveraging the Associate Requestor for Chat interactions through parameter support for the openAssignment action. This will allow an activity to be called to create the interaction and pass back the assignment and open it using the openAssignment API.
SR-D3767 · Issue 438201
Enhancement added to track list based report definitions for statistics
Resolved in Pega Version 8.1.5
In order to expand the use of pyDefaultReport for Log-ReportStatistics, an enhancement has been added to pzPopulateListReport to call the pzPopulateStatisticsInfo activity with the required parameters to enable tracking of list based report definitions so they can be included in the report statistics table.
SR-D3788 · Issue 437780
Corrected temp page reference for save-as in CreateAndManageWorkFromEmail
Resolved in Pega Version 8.1.5
Attempting to save-as pyCreateAndManageWorkFromEmail was failing due to a missing reference to TempCurrentPage in Pages and Classes. This has been corrected.
SR-D392 · Issue 438873
Behavior reset for using getLocalizedValue with an input string containing parentheses
Resolved in Pega Version 8.1.5
After upgrade, the getLocalizedValue function was not returning any value if the input string contained parentheses. This was a difference in behavior caused by a missed use case when correcting another issue, and has been resolved by resetting the system to the previous behavior of getLocalizedValue returning a localized string in cases where a Field value/Rule message is present, or otherwise returning the exact input string.
SR-D4025 · Issue 439630
Check added to ensure interactions show ID
Resolved in Pega Version 8.1.5
After creating many interactions, navigating to the interactions not visible on the screen using the "Currently open" menu displayed the interactions as New instead of the interaction ID. This has been resolved with the addition of a check for customer headers.
SR-D4027 · Issue 439899
Explicit property evaluation added to correct visibility in Proposition Management sorting
Resolved in Pega Version 8.1.5
After navigating to the Decisioning: Proposition Management landing page (Configure->Decisioning->Decisions-> Proposition management -> Hierarchy), opening any Decision data and then switching to the Form tab to perform any sorting on the Form fields grid caused the UI to become unresponsive and generate the error "Uncaught SyntaxError: Unexpected end of input at pega.ui.Doc.evaluateVisibleWhens". This issue was traced to a 'when' condition which demanded explicit mention of whether the property value had been evaluated as true or false, and that result has now been added.
SR-D4829 · Issue 439801
Corrected ADP sections rendering twice
Resolved in Pega Version 8.1.5
ADP sections were being rendered twice due to the inclusion of lazyloadinfo in pzModalAction which loaded multiple divs during the initial expand onload configuration of expand pane. This has been corrected.
SR-D4829 · Issue 439802
Focus issue corrected for multiselect lists navigation
Resolved in Pega Version 8.1.5
Keyboard navigation (arrow keys UP and DOWN) were not working in Microsoft Internet Explorer and Google Chrome after selecting the value by using a mouse click in a multiselect control. After selecting the value using ENTER, keyboard navigation began working again. This was an issue where clicking an element from multiselect list caused the focus to shift to the body, and has been resolved by shifting the focus to the input element when the multiselect lists are clicked.
SR-D5079 · Issue 438383
Handling added for empty UILabel in grid fields
Resolved in Pega Version 8.1.5
When using a Datetime property with a default format, opening the filter popup and clicking on the 'select all' check box caused the format of the values to break. This was traced to ".pyUILabel" being passed as empty, and handling has been added for that in "pzUniqueValuesGridFields".
SR-D520 · Issue 435487
Wait corrected for sub case after reopening
Resolved in Pega Version 8.1.5
A re-opened parent case was not waiting for the sub case when a sub case was reopened, but it did wait if there was no sub case on the reopened parent case. This has been resolved by enhancing the system to better handle the reopen of activator and dependent work objects by checking the reopen time: - pzGetAllStatusforDepClass activity: added step 2 to consider activator reopen time - pzGetMessageKeysForFlowDependencies list view: added criteria to filter on reopen time