SR-C74648 · Issue 422904
Autocomplete arrow placement corrected in Right to left local mode
Resolved in Pega Version 8.3
When using the Autocomplete control, the blue arrow was seen to have an incorrect placement/orientation in RTL mode. This was traced to the autocomplete background-image in RTL mode being the same as that for LTR, and has been resolved by adding specific background-image for RTL.
SR-D37326 · Issue 504935
Resolved clipboard formatting issue in Reply Thread and Send Correspondence
Resolved in Pega Version 8.2.4
Issues were seen with the table formatting of client data after mail was sent. This has been resolved by ensuring all borders are retained in RTE when used in both "Send Correspondence Task" and "Reply Thread".
SR-D42143 · Issue 509316
Tab names maintained after Ajax container refresh
Resolved in Pega Version 8.2.4
When using an Ajax container in Tabs mode, a browser refresh with multiple tabs opened caused the active tab name to be changed to the main tab name. This was caused by the work object name being lost during the refresh, and has been corrected.
SR-B34850 · Issue 297938
Dirty warnings properly cleaned up
Resolved in Pega Version 7.3
After displaying a dirty warning on screen, the warnings remained even when navigating to other screens. This was caused by the complex element used to display the warning not being cleaned up, and has been fixed by refining the HTML markup to ensure proper handling.
SR-B42305 · Issue 299199
Parse-XML generation updated for complex XML element
Resolved in Pega Version 7.3
When generating the datamodel using the REST wizard, if the response XML had a page with type attribute then the value was ignored at run time. This has been fixed with updates to the "RuleGeneratorREST.java" for data model generation and "ParseXMLSAXRuleWrapper.java" for run time handling.
SR-C91492 · Issue 430456
Focus issue corrected for multiselect lists navigation
Resolved in Pega Version 8.3
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-C76417 · Issue 430545
Check added for reference function in DB2 join
Resolved in Pega Version 8.3
In DB2, when a sub-report column contained a function that was used for a join condition in the main report, an invalid filter property error was generated while saving. This was traced to the edit validate rule checking for the data type of both of the properties used in the join, and has been resolved by adding a check to see if the join operand is of function 'reference'; if so, the system will resolve the function, check for data type property, and set it.
SR-C91274 · Issue 481706
Corrected Base64Decode calculations
Resolved in Pega Version 8.3
Testing indicated that a file encoded using Base64Encode generated the error "The Operation completed successfully, but returned no content" when decoding with Base64Decode. Validating the content of the text file via a JSON validator using text formatted as JSON worked as expected. Investigation showed that extra padding characters were being appended due to calculations around CRLF characters, and this has been corrected.
SR-D33445 · Issue 505994
Handling added for context switching with Ajax container in Timeline
Resolved in Pega Version 8.2.4
When using Interaction Portal -> Overview -> Timeline and opening a case that uses an AjaxContainer, clicking on an icon in the Timeline without having first clicked anywhere in the document was generating an exception. If there was a click in the document body first, clicking on the icon worked as expected. This has been resolved by adding a parameter to registerContextSwitching method to handle customeDOMEvents along with a condition to check if pega.u.d.isAjaxContinerExists is a function, which will register the Context if 'true'.
SR-B8696 · Issue 279855
Support added for FCM GetNextWork
Resolved in Pega Version 7.3
When using Federated case management (FCM) to get next work, the work object pulled was not assigned to the operator. This was due to the implementation of FCMR not supporting the moving of workbasket assignments to worklist through get next work. To support this use, the following functions now accept extra parameters as last param: FCMRGetNextWork FCMRGetNextWorkItem FCMRProbeNextWorkItem This will enable distinguishing between normal GNW and federated GNW, and it is possible to override any py rule call MoveToWorklist.