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.
SR-D4171 · Issue 439537
Preview of Activity shows the parameters correctly
Resolved in Pega Version 8.3
If Activity A1 called another activity A2 which had some parameters, clicking the preview of activity A1 did not show all of the parameters of A2. Investigation showed that RuleScribe_Call was getting the property value as a String, but in pyStepsCallParams some of the properties are not strings (for example, pyStepsParamUI(...) is a Page List). To resolve this issue, code has been added to handle this use case so all of the expected parameters are displayed.
SR-C88711 · Issue 439595
Handling added for exception caused by empty page list
Resolved in Pega Version 8.3
Attempting to map an auto-populated pageList property in a data transform was throwing a java IndexoutofBoundException. Investigation showed that the system was trying to access the second element of an empty Page List. To resolve this, the system has been updated to use a flat list DataProvider which will return null if the list does not exist rather than return a list that is not associated with the parent page.
SR-D4025 · Issue 439628
Check added to ensure interactions show ID
Resolved in Pega Version 8.3
After creating many interactions, navigating to the interactions not visible on the screen using the "Currently open" menu displayed the interactions as New instead of the interaction ID. This has been resolved with the addition of a check for customer headers.
SR-D3034 · Issue 439706
Corrected reference to Hierarchical table in tree grid modal section
Resolved in Pega Version 8.3
Given a table on which row editing opened a modal dialog containing a section with a Hierarchial table, after the modal dialog window was opened and closed without changes, attempting to open it again produced a blank screen. The error "The reference PackagesPage.Packages(2)(1) is not valid. Reason: unexpected character '(' at position 24, expected dot" was logged. This was an edge case where a grid was opened in a modal dialogue from a tree grid. In this case, the parameters passed from the parent grid corrupted the logic to calculate the Automation ID and caused the reference page to be constructed incorrectly. To resolve this, a try catch block has been added to read the reference from 'tools.getActiveName()'.