INC-220715 · Issue 726415
Currency Code updates
Resolved in Pega Version 8.8
A Section configured with an editable currency input using auto-formatting failed to render at runtime if configured using Type -> Number, Symbol -> Currency, Other currency, and Currency -> "USD". The error "Invalid Locale : USD" was logged. This was an unintended side effect of work done to configure currency codes for the Number control, and has been resolved by accounting for the locale settings and handling the condition for the error "Invalid local-USD" so that the the UI rendering appears as expected. In addition, when the Currency control was configured with editable mode "Editable" and "Display value using read-only formatting" checked, read-only formatting generation did not happen for the control. Entering a value and tabbing out caused the ReloadCell activity to return empty content, which resulted in the server returning full HTML markup with a message "Operation Successful". Because the ReloadCell activity handler expected only control markup with formatted value to be returned, the HTML markup containing inline CSS styles in it appeared in the Currency input field on tab out. There was a workaround of unchecking "Display value using read-only formatting" on the control's presentation tab, but this has been resolved by using Post value infrastructure to get the formatted value from the server.
INC-220985 · Issue 728989
IsPropositionActive property retained during save-as
Resolved in Pega Version 8.8
When the action treatment was saved-as from a lower version to higher version, the treatment DDR form was missing the attribute "pyPropositionactive" property in the higher version. This was traced to the pyIsPropositionActive property being removed by the PreSaveAs activity of the DDR rule because it was considered not relevant for a non-proposition type decision data. This has been resolved by adding handling for the pyIsPropositionActive flag.
INC-220989 · Issue 719864
Improved accessibility on create harness
Resolved in Pega Version 8.8
Hitting the tab key was navigating out of the popup on the create harness. This has been corrected.
INC-221722 · Issue 739201
Menu button no longer steals focus on dismissal
Resolved in Pega Version 8.8
Action menus in the portal harness were stealing focus from input fields in the work harnesses. This was an unintended side effect of work done to correct an issue where focus was not correctly remaining in the table layout, and has been resolved by updating the control menu to avoid the explicit focus in the hideNode function when the menu is already dismissed.
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-221956 · Issue 721686
Archived cases with custom data viewable in ThemeCosmos
Resolved in Pega Version 8.8
Support has been added to ThemeCosmos to allow reviewing archived cases with custom data association.
INC-222553 · Issue 724226
Repaired Perform for 'Assignments with Errors'
Resolved in Pega Version 8.8
The 'Perform' button was not working on the "Assignments with errors" pop-up. This was an inadvertent side effect of changes made in 'pega_desktop_support' (Pega-Desktop ruleset), and has been resolved by adding a check before calling pega.mobile.isMultiWebViewPegaMobileClient.
INC-222769 · Issue 720982
Report filter popup displays correctly for UI kit applications
Resolved in Pega Version 8.8
Previous work done on the popover js to correct the filter popup placement and vertical and horizontal scrollbars for report columns has been further updated to handle the use case of UI kit applications.
INC-222784 · Issue 739536
BAC handling added for calling StartNewFlow activity from UI
Resolved in Pega Version 8.8
After modifying the pycaseactionarea submit button to call a flow that uploads a PDF to a third party system using the order action 1) Finish Assignment; 2) Call an activity and inside the activity call startflow to initiate the integration; and 3) Launch local action, clicking the button to finish the assignment showed only the first local action instead of the expected behavior of having a modal appear to the user to confirm that their file was successfully uploaded. An access control error also appeared. This was traced to the registration details being removed after generating the pdf with an activity running on a different thread, and has been resolved by adding a flag tools.putParamValue("skipResetQueryStringRegistration",true); in pzCreatePDFHarnessWrapper to avoid wiping the registration details and skip resetting the query string registration during the process.
INC-222800 · Issue 725125
Currency Code updates
Resolved in Pega Version 8.8
A Section configured with an editable currency input using auto-formatting failed to render at runtime if configured using Type -> Number, Symbol -> Currency, Other currency, and Currency -> "USD". The error "Invalid Locale : USD" was logged. This was an unintended side effect of work done to configure currency codes for the Number control, and has been resolved by accounting for the locale settings and handling the condition for the error "Invalid local-USD" so that the the UI rendering appears as expected. In addition, when the Currency control was configured with editable mode "Editable" and "Display value using read-only formatting" checked, read-only formatting generation did not happen for the control. Entering a value and tabbing out caused the ReloadCell activity to return empty content, which resulted in the server returning full HTML markup with a message "Operation Successful". Because the ReloadCell activity handler expected only control markup with formatted value to be returned, the HTML markup containing inline CSS styles in it appeared in the Currency input field on tab out. There was a workaround of unchecking "Display value using read-only formatting" on the control's presentation tab, but this has been resolved by using Post value infrastructure to get the formatted value from the server.