SR-D77004 · Issue 542349
View Full History will not include private edits
Resolved in Pega Version 8.4.1
After upgrade, clicking 'View Full History' and then 'History of All Versions', showed the history of discarded private edits of other users. This was an inadvertent side effect of work done to improve the support for rollback and migration, and has been resolved by updating the system to not save the history when in a personal ruleset (checkouts/private edits). The help documentation has also been updated to note there is no history available for checkouts/private edits.
INC-185362 · Issue 668826
Keystore update properly revises the cache
Resolved in Pega Version 8.7
A keystore updated with the latest certificate was not getting reflected in the runtime and the old certificate was getting picked. In a multi-node environment when the new JKS is uploaded in one node, the changes are expected to be communicated to other nodes so that the cache can be cleaned up. In this case, investigation showed that the keystore label was in uppercase and the cache entry was not correctly removed. This has been resolved by adding an update that will convert the cache key to lowercase and maintain uniformity to ensure proper cleanup.
INC-222388 · Issue 731651
Handling updated for custom flow bulk actions
Resolved in Pega Version 8.8
If the first assignment in a bulk queue failed validation of the flow action, the other selected assignments with same validations also failed without going to queue. This occurred when custom flow actions were configured on the standard bulk processing section, and caused the incorrect email template to be sent. To resolve this, Activity ProcessMultipleAssignments has been modified to add jump conditions to address the errors in PerformFlowAction and handle exception scenarios and ensure the proper template is sent.
INC-228963 · Issue 740547
Null check added for blank CSS style
Resolved in Pega Version 8.8
After a case was created from email, opening the case did not display the email body. This was traced to the styles found in the content of the email body, specifically to a style starting with ":root" that was causing the issue. In pyGetHTMLMessage, the email processing does not happen if the CSS selector is blank, which happened due to a null check not being performed when changing the internal CSS styles to inline CSS styles. To resolve this a null check has been added on the selector.
INC-213918 · Issue 714453
Discard button works consistently
Resolved in Pega Version 8.8
After check out, the discard button was not working consistently for decision tables or MapValue. Investigation showed this occurred when an exported file was being downloaded in the same window, as the thread would be busy with the file and not able to perform the discard action on the window. To resolve this, the configuration for the download on the same window has been removed, exportToDecisionTable has been modified to handle an iframe, and a runScript action has been added to register the exportToExcel activity and download in iframe.
INC-184307 · Issue 673228
Improved accessibility for overflow menu tab
Resolved in Pega Version 8.8
When a tabbled layout group has more tabs than will fit horizontally on the screen, icons appear to the left and right of the visible tabs to scroll through the available tabs along with a drop down list to select from all available tabs. Running the accessibility tool generated an error message for the down arrow button on the right. This was traced to a set tabindex 0 for unfocusable items, and has been resolved by adding tabindex="-1" for the overflow menu.
INC-226386 · Issue 741133
Ensure field level server side validation messages cleared
Resolved in Pega Version 8.8
A validation message was retained when not required. This was traced to a scenario where there were two server side validation messages on the decimal field in addition to a required client side validation condition; on text change of the decimal field, the server side validation persisted and client side validation replaced only the first message. This has been resolved with an update which will remove field level server side validation messages after client side validation on an event trigger.
INC-145425 · Issue 600774
New email template added to include full message history
Resolved in Pega Version 8.4.4
Whenever a reply was sent from the email triage case, the outbound email sent only the actual reply along with the original email and latest reply only, skipping all remaining replies from email. For example, if there were 5 replies from case, replying 5th time generated an outbound email that contained only 5th reply (actual / current), original reply (which created the service case) and the latest reply (reply 4 in this case) and skipped reply 1 and reply 2. To resolve this, a new Outlook-style template has been added for use in replies that will include all of the previous exchanges.
INC-195354 · Issue 682183
Handling updated for UpgradeBeforeOpening
Resolved in Pega Version 8.7
After update, an email case paused for 1 minute with a wait shape and then resumed by a ServiceLevelEvents agent seemed to lose the context (class) of the case and went into the broken processes queue with the error "Unable to open an instance using the given inputs: pxObjClass = "Work-Channel-Triage"". This was traced to an incorrect class applied by the activity OpenAndLockWork which assumed that "Work-Channel-Triage" was the preferred class and passed in the case ID as a parameter. To resolve this, pzUpgradeBeforeOpening has been updated such that it will migrate a case only if it has "WORK-CHANNEL-TRIAGE" in the work object inskey.
INC-163791 · Issue 704030
Simplified default reference time calculations
Resolved in Pega Version 8.8
After a job scheduler was configured to run at Start time = 21:00:00 for Time zone = Europe/London, the scheduler determined 20:00:00 as the next start time. This was due to the calculation for the next start time using the time zone offset calculation pattern for the date and time stored in System-Runtime-Context.pxCreateDateTime, which had difficulty with changes to the time zone definition implemented in the time between the given date and today (meaning the current time) such as daylight savings time. To resolve this, the default reference time from System Runtime Context will be 'now' instead of Date(0).