INC-175207 · Issue 655554
Added handling for DSM Services stuck in leaving status after database outage
Resolved in Pega Version 8.7
During a database outage, the heartbeat would fail and DSM services would eventually try to enter safe mode and stop. As the first step they would try to change the state to LEAVING, but because the database was down saving the LEAVING state failed and the exception was not handled correctly. This resulted in the rest of the stop operation logic not being executed and the service being stuck in LEAVING. To resolve this, an update has been made to ensure the service goes to LEAVING_FAILED if anything fails during the stop operation including when setting state to LEAVING_FAILED. The state LEAVING_FAILED will get flushed to the database eventually when it comes back up. This will allow the aggregation service to start from the LEAVING_FAILED state and recover by itself after a database outage.
INC-170130 · Issue 643776
Null check added for debug logging pointer error
Resolved in Pega Version 8.7
When DEBUG logging was enabled on the class 'com.pega.pegarules.session.internal.mgmt.base.AbstractPageDirectory', system restart resulted in the node failing to startup with a null pointer error in a debug block of this class. A null check has been added to resolve this.
INC-142066 · Issue 600046
Dirty confirmation alert added for standalone Ajax container
Resolved in Pega Version 8.4.4
In the Pega CS interaction portal, an interaction could be launched to create a service in the Ajax container. If the same service was opened from the search results or the worklist, however, it was not prompted with the dirty popup message to save or discard the changes. This was a missed use case for a standalone Ajax Container, and has been resolved by adding a check to evaluate whether the document has an Ajax Container so the proper dirty state handling will be called.
INC-183960 · Issue 674381
Cases Created through email bots remains searchable
Resolved in Pega Version 8.7
When a case was created through Email Bot, the delete attachment link in pzCreateTriageWork activity was triggering a delete event in incremental indexing that removed the main work object. This has been resolved by adding a condition check in the SearchIncrementalIndexNotifier class for the link page, and the work object will be updated instead of deleted.
INC-174921 · Issue 652322
Client Side required validation applied to dropdown Date field
Resolved in Pega Version 8.7
The mandatory validation on submit of the screenflow screen was not being triggered even though 'Required' was configured on the Date field. This was traced to the validation being applied to a hidden field when the date time control is configured in dropdown mode, and has been resolved by adding a condition for validating this configuration.
INC-136091 · Issue 598908
Activity updated for Mobile attachment access
Resolved in Pega Version 8.4.4
Preview and download were not working for attachments stored in Pega Cloud Storage repository for mobile devices. Attempting to open an email attachment to preview or download resulted in a console error and the tracer showed the message 'Class pxLinkedRefTo does not exist'. This has been resolved by updating "pzpega_control_attachutil" to use the activity "GetAttachmentReference" for interactions with the attachments from any storage type.
INC-142632 · Issue 598170
Activity updated for Mobile attachment access
Resolved in Pega Version 8.4.4
Preview and download were not working for attachments stored in Pega Cloud Storage repository for mobile devices. Attempting to open an email attachment to preview or download resulted in a console error and the tracer showed the message 'Class pxLinkedRefTo does not exist'. This has been resolved by updating "pzpega_control_attachutil" to use the activity "GetAttachmentReference" for interactions with the attachments from any storage type.
INC-143134 · Issue 598580
Activity updated for Mobile attachment access
Resolved in Pega Version 8.4.4
Preview and download were not working for attachments stored in Pega Cloud Storage repository for mobile devices. Attempting to open an email attachment to preview or download resulted in a console error and the tracer showed the message 'Class pxLinkedRefTo does not exist'. This has been resolved by updating "pzpega_control_attachutil" to use the activity "GetAttachmentReference" for interactions with the attachments from any storage type.
INC-152217 · Issue 613928
Activity updated for Mobile attachment access
Resolved in Pega Version 8.4.4
Preview and download were not working for attachments stored in Pega Cloud Storage repository for mobile devices. Attempting to open an email attachment to preview or download resulted in a console error and the tracer showed the message 'Class pxLinkedRefTo does not exist'. This has been resolved by updating "pzpega_control_attachutil" to use the activity "GetAttachmentReference" for interactions with the attachments from any storage type.
INC-137966 · Issue 597738
Embed-ReportFilter supports pyDateproperties
Resolved in Pega Version 8.4.4
After creating a report definition with Date time filter values where the 'from' date and 'to' date are input and propagated as “pyStartDateTime” and “pyEndDateTime” in the clipboard, opening the pyDate properties from clipboard resulted in a 'rule not found' exception. No properties of other data types generated the error. This has been resolved by creating the pyStartDateTime,pyEndDateTime and pyDisplayTimeperiod properties in Embed-ReportFilter to support this use.