SR-D3604 · Issue 439095
Parameter support added for openAssignment
Resolved in Pega Version 8.3
An enhancement has been added that will allow leveraging the Associate Requestor for Chat interactions through parameter support for the openAssignment action. This will allow an activity to be called to create the interaction and pass back the assignment and open it using the openAssignment API.
SR-D2380 · Issue 439108
Fixed Export to PDF page formatting
Resolved in Pega Version 8.3
A formatting issue was seen when using export to PDF; the first page contained only the title of the report as well as the filter, the generated date, and the number of records, and the exported data was included only from the 2nd page onwards. This has been corrected, and some performance improvements for the generation time were added.
SR-D3598 · Issue 439124
CSS updated to correct Microsoft Internet Explorer issues with Flexbox
Resolved in Pega Version 8.3
After launching a user portal from Dev Studio in IE11, the screen appeared blank. Each table column was stretched out, and a horizontal scroll bar appeared at the bottom of the screen that scrolled infinitely. Investigation revealed that this issue was caused by Internet Explorer not completely supporting FLEX containers. To resolve this, the CSS code for the screen layout region content has been updated to compensate and properly display in IE.
SR-D26641 · Issue 439205
Truncate now considers empty Cassandra cluster as proper DDS state
Resolved in Pega Version 8.3
After setting up two external Cassandra DDS nodes with data sets, decommissioning one node and running truncate resulted in the exception "Truncate cannot be performed due to an inconsistency in the Cassandra cluster status". This was traced to the empty cluster being considered an improper state of DDS that then failed a consistency check, and this has been resolved by modifying the consistency check behavior to consider an empty cluster as a proper state of DDS.
SR-D2615 · Issue 439225
Added function to auto-validate Chinese date
Resolved in Pega Version 8.3
If a datetime property with custom format was created in the zh_CNadtimezoe (Asia/Shangai) locale, the property was not updating if a date was selected with any time unless an onchange refresh action was included. This has been resolved by adding a function that will automatically validate the date for the Chinese locale.
SR-D2286 · Issue 439250
UIKit 12 updated to ensure data pages are cleared when switching applications
Resolved in Pega Version 8.3
When using UIKit 12, switching applications without logging off resulted in the 'Recent reports' list and Public Category containing reports and folders that belonged to the previous application. Investigation showed that the pyCMReportBrowserHeader function in UIKit 12 did not include the custom control "pzRBIncludes7", which clears the data pages. This has now been added to ensure that report browser data pages are now automatically cleared on app switch.
SR-D3405 · Issue 439258
URL construction logic updated for Tracer
Resolved in Pega Version 8.3
When trying to trace a requestor from the requestor management landing page, a 400 bad request error was generated. Investigation showed that when forming the tracer URL, the pxRequestor.pxRequestorPathInfoInReal property was being appended to it. Because the property contained unencoded characters([), the request was not being processed. To resolve this, the URL construction logic has been changed to use pxThread.pxReqBaseURI.
SR-D3494 · Issue 439415
Enhanced REST acceleration wizard handling of existing properties during rule generation
Resolved in Pega Version 8.3
A resolution provided in an earlier release addressed the REST accelerator wizard failing when there was a property present in the @baseclass and that property was also present in the JSON input for data model generation. The error generated was "Cancelling rule generation. Definition required to conform to @baseclass.Name instance". This update further enhances that Rest wizard resolution to address case sensitivity issues in the naming, and adds additional support for scenarios where the property does not exist in the integration class or parent class by checking if the property exists in pyIntContextClass.
SR-D3371 · Issue 439505
Association Resolver updated to handle filters created on secured properties
Resolved in Pega Version 8.3
After creating a Report Definition in a class (Example Class A) that had an Association in that report with Class B, no results were generated from the report when an Access Control Policy and Access Control Policy Condition were created for Class A and Class B where the Class B had an ACPC with a Value field that referred to a Data Page or clipboard page property. Investigation showed the system was not able to resolve the actual value of the datapage property in the generated SQL query due to Association Resolver resetting the filter value (the Page reference in this case) of a filter that is created on a secured property. This has been corrected by updating Association Resolver to not reset the right operand for a filter that is created on a secured property.
SR-C97479 · Issue 439533
Database indexes added for better performance
Resolved in Pega Version 8.3
In order to improve performance, database indexes have been added to pegarules-master.xml.