INC-174045 · Issue 650735
DSS added to control merge strategy
Resolved in Pega Version 8.5.5
The activity page merge option takes merge strategy as input and supports different merge strategy options like 'Replace', 'Update' etc. Previously, V1 DX APIs defaulted to REPLACE as the merge strategy; this has been updated to support both 'REPLACE' and 'UPDATE' merge strategies which can be controlled with the new DSS "v1MergeStrategy". The DSS to customize the merge strategy for v2 APIs is 'v2MergeStrategy', which also takes the values 'REPLACE' and 'UPDATE', which are for merge strategy '1' and '3' respectively. The default strategy from Pega 8.6 forward is 'UPDATE' and any other value other than the above two values will be considered as 'UPDATE'.
INC-174267 · Issue 657129
Wait action persists when using Urgency Adjustment
Resolved in Pega Version 8.5.5
When using the Urgency Adjustment (pyAdjustAssignmentsla standard local action), once a case reached the wait action and the goal and deadline were updated the previous pyWaitAction was not being stored. This has been resolved by ensuring the previous pyWaitAction will be stored and passed to the AddAssign activity.
INC-174511 · Issue 653620
Attachment errors correctly triggered for subsequent copies of the same file
Resolved in Pega Version 8.5.5
After attaching a file larger than 4MB and triggering a dirty popup error, uploading the same file again did not trigger the error. This was traced to the onChange event of the File Input Tag not being triggered when the same file is attached again, and has been resolved by adding handling for attaching the same file in error scenarios (File Max Size,File Size Zero).
INC-175151 · Issue 658699
Bulk Actions filter working for embedded date properties
Resolved in Pega Version 8.5.5
For Embedded DateTime properties, the pyStringType was returned as "Date Time" instead of "DateTime", causing a mismatch in the filter criteria for Bulk Processing. This has been corrected.
INC-175630 · Issue 653862
Application selections only announced when visible
Resolved in Pega Version 8.5.5
The elements of the application switcher were being announced by the NVDA screen reader even when toggled off, i.e. not visible. The issue was occurring because the focus was remaining at the search bar even after closing the app switcher window, and has been resolved by adding the necessary logic to switch the focus.
INC-175882 · Issue 658640
Updated bulk action audit history logic and security
Resolved in Pega Version 8.5.5
After update, using the standard bulk action feature did not record an audit history entry for the SLA action on a case. This was traced to changes made around authorization for opening worklists when using pzBulkProcessItem that limited the audit history to reassign, transfer or transfer assignment, and has been resolved by updating the login the Work-pzBulkProcessItem activity. In addition, the Require authentication to run checkbox has been enabled on the Security tab of the activity, and the Allow invocation from browser checkbox has been disabled.
INC-168254 · Issue 659299
Documentation updated for accents and special characters used in search
Resolved in Pega Version 8.5.5
The "Pega search API" article has been updated to reflect that the search functionality in Pega Platform does not match accented words with unaccented. For example, searching for santé and sante will retrieve different results. In addition, Domain Specific Language (DSL) includes special characters for use when searching, for example '-', '_', '!', '@'. However, the system retrieves various results depending on the way the special characters are used in the search query. If the query contains special characters that are not escaped, the system may retrieve incorrect results. For example, not escaping the slash mark in the 25/02 query may cause the system to ignore the special character.
SR-D5904 · Issue 490489
Discard changes dialog now showing for local actions
Resolved in Pega Version 8.1.7
After having modified case data without saving and clicking on a menu entry (left menu, search, ...), the system shows a dialog box to ask the user to confirm it is ok to discard changes. However, this confirmation dialog did not work with local actions, leading users to lose their work without any warning nor any way to step back. This was traced to a difference in the dirty form check, which was not present when launching a local action from a case. An enhancement has now been added to the handleMenuAction js function in pypega_ui_harnessactions.js which will perform a dirty form check with a prompt.
SR-D23723 · Issue 503090
pxGenerateExcelFile updated for handling blank dates
Resolved in Pega Version 8.1.7
When using a custom template for exporting to Excel, blank DateTime property column values defaulted to the current date. To resolve this, the pxGenerateExcelFile activity has been updated to ensure that an empty date will be exported as blank and that given dates will appear in the correct datetime format.
SR-D24950 · Issue 494566
Added explicit step page to resolve null-pointer exception with custom error message
Resolved in Pega Version 8.1.7
A null pointer exception was generated during case run time harness refresh after a custom error message was inserted. This was traced to a blank step page related to the custom message, and has been resolved by adding a primary step page at step 10 of the New(Work-) activity to prevent the null-pointer exception on harness reload.