SR-C84361 · Issue 437601
Added handling for better recovery and reset when using 'When' conditional row deletion
Resolved in Pega Version 8.1.5
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-C84981 · Issue 437816
Setting added to compensate for data volume removed during Cassandra restart
Resolved in Pega Version 8.1.5
The DSM/service/replace option was not working correctly for DDS Service if the data volume was not present, causing an issue with being able to perform a rolling restart of DDS nodes when a data volume was removed as part of restart. This has been resolved by Introducing a dnode/cassandra_replace_ip setting that results in adding the cassandra.replace_address_first_boot environment setting to the Cassandra process. The setting is taken into account only if the data volume (cassandra_data) is not present.
SR-C86589 · Issue 436267
Added explicit thread cleanup to resolve case worker portal UI rendering problem
Resolved in Pega Version 8.1.5
Creating a case in the case worker portal was resulting in the respective screen being rendered with a distorted UI. This was traced to an issue in topnavigation where the thread was being changed to a base thread and skipping the FlowModalProcess thread removal when the new DC action was triggered. To resolve this, the system has been modified to append "$FlowModalProcess" in harnessOnBeforeUnload if it is missing to make sure the FlowModalProcess thread is removed.
SR-C86607 · Issue 436442
getProperty API updated to use the pega.ctx.dom API for get element by name
Resolved in Pega Version 8.1.5
When multiple tasks (S- Cases) were added from an interaction (I- Case) and the Service Cases had three auto complete controls which were sourced by parameterized data pages, it was expected that upon selection of the first auto complete, the second and third auto complete values would be populated. However, parameters passed to the Data Pages from the second and third S- Cases, had the same value as the first S- Case even though the clipboard was correct. Investigation showed that with MDC, the pega.util.dom API was failing to get the correct dom element and the needed data pages were not called. This has been corrected by updating the getProperty API to use the pega.ctx.dom API instead of the ega.util.dom API to get element byname.
SR-C89040 · Issue 438829
Calling flow correctly resumed after sub-process completes
Resolved in Pega Version 8.1.5
If a case was processed via Operator1 and passed as an assignment to a workbasket where Operator2 picked it up and performed a Reject case on it, the process in Flow1 correctly called Flow2, but once Flow2 was processed Flow1 was not resumed. If Operator2 only performed the Reject processing, Flow1 was resumed. To to ensure the correct flow resumption, the location of the pyFirstRun setting in flowMethodBody FUA has been updated.
SR-C89135 · Issue 434748
Formatting tag updated to ensure skin rule styles are correctly applied
Resolved in Pega Version 8.1.5
After a style was configured in the skin rule for TABS laouts -> Repeating Formats, the configured style was not being correctly applied to the skin. This was related to the anchor tag not picking up the changes, and has been resolved by replacing that with a span tag.
SR-C89463 · Issue 433822
Corrected tab name handling in Report Browser
Resolved in Pega Version 8.1.5
When using the report browser, refreshing the page after subscribing and unsubscribing to a report changed the tab name to the task id (eg. "PX-ST-123") and an extra tab appeared. This has been corrected.
SR-C89482 · Issue 427891
ReportBrowser export to Excel or PDF retains chart
Resolved in Pega Version 8.1.5
Clicking on "Export to PDF" or "Export to Excel" caused the chart image in the report browser to become blank on the screen and the image was not included in the exported file. Hitting refresh or reruning the report displayed the chart again. This was caused by the chart being unloaded whenever any form was submitted due to the way caching was handled, and has been corrected with the addition of a check that will ensure included charts are preserved.
SR-C89504 · Issue 435567
Multi-Select values visible in read-only
Resolved in Pega Version 8.1.5
The Selected Multi-Select values were not seen on the read-only review screen. This has been corrected.
SR-C89628 · Issue 430886
Correct values are selected in auto-complete in list configuration after scrolling
Resolved in Pega Version 8.1.5
When a value from the second page of the source list in the auto-complete was selected, the prior value was getting selected and posted. As an example, if the (n)th value was selected by scrolling down the results in the list, the (n-1) value was getting selected and posted to clipboard. Investigation showed this occurred if autocomplete was configured with allow free form input ' no', and that results were not getting selected properly after first scroll when using list configuration. This has been corrected.