SR-A97665 · Issue 265978
ResumeFlow updated to handle SLA update in batch mode
Resolved in Pega Version 7.2.2
When any assignment configured with SLA was resumed by any agent in batch mode, the associated record in the pr_sys_queue_sla table was not getting deleted. To resolve this, the deletion method used in CompleteAssignment has been updated.
INC-153537 · Issue 614847
Corrected popup placement for Microsoft Edge browser
Resolved in Pega Version 8.4.4
Autocomplete, date control and SmartInfo pop-ups were not displayed correctly when using the Edge browser. This was due to Javascript behavior differences with that browser, and has been resolved by updating the system to ignore the scrolltop if browser is Microsoft Edge.
INC-144311 · Issue 601108
Updates for nested "Append And Map To"
Resolved in Pega Version 8.5.2
Nested actions "Append And Map To" in Data Transforms were producing incorrect results when offline. This was traced to all operations being performed on the Page List which was on first level of nesting, which was caused by changing the Data Transform into JavaScript form for offline use. The JavaScript form of DataTransform uses variable the "targetListObj" to represent the Page List, and this same name was reused regardless of the "Append And Map To" nesting. An additional problem was seen with the "Update Page" Data Transform action when used with conjunction with a nested "Append And Map To" action: the action assumes that top level Pages exists, but "Update Page" did not create them. This caused the "Append And Map To" action to fail. To resolve this, the "Append And Map To" action will use suffixed variable names to reference nested PageLists, and "Update Page" will create the Page if it doesn't exist.
INC-144311 · Issue 601110
Updates for nested "Append And Map To"
Resolved in Pega Version 8.4.4
Nested actions "Append And Map To" in Data Transforms were producing incorrect results when offline. This was traced to all operations being performed on the Page List which was on first level of nesting, which was caused by changing the Data Transform into JavaScript form for offline use. The JavaScript form of DataTransform uses variable the "targetListObj" to represent the Page List, and this same name was reused regardless of the "Append And Map To" nesting. An additional problem was seen with the "Update Page" Data Transform action when used with conjunction with a nested "Append And Map To" action: the action assumes that top level Pages exists, but "Update Page" did not create them. This caused the "Append And Map To" action to fail. To resolve this, the "Append And Map To" action will use suffixed variable names to reference nested PageLists, and "Update Page" will create the Page if it doesn't exist.
SR-A101848 · Issue 270084
Obj-Browse accepts Embedded Code-Pega-List
Resolved in Pega Version 7.2.2
Trying to reference a Property of Page Code-Pega-List in an activity using Obj-Method activity generated an error when executing, indicating that an invalid page name was passed. However, according to the Obj-Browse method help screen, there is no restriction on whether this page has to be top-level or embedded. After analysis it was determined that the code did not previously allow embedded pages in obj-browse, and this has been added to support this use.
INC-132569 · Issue 595174
Resolved case detail overwrite
Resolved in Pega Version 8.5.2
In the interaction portal, when the same property (dropdown) was used to populate the details of sections in two cases, the first section (email case) details were replaced by the second section (outbound call case) details. Investigation showed that the refresh API was getting the reloadElement in the entire DOM based on the event target name property. To resolve this, updates have been made to use context DOM APIs to get the correct section.
SR-A87242 · Issue 255987
Removed secondary encoding in GetLocalizedValue checkbox
Resolved in Pega Version 7.2.2
When using a field value that referenced the GetLocalizedValue control to populate the caption of a checkbox, special characters were encoded on the UI. This behavior did not occur for simple labels. This was due to a second encoding step which has now been corrected.
INC-134188 · Issue 576731
XML Parse handles dates with time zone correctly
Resolved in Pega Version 8.4.4
Due to a difference in data mapping behavior for Date values, the Parse XML new assembler implementation was incorrectly applying the DateTime type of processing for Date inputs when using timezones and silently ignored the exceptions reported. This has been resolved.
INC-139086 · Issue 597144
"Show next error" correctly displayed on user portal
Resolved in Pega Version 8.4.4
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.
SR-A89637 · Issue 259256
Search for Work gadget updated to accept "StartsWith"
Resolved in Pega Version 7.2.2
When using a fixed portal, the Search for Work gadget was not working for the option "Starts With" when pxOperatorMap rule was being called from newly added Property-Map-Value methods. This was caused by pxOperatorMap not having a return value for StartsWith, causing the default value"=" to be returned. This has been fixed by adding a return value for "StartsWith", "NotStartsWith", "EndsWith", "NotEndsWith", "Contains", "NotContain", "IsNull", and "IsNotNull" in pxOperatorMap.