INC-128960 · Issue 571360
Corrected approval step task message
Resolved in Pega Version 8.1.9
When a case progressed to the approval step, the task name did not properly appear as part of the "Please approve or reject this" message. In another scenario, a portal which supported locale switching was not translating "Please approve or reject this" when the locale was switched, but instead displayed the message in the original language. Investigation traced this to the pzInstructionsForApproval data transform storing the localized field value, causing it to persist inappropriately. This has been resolved.
INC-131151 · Issue 572832
Resolved empty body for Reject email
Resolved in Pega Version 8.1.9
When using the pzEmailActions Section in Correspondence for Approve/ Reject functionality via email, there was no reply body in the email for Reject Option. This was due to the flow action for the Reject email being different than that of the Approve email, and has been resolved.
INC-131385 · Issue 573454
Swagger APIs updated
Resolved in Pega Version 8.1.9
The Swagger File APIs have been updated to ensure swagger document files generated meet specifications for editor.swagger.io .
INC-134370 · Issue 577635
Expanded Grid locking updated
Resolved in Pega Version 8.1.9
When using pyDashboadMyWorkList to show the cases of an operator with Master Detail in Read Only mode, the system was acquiring a lock on the expanded work object. To resolve this, the following changes have been made: * In activity Assign-pyAcquireObject, If the parameter bRODetails is true, do not call acquireWorkObject and do obj-open-by-Handle to get assignment and work page in pyAcquireObject activity. * In activity acquireWorkObject, the parameter skipWorkLock has been removed as acquireWorkObject should always acquire the lock.
INC-134709 · Issue 579433
Updated endpoint Cross-site scripting protection
Resolved in Pega Version 8.1.9
Cross-site scripting security has been updated for Endpoints in Display activities.
INC-140739 · Issue 592830
UniqueID enhancement for attached files
Resolved in Pega Version 8.1.9
When two files with the same name were uploaded by different users simultaneously through Pulse or if a user uploaded two files with the same name across two sessions, whichever file arrived later was overriding the previous one in the system. As a result, the first pulse post ended up with an incorrect file attached. This has been resolved with an enhancement to add an API that appends a uniqueID to the file before uploading to ServiceExport directory.
SR-D98224 · Issue 580595
Updated endpoint Cross-site scripting protection
Resolved in Pega Version 8.1.9
Cross-site scripting security has been updated for Endpoints in Display activities.
INC-126129 · Issue 569666
PropertyToColumnMap made more robust
Resolved in Pega Version 8.1.9
The DF_ProcessEmails dataflow was intermittently failing with a StageException error. This was traced to schema changes being propagated asynchronously by system pulse, which seem to have caused PropertyToColumnMap to cache stale schema. To resolve this, if the property mapping is not found the first time, the system will make a second attempt to get the mapping. Additional logging has also been added for better diagnostics.
INC-128385 · Issue 564521
Behavior made consistent between SSA and legacy engines
Resolved in Pega Version 8.1.9
There was a behavioral disparity between the legacy execution engine and the SSA engine where the latter was not creating a new page when the index was one above the size of the page list. This has now been corrected in order to make the SSA behavior fully backward compatible with the legacy engine, i.e. a new blank page will be added to the list if the index is one above the size of the list.
INC-129222 · Issue 568530
Handling improvements for commit logs
Resolved in Pega Version 8.1.9
The ADM commit log logs the number of unconsumed messages that are going to expire. In certain circumstances, it can include unconsumed messages that are not going to expire in the count. Because they are not expired and removed, the environment was running out of disk space due to the ADM commitlogs table growing larger than expected and performance issues were seen. To resolve this, a new adm_commitlog.adm_responses_commit_log_date_tiered table has been created, with a default_time_to_live of 24 hours. DateTieredCompactionStrategy has been set with max_window_size_seconds as 24hrs and tombstone_compaction_interval as 24hrs.