SR-A82337 · Issue 256391
Optimized properties populated in exposed columns
Resolved in Pega Version 7.2.2
After using the property optimization wizard to expose a property in a higher class, the column was not populated with data for existing instances of lower classes that used that property even though the column population job ran on those classes. The column was also not populated when new instances of the lower classes were created. This was an issue where the API was using different update methods for optimized and regular properties, causing propagation problems. HandleSchemaUpdates has been modified to update the class map for all the classes mapped to the table instead of just the class name with which the API is invoked.
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-221955 · Issue 719288
Archival association supported without data retention policy
Resolved in Pega Version 8.8
Previously, configuring an archival association when the data retention policy had not been created resulted in an error and the associations were not saved. Handling for this use has now been added in order to support the archival of custom-associated data.
INC-234874 · Issue 739874
Cursor moves via arrow buttons
Resolved in Pega Version 8.8
Using the keyboard arrow buttons to navigate between numbers was not working. Nothing happened when clicking on the left arrow, and clicking on the right arrow moved the cursor to two digits. This has been resolved by updating pzpega_control_textinput.
SR-A86522 · Issue 266946
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.
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-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-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.