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-C49664 · Issue 435310
Updates made for usage validation utility Run report checkbox and buttons
Resolved in Pega Version 8.1.5
The 'Review mode only' checkbox wasn't working for any browser, and the 'Run Report' button wasn't working in IE. This has been resolved by updating the javascript used to invoke the Run Report button to be better integrated with IE, and by adding additional handling to set the ID for the checkbox.
SR-C74677 · Issue 418339
ADM pulse timing changed to inprove performance on very large clusters
Resolved in Pega Version 8.1.5
ADM uses a pulse that checks if any models need to be updated. This uses a Cassandra query which has no "where" clause, causing poor performance for very large clusters. For immediate relief of this issue, the pulse configuration has been updated to increase the timing from 30 to 300 seconds so it fires less often. Model updates typically happen every x hours and often the pulse will not detect any models that would need to be updated. Further improvements in this process will be available in a future release.
SR-C77730 · Issue 437101
Resolved case lock release improved
Resolved in Pega Version 8.1.5
Cases created through the create work object were unnecessarily holding onto locks for up to two hours. This was traced to a defer-write scenario for mobile devices which did not return the correct status needed for "no further assignments". In order to resolve this issue, a new parameter "returnNextActionInfo" of type boolean has been added to svcPerformFlowAction. This parameter will be always set as false when calling this activity from sync up so all locks will be closed and released.
SR-C80622 · Issue 424876
GenerateContainer updated to prefer icon given in skin over hardcoded icons
Resolved in Pega Version 8.1.5
When trying to change the Expand/Collapse icon for dynamic layout by defining a custom format in the app skin, changes made in the Expand icon image and Collapse icon image were not reflected. This was due to the CSS selector being overriden with a hardcoded arrow icon instead of automatically taking the icon from the skin rule. To resolve this, the selector and conditions used in GenerateContainer.java have been modified such that the icon added in the skin should be picked automatically instead of any hardcoded icon available.
SR-C81185 · Issue 427995
Accessibility enabled Layout group tabs browsing corrected
Resolved in Pega Version 8.1.5
When using Layout group (Tab) or a Tabbed Layout for viewing client information in Tabs with Accessibility enabled, the system was reading each tab and its content but then focus was returning to the browser and tracing through all elements before moving on to the next tab. This was traced to an incorrect tabindex setting in the pzpega_ui_template_layout_header file, and has been fixed.