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.
SR-D38588 · Issue 506370
Removed unneeded table name calculation
Resolved in Pega Version 8.4
After giving short names (less than 30 characters) for "To Table", saving did not produce an error, but an error was thrown during Check In. Investigation showed that while checking in the extract rule, a block of code in the Rule-Utility-Function validateTreeProperties was being executed to recompute the pagelist's table name instead of using the name provided by the user. To resolve this, the Rule-Utility-Function has been modified to not execute this block of code during check-in of the extract rule. The validation will be seen during save if the 'To field' has more than 30 characters.
SR-D32086 · Issue 500895
Memory leak repaired
Resolved in Pega Version 8.4
A server side memory leak was traced to heap utilization increasing due to a Stream control assembly problem where the CleanForReuse() function was not cleaning up pzAuto. The cleanForReuse method in generated HTML properties is used to either initialize local fields, in which case aContext will be non-null, or to clear the object for pooling, in which case aContext will be null. Because the pzAuto variable was not being properly nullified, pooled controls were retaining stale references to StreamTools, LayoutRuntime, PRThread, and others. This has been resolved by adding code to ensure the pzAuto variable is correctly nullified, and additional work has been done to improve memory management.
SR-D32332 · Issue 502270
Removed unneeded table name calculation
Resolved in Pega Version 8.4
After giving short names (less than 30 characters) for "To Table", saving did not produce an error, but an error was thrown during Check In. Investigation showed that while checking in the extract rule, a block of code in the Rule-Utility-Function validateTreeProperties was being executed to recompute the pagelist's table name instead of using the name provided by the user. To resolve this, the Rule-Utility-Function has been modified to not execute this block of code during check-in of the extract rule. The validation will be seen during save if the 'To field' has more than 30 characters.
SR-D32332 · Issue 502269
Removed unneeded table name calculation
Resolved in Pega Version 8.2.4
After giving short names (less than 30 characters) for "To Table", saving did not produce an error, but an error was thrown during Check In. Investigation showed that while checking in the extract rule, a block of code in the Rule-Utility-Function validateTreeProperties was being executed to recompute the pagelist's table name instead of using the name provided by the user. To resolve this, the RUF has been modified to not execute this block of code during check-in of the extract rule. The validation will be seen during save if the 'To field' has more than 30 characters.
SR-D38588 · Issue 506368
Removed unneeded table name calculation
Resolved in Pega Version 8.2.4
After giving short names (less than 30 characters) for "To Table", saving did not produce an error, but an error was thrown during Check In. Investigation showed that while checking in the extract rule, a block of code in the Rule-Utility-Function validateTreeProperties was being executed to recompute the pagelist's table name instead of using the name provided by the user. To resolve this, the Rule-Utility-Function has been modified to not execute this block of code during check-in of the extract rule. The validation will be seen during save if the 'To field' has more than 30 characters.
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.