SR-C84361 · Issue 437599
Added handling for better recovery and reset when using 'When' conditional row deletion
Resolved in Pega Version 8.3
Given a 'When' condition configured so that a specific row could be deleted, trying to delete another row resulted in the expected error indicating it was not possible to delete that particular row. However, attempting to then delete the row with the 'When' condition caused the same failure error to appear which could not be cleared through clicking on the Refresh button for the section. In order to resolve this, handling has been added for a scenario where Obj-Delete fails and the record is marked for deferred commit. In this situation, the system will revert Obj-Delete by way of Obj-Save-Cancel in @baseclass.pzDeleteRecord so that a subsequent Obj-Delete does not pick up the previous record and fail again.
SR-C93726 · Issue 435285
Work status icons work correctly when using localization
Resolved in Pega Version 8.3
The pyWorkAssignmentStatus control was not displaying the status flags/icons for localized work status values due to a match failure caused by the system using the localized text for the pyAssignmentStatus to perform a string comparison against the hard-coded English values. To correct this, the control pyWorkAssignmentStatus has been modified to run the comparisons with the new string "assignmentStatus" instead of with the localized text.
SR-C89541 · Issue 430728
Case Manager email correspondence opens when encryption and obfuscation are used
Resolved in Pega Version 8.3
If the urlEncryption (true) and submitURLObfuscation(required) settings were enabled, it was not possible to open correspondence emails sent in Case Manager portal. No issue was seen when submitURLObfuscation was set to "optional" (which allows the server to accept URLS with either clear-text or obfuscated strings). Investigation showed the obfuscated values for pyActivity were not part of the HTTP request generated when the Data-Corr-Email attachment is clicked, leading to the system blocking the pop-up window request. Because bEncryptURLs, which is being set in the fragment DesktopWrapper_Variables, is not available in the harness context, the SafeURL method toURL therefore was not encrypting the URL. This has been resolved by setting both bEncryptURLs and pega.ctx.bEncryptURLs to true in the HTML fragment.
SR-D16327 · Issue 487448
Updated logic for Bulk Upload count when background processing is used
Resolved in Pega Version 8.3
When multiple items were queued as part of "Bulk Upload" and the "Transfer To" operation was used with "BULK PROCESS in BACKGROUND", discrepancies were seen in the email received. For example, if two items were selected for transfer, email notifications stated that 1 item was selected and 1 item was processed instead of 2. This was traced to using 'process in background': when selected during bulk processing, the first record is processed in the foreground and remaining records are processed in the background. When the system sent the email notification once the background process was done, the total records computation was not considering the foreground-processed record, and the count was off. The timing logic has been updated to account for the foreground record to resolve this.
SR-C67397 · Issue 421637
Added check for missing rule data when using abstract class in CSS
Resolved in Pega Version 8.3
Including CSS optimization with abstract class in the Advanced tab of the 'Add Optimization' Screen resulted in a Null pointer exception error. This has been resolved by adding a check for missing data from a rule to make the system more resilient in its handling of a corrupt flow-action clipboard page.
SR-D5413 · Issue 484328
Enhanced returned value handling for using Expand when in collapsible dynamic layout
Resolved in Pega Version 8.3
After configuring an 'expand when' condition with the intention that the dynamic layout expands when the user doesn't enter the required field(@hasMessages(Primary)), the dynamic layout was expanded by default even though the "Expanded on load" was not enabled. This was traced to 'expand when' not getting set on refresh due to a different returned value for the condition, and has been corrected.
SR-D15391 · Issue 484920
Add row works as expected when using Embedded Elsewhere with a modal grid
Resolved in Pega Version 8.3
When using Embedded Elsewhere, add row was not working on the first attempt for a grid launched inside a modal dialog. Changing the focus then resulted in the added row appearing. This has been resolved by updating the timing for the performInsertAction in the ui_grid JS.
SR-D17122 · Issue 487599
Updated code to resolve PMS variable errors when using the iframe container
Resolved in Pega Version 8.3
After building the iOS application using “Reuse web portal” (under channels & interfaces > layout) and with the default settings application, the Dashboard, My Work, and Pulse sections were not rendered and the error "Can't find variable pms" appeared. This happened only when the iframe container was used, as the pms object (PIMC API) is always injected into top window and does not exists in child windows like iframe embedded in a page. In order to ensure that undefined variable pms does not break the rendering, the code has been updated to use top.pms for all pms occurrences to avoid errors when API is invoked from iframe.
SR-C97873 · Issue 437280
Added check to maintain key value when using collapseAllMenu in child navigation menu
Resolved in Pega Version 8.3
After a navigation menu had a child added as reference navigation menu that used the function collapseAllMenus, the screen was freezing if a link was clicked in the added child navigation and a javascript error appeared on the console screen. This was traced to an improper key being set in sessionStorage object in setItem due to the nesting, and has been corrected by adding a check in sessionstorage setitem to maintain the proper key value.
SR-D15089 · Issue 485330
Handling added for single quotes in custom DateTime controls when using Export to Excel
Resolved in Pega Version 8.3
A previously resolved issue with the timezone not being appended to datetime when exporting to Excel if a custom control was used has been further updated to better handle single-quote strings in custom DateTime controls.