INC-142118 · Issue 597313
Data Migration Import/Export made more resilient
Resolved in Pega Version 8.6
The entire data migration operation (export or import) was marked as "FAILED" even if the operation failed for just one type of data. While managing the failure, the operation deleted any completed data flow runs as part of the clean-up and only retained the failed data flow runs for use in further analysis. Because the queued runs could not be deleted, the data migration case became a broken process. At the root of the issue, the data export work item was failing due to one or more DSM service nodes being non-functional based on a validation failure in the case type that runs a check for the presence of functional DSM nodes before starting the data migration operation. This validation can return false negatives, especially on Cloud where the nodes are usually swapped seamlessly without the function realizing it. In such cases, the validation function returned false despite the DSM service nodes being up and running. This has been resolved by adding handling for the failed data migration case by stopping and deleting the open data flows and by disabling the validation which checks for functional nodes.
INC-217680 · Issue 717605
Tab name displayed correctly in embedded mashup portal
Resolved in Pega Version 8.8
"Work Item" was given as as the tab header instead of the Case ID## when:a case link was clicked/opened in an application embedded in an external site (IAC). This was traced to the pega.desktop.support.doGadgetAction function not calling the regular handleGadgetLoad function in this scenario, and has been resolved by explicitly directing work items opened in a multi-doc mashup portal to use handleGadgetLoad.
INC-214338 · Issue 712497
Navigation updated for checkbox control in table cell
Resolved in Pega Version 8.7.2
Keyboard-only navigation was not working correctly when there was a checkbox control in a table cell. This was traced to the manageFocus function in the pega_ui_templatizedGridComponent js file which was setting the tab index to -1 when the checkbox value was updated. This has been resolved by skipping the execution of this function for checkbox control to handle the case when escape is not pressed before tabbing to come out of the table when there is a checkbox control in a cell.
INC-214338 · Issue 712499
Navigation updated for checkbox control in table cell
Resolved in Pega Version 8.8
Keyboard-only navigation was not working correctly when there was a checkbox control in a table cell. This was traced to the manageFocus function in the pega_ui_templatizedGridComponent js file which was setting the tab index to -1 when the checkbox value was updated. This has been resolved by skipping the execution of this function for checkbox control to handle the case when escape is not pressed before tabbing to come out of the table when there is a checkbox control in a cell.
INC-155648 · Issue 617395
Corrected reference of PropertyExists in pyAdjustSLAPostAction
Resolved in Pega Version 8.6
The PropertyExists function was returning incorrect results. This has been resolved with the addition of a 'property exists' check in pyAdjustSLATimes.
INC-205683 · Issue 702563
Data transform actions supported in offline app
Resolved in Pega Version 8.8
Support has been added for pre- and post-processing data transform functionality and validation in the local actions of the offline app.
INC-139130 · Issue 591861
Tab Headers accessible in Report Filter with keyboard
Resolved in Pega Version 8.6
Tab Headers such as "Available Values" were not accessible with a keyboard in the modal to select values for Report Filters. Instead, the focus marker directly shifted to content and toggling between Tabs was not possible. Investigation showed that at runtime for report definitions, the value for prevElement was null, which threw an error and caused the rest of the function to not run. This has been corrected by adding null checks for prevElement and newElement in the function tabClickCallback in the pega_report_events js file.
INC-225687 · Issue 739708
Handling added to avoid incorrect true value for DateTimeisPastOrFuture
Resolved in Pega Version 8.8
When the Function pxDateTimeisPastOrFuture() was called with the arguments "" (the empty String) and "false", it sometimes returned "true" instead of "false". This function internally calls the Function CompareDates() which takes two Strings as arguments. In this case, one is provided by the caller of pxDateTimeisPastOrFuture, the other one is generated at runtime, as the current date/time. As the second argument of pxDateTimeisPastOrFuture, the generated date/time will be the first parameter, while the second one is the date/time argument for pxDateTimeisPastOrFuture. If that argument is the empty String, is will be replaced by the current date/time. This means that the value for the second parameter is determined after the first parameter and that can result in a gap in time by a few milliseconds. This in turn results in "true" as the return value for pxDateTimeisPastOrFuture. This has been resolved by adding handling for a blank string so "false" is returned correctly.
INC-188127 · Issue 678350
Updated cache key generation for ROPC
Resolved in Pega Version 8.8
After configuring outbound email functionality using MSGraph with OAuth 2.0, sending the emails failed consistently following passivation. Running "Test connectivity" in the Email Account data instance then seemed to restart the functionality and the automation "Create And Send Email" subsequently worked. This was traced to a missing username in the cache key generation for the Resource Owner Password Credentials (ROPC), which caused the same token to be fetched when attempting to dynamically generate different usernames, and has been resolved.
INC-225257 · Issue 730293
Pega DateTime supports pre-1970 timestamps
Resolved in Pega Version 8.8
The function getTimeStampAsDateStamp from Pega DateTime class was not working correctly for dates before Jan 1st, 1970. Support has now been added for this use.