SR-D26101 · Issue 495206
Improved DX API page reference handling
Resolved in Pega Version 8.2.3
When using a property that was being referred through a secondary page that could be referred directly by the case (such as .AccountClosureDetails.ClosingAccountApplicant), the page was not initialized and the local list values were not returned by the DX API. This has been resolved by improving the handling for embedded page references via section include where the property reference is a full path.
SR-D26334 · Issue 495320
Restore delegated rules short description header
Resolved in Pega Version 8.2.3
For delegated rules like SLA/Correspondence, the short description was not getting displayed in the header. This was an unintended side effect of work done on automation rule capabilities, and has been resolved by restoring the layout visibility condition pzDelegateHeader in pzRuleFormKeysAndDescription.
SR-D18036 · Issue 495397
Holdability flag set on connection for using MS SQL in Designer Studio
Resolved in Pega Version 8.2.3
Static assembler was not working from Designer Studio, displaying the error "com.microsoft.sqlserver.jdbc.SQLServerException: SQL Server supports holdability at the connection level only. Use the connection.setHoldability() method." Investigation showed that ApplicationAssembly.getResultSetForQuery explicitly sets the holdability flag on the prepared statement, and this issue has been resolved by updating the system to set the holdability flag on connection as well.
SR-D22170 · Issue 495575
Whitelisted RunTime_ControlPanel streams in Designer Studio development
Resolved in Pega Version 8.2.3
Using developer access in Designer Studio was generating SECU0016 errors in PDC: "Unauthorized access to the stream rule : Unauthorized access to the stream rule Data-Portal-DesignerStudio.pzRunTime_ControlPanel Rule-HTML-Section". This has been resolved by whitelisting stream names starting with pzRunTime_ControlPanel.
SR-D25607 · Issue 495622
Added NPE handling to PegaInstaller
Resolved in Pega Version 8.2.3
When upgrading, the error "Error: java.lang.NullPointerException [java] at com.pega.pegarules.deploy.internal.exposecols.jobs.ExposeWrapper.runExposer" appeared and the installation would not proceed. Investigation showed that the NPE occurred because of class name validation not being performed at the right place. As the NPE occurred in the main class, it initiated thread pool executor shutdown. However, the consumer pool did not shutdown because it did not receive the correct specific producer message fto do so. This has been resolved by ensuring isValidClass is executed at the right place in ExposeWrapper.java to handle the NPE, and adding handling for the interrupt exception in consumer thread so that in case of any run time exceptions in the main thread, the consumer thread will not be stuck.
SR-D19801 · Issue 495839
Corrected embedded section inside dynamic layout group becoming readonly
Resolved in Pega Version 8.2.3
When using a nested sections structure in a Dynamic Layout Group (tab), the fields inside the layout group were becoming readonly. This has been resolved by ensuring the controls present in second-level nesting onwards obey section read-only value in a dynamic layout group, and resolving the 'when' rule that governs the disabledwhen of link for all sections in a section include.
SR-D23164 · Issue 493796
Edit icon removed from deprecated custom skin styling
Resolved in Pega Version 8.2.3
Using custom styles as skin component is a deprecated feature as of Pega Platform v8.2. While existing styles will still be added to the CSS file when upgrading to or beyond this version, adding or updating custom skin styles is now handled through manual CSS files included in the skin. As part of this change, the edit icon for changing custom styles has been removed.
SR-D23239 · Issue 496707
Support added for multi-operator SAML logins
Resolved in Pega Version 8.2.3
When a SAML user logged in by Single Sign-On (SAML), the system processed the login to portal as a different operator if there was a function on the Attribute field under Operator identification in the SAML authentication service. In this scenario, using an expression for operator provisioning did not work because all SAML login sessions resolved to same first operator due to parseAndEvaluateExpression() in ExpressionHelper.java ignoring new expression arguments if the expression page already existed. To support the use of multiple operator logins in this format, the system has been updated to clone a new expression page for every session and update it with the correct expression arguments.
SR-D28034 · Issue 497838
Asynchprocessor generation code deprecated from distribution
Resolved in Pega Version 8.2.3
During a Pega Rules Upgrade of the environment, the error "duplicate key value violates unique constraint "pr_data_admin_pk" was observed. This exception originated from the "Upgrade Context" target while executing a query to fetch the missing ASYNCPROCESSOR requestors for all available system names, and was caused by the system attempting to insert a single ASYNCPROCESSOR requestor more that once in the shared layer. The need to generate missing requestors only applied for installations where a custom system name was provided to the deployment properties (setupDatabase), so by default the asyncprocessor generation code has been removed from the distribution as it is no longer required for upgrades. Default system behavior now is to use system-runtime-context in place of async requestors.
SR-D28293 · Issue 498234
Pega Survey answer values support special characters
Resolved in Pega Version 8.2.3
When using a Complex radio control (RadioButtonComplexQuestionSurvey), a selected option that used answer values containing special characters was cleared on refresh. This was traced to a mismatch between strAnswer and strValue in the control logic, and has been corrected.