SR-D3405 · Issue 439260
URL construction logic updated for Tracer
Resolved in Pega Version 8.1.5
When trying to trace a requestor from the requestor management landing page, a 400 bad request error was generated. Investigation showed that when forming the tracer URL, the pxRequestor.pxRequestorPathInfoInReal property was being appended to it. Because the property contained unencoded characters([), the request was not being processed. To resolve this, the URL construction logic has been changed to use pxThread.pxReqBaseURI.
SR-C89463 · Issue 433822
Corrected tab name handling in Report Browser
Resolved in Pega Version 8.1.5
When using the report browser, refreshing the page after subscribing and unsubscribing to a report changed the tab name to the task id (eg. "PX-ST-123") and an extra tab appeared. This has been corrected.
SR-D5309 · Issue 438880
Merge multiple branches tool updated to resolve selection error
Resolved in Pega Version 8.1.5
When an application was configured to not allow branches to be merged without being reviewed, the "Merge multiple branches" tool did not allow any branches to be selected even if they had been reviewed. This was traced to the pzLoadBranches activity using local.reviewStatus even though the local variable was not required in this case. To resolve this, the activity has been modified to use Param.reviewStatus to pass the parameter page to pzSetBranchReviewStatus activity. If the 'when' rule pyAllowMergeWhenNotReviewed is set to false, the checkbox will be enabled for branches which are reviewed. For branches which are not reviewed, the checkbox will be disabled and the message "Please review the branch before merge" will appear.
INC-153805 · Issue 627969
Mobile app language remains consistent after data sync
Resolved in Pega Version 8.5.3
When using a Field Service Mobile App where the locale of all workers was set to nl_NL, the UI was intermittently flipping from NL to EN and and back again. This was traced to the locale of the requestor (field worker) being lost during synchronization of the mobile app data to the server, causing the UI to fall back to the default value of EN. This has been resolved by ensuring the requestor always uses the chosen locale for the operator.
INC-157699 · Issue 624596
Customer 360 Tabs load in Firefox browser
Resolved in Pega Version 8.5.3
After upgrade from v8.1 to v8.4, the layout group's tab content was not loading as expected in the customer 360 view when using the Firefox browser. Investigation showed this was due to the �role� attribute being removed from the header div by the on-hover showSmart tip action configured on the dynamic layout tabs. This has been resolved by updating the system to use data-role along with the role tab.
INC-139086 · Issue 597146
"Show next error" correctly displayed on user portal
Resolved in Pega Version 8.5.3
In the Case Worker user portal, the Show Next Error link was not shown when the layout group had a validate rule in the flow action. The same configuration worked as expected in Case Manager. This was a missed use case, and has been resolved.
INC-144778 · Issue 619615
Performance improvements for Ajax tab switching
Resolved in Pega Version 8.5.3
When using a 360-view of members in a portal implemented with an Ajax container that showed information in multiple tabs, tab switching was taking a lot of time even though the data was already in the memory. Updates have been made to improve performance.
INC-157041 · Issue 626312
Performance improvements for email listener processing
Resolved in Pega Version 8.5.3
Email processing was taking an excessive amount of time when a very large number of email listeners were running. Performance has been improved by updating the implementation of pzGetChannelByName to use obj-browse instead instead of looping through channels.
INC-155752 · Issue 622772
Hidden Question pages and answers will be saved to database
Resolved in Pega Version 8.5.3
After a question page was shown and some values were entered, going back to the question and reverting an option caused the question page to not be visible, but the answer values persisted in the clipboard and were eventually saved into the database. This was a missed use case for Question page smart shapes, and has been resolved by updating the pzSetQuestionPageParams data transform so that whenever a question page is evaluated to either to show/hide, when the question page visibility is set to false and the pyClearAnswerValuesWhenQPHidden 'when' rule is overridden, the corresponding values will be wiped from the clipboard and only the required values will be saved to the database. However, please note this is not supported for branching logic and visibility conditions should be used instead.
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.