SR-C94042 · Issue 444586
Resolved JSON exception with refreshrow used for navigation
Resolved in Pega Version 8.3
After upgrade, a custom implementation of a grid that had a menu configured on right click of the row for the category/description in the uploaded case attachments was not working. This was traced to the RefreshRow(non-list) action generating quotes that made the JSON invalid for a navigation rule, and has been fixed by modifying pzProcessRefreshRowItem to remove quotes from navigation refreshrow action generation.
SR-C96291 · Issue 445258
ADM initialization modified to eliminate unnecessary keyspace creation triggers
Resolved in Pega Version 8.3
On startup, ADM issues a Cassandra query to create one of its keyspaces if it doesn't already exist. To do this, it was set to require creation level permissions whether it created the keyspace or not, but those permissions may be considered a potential security violation if the Cassandra instance is shared with other teams. If permissions were restricted to only below key spaces used by Pega, then the ADM node would not start up. To resolve this, the way ADM initializes its keyspaces and tables has been modified so that queries requiring 'create keyspace' permissions are not triggered if the keyspace already exists. These changes also include code that ensures that keyspace and table creation can only happen on one node in the cluster at a time.
SR-D5196 · Issue 445416
Hardcoded prweb reference removed from the REST connector to enhance flexibility
Resolved in Pega Version 8.3
The DASS for pegarobotics/RobotManagerHostDomain allows specifying the instance where Robot Manager is hosted. Previously, connect-REST pzInvokeRoboticAutomation contained a reference to the resource path {RobotManagerHostDomain}/prweb/PRRestService/robotics/v1/automations which forced the use of prweb. In order to add flexibility, the hardcoded prweb reference has been removed from the REST connector resource path, and the pegarobotics/RobotManagerHostDomain) DASS's default value has been updated to include 'prweb' in it. Local sites should update DASS accordingly to point to an updated URL with prweb if needed.
SR-C95733 · Issue 445477
SendSimpleEmail modified to show complete attachment subject line
Resolved in Pega Version 8.3
The complete subject of the correspondence attached in a work object was not displayed in the UI. The clipboard page pyWorkPage -> Attachment (Link-Attachment) also showed an incomplete value in the pyMemo property, displaying only 64 characters. Investigation showed that pyCorrPage.pyLabel was being set to 64 characters in the Work-.SendSimpleEmail activity, and then used LinkMemo to show the value in the UI. To resolve this, the system will take HistMemo as the LinkMemo as well if it is available and then truncate it to the Link-Attachment.pyMemo size to store the entire value as exposed.
SR-D337 · Issue 445603
Rule Security Analyzer documentation updated regarding scan results examination
Resolved in Pega Version 8.3
The documentation for the Rule Security Analyzer (RSA) has been updated to indicate that the scan/search results must be exported to Excel In order to examine the details and identify the rules with vulnerabilities so the necessary actions may be taken.
SR-D2530 · Issue 445609
Added handling for cases where Microsoft Internet Explorer causes a SAXParseException
Resolved in Pega Version 8.3
Numerous SAXParseException messages were seen in the log file, and the queryString showed the pyDeleteDocumentPg being referenced. This was traced to the method used by Internet Explorer to construct an HTTP request: Microsoft Internet Explorer sends the header and body of the request in separate TCP packets, but for an unknown reason in this case the body packet goes missing. To resolve this, a toggle has been introduced which will send the pyDeleteDocumentPg request as GET if pega.u.d.GET_REQUEST_DELETEDOCUMENT is set to true in userworkform. In a normal flow without this variable, the request will pass through the normal flow.
SR-D5404 · Issue 445611
Support added for nested grids with child categorization
Resolved in Pega Version 8.3
Show Details and Expand All were not working as expected in a repeat grid with a nested grid scenario where the parent grid had Show Details enabled and the child grid had categorization enabled with one column selected for categorizing. Investigation showed that a null page was being passed (final @baseclass pzGridSortPaginate activity) due to a lack of support for considering page lists that are embedded in a page different than the step page. To add this support, the activity has been modified to use tools.getProperty(...) instead of myStepPage.getProperty(...) if the data source page list is not an embedded property in the parent row page.
SR-C96786 · Issue 445619
Controls updated to handle hidden values in finishassignment submission
Resolved in Pega Version 8.3
A SECU0001 alert was thrown from the out-of-the-box function finishassignment upon the submit of assignments. This was traced to an alert generated while attempting to post the feed even though there was no Pulse gadget used in the work object, and was due to the handling of hidden fields as read-only. Since the read-only values were not editable, they should not be submitted with the request body; this has been corrected by modifying the hidden control entry handle such that hidden property is considered as editable-filled. Controls have also been added to pxHidden to prevent potential misuse.
SR-D3556 · Issue 445684
Requestor.OperatorID page updated to stay in sync with current OperatorID to enable post-Auth activity mapping
Resolved in Pega Version 8.3
The systems pages were not getting updated to the right operator's context when a post-Auth activity was used for mapping. To support this use, the UpdateOperatorID trigger has been updated to keep the pxRequestor.OperatorID page in sync with the current operatorID page during SAML. The operator will also be saved during provisioning.
SR-D9157 · Issue 445709
Pega-RULES session decryption issue resolved
Resolved in Pega Version 8.3
When the Pega-RULES session encryption key was updated (rotated) after 90 days by the pyValidateKMSMetadata agent, the in-memory version of the key was then corrupted leading to a failure to decrypt the session header. This had the result of preventing any users from logging into the system. Users could connect to the login page and enter their credentials, but after clicking the Login button they were redirected back to the starting login page and their credential information was cleared. This was traced to the pulse change of SystemCDK moving the encryption and decryption process to inconsistent state where the CurrentSystemEncryptKeyIDHash still contained the old CDK ID.To resolve this, the system has been updated to use only ActiveKeyID instead of the previous behavior of using both ActiveKeyID and CurrentSystemEncryptKeyIDHash.