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-D33832 · Issue 503958
Configurability added to SLA Timeliness to allow either 0 or NULL for Unqualified records
Resolved in Pega Version 8.4
When using a Report Definition where the count (aggregate function) was used for both the WithinSLA and Past Deadline columns, the correct value was not getting displayed. The correct value was displayed when the sum function was used instead of the count function, but clicking 'value' returned all values despite what value was displayed on the screen. This was a behavior change related to performing a drill down action on a report definition. As per the older behavior, drill down relies on a specific value (NULL) to determine whether a record is a candidate to be shown in the drill down report. From 7.2.1 forward, drilldown relies on value 0 instead of NULL to make the average summarize function work properly, which led to a change in behavior when used with other summarize functions like sum and count. To resolve this, SLA Timeliness related RAFs have been modified to conditionally return either 0 or NULL for Unqualified records based on a DASS config.
SR-D42602 · Issue 511856
PRCipher class references updated
Resolved in Pega Version 8.4
After upgrade, starting Tomcat resulted in the error "java.lang.ClassCastException: com.pega.platform.securitycore.encryption.internal.CipherDefault cannot be cast to com.pega.pegarules.exec.external.util.crypto.PRCipher"This was traced to an issue with the references for PRCipher: cipher was moved to be a security-core component, but the class structure changes were not fully updated. This has been corrected.
SR-D45865 · Issue 513019
Primary page paramter explictly set to resolve fix/edit Scheduled Tasks issue
Resolved in Pega Version 8.4
After upgrade, the top section of report details was getting blanked out when using the Reporting | Components | Scheduled Task to open a report and "update" it to fix issues. This was an unintended side effect of updating the Review harness to display the Perform harness when clicking Update, which was done to correct an earlier issue with UI validations when using the out of the box schedule report functionality. To resolve this, pxScheduleTaskWrapper has been updated to explicitly set the parameter page according to the primary page's values when not in the report browser.
SR-D5904 · Issue 504995
Discard changes dialog now showing for local actions
Resolved in Pega Version 8.4
After having modified case data without saving and clicking on a menu entry (left menu, search, ...), the system shows a dialog box to ask the user to confirm it is ok to discard changes. However, this confirmation dialog did not work with local actions, leading users to lose their work without any warning nor any way to step back. This was traced to a difference in the dirty form check, which was not present when launching a local action from a case. An enhancement has now been added to the handleMenuAction js function in pypega_ui_harnessactions.js which will perform a dirty form check with a prompt.
SR-D63737 · Issue 525524
Resolved ruleset save issue for Google Chrome/IE
Resolved in Pega Version 8.4
When using particular versions of Google Chrome or Microsoft Internet Explorer, the intermittent error "pyComponentInterfaceClass: <user> does not exist or is not a valid entry for this ruleset and its prerequisites" appeared when attempting to validate an application, and the ruleset could not be saved. This was traced to changes made in the browser around password handling, and has been resolved by explicitly clearing out the pyComponentInterfaceClass if that value is not in use.
SR-69015 · Issue 619995
Unescaping characters implemented for expressions
Resolved in Pega Version 8.3.6, Resolved in Pega Version 8.4.4, Resolved in Pega Version 8.5.3, Resolved in Pega Version 8.6
An issue where expression builder statements were evaluated differently at runtime than at testing has been resolved. Pega Platform expressions with String literals(that is, sequences of characters enclosed in quotation marks) now unescape characters in strategy shapes such as Set Property or Filter.
SR-D47018 · Issue 517032
Corrected parameter being encrypted during change portal configuration
Resolved in Pega Version 8.2.5
After configuring a changePortalLayout control using .pyDescription as property, trying to switch the portal was throwing a error page. The same configuration worked in earlier platform versions. This was traced to recent updates where the activity parameter ended up being encrypted along with the activity name, and has been resolved by removing the parameter from encryption input and adding it to encryption output.
SR-D5904 · Issue 511600
Discard changes dialog now showing for local actions
Resolved in Pega Version 8.2.5
After having modified case data without saving and clicking on a menu entry (left menu, search, ...), the system shows a dialog box to ask the user to confirm it is ok to discard changes. However, this confirmation dialog did not work with local actions, leading users to lose their work without any warning nor any way to step back. This was traced to a difference in the dirty form check, which was not present when launching a local action from a case. An enhancement has now been added to the handleMenuAction js function in pypega_ui_harnessactions.js which will perform a dirty form check with a prompt.
SR-D24527 · Issue 504402
Improved requestor cleanup
Resolved in Pega Version 8.2.5
Batch- and Browser-type Requestors were building up over time in both the Admin Studio and in the PegaRULES log and not removed until the system was restarted. This has been resolved by adding two extra cleanupRequestor calls to the Email Listener implementation.