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()'.
SR-C97399 · Issue 439741
Button type added to allow grid expand in Edge
Resolved in Pega Version 8.3
When using an expand pane grid in a modal with the Edge browser, clicking on the expand icon using the enter key was throwing an error in new window. This was traced to an issue with a hidden non-auto-generated button in the pzModalHelp control not having a default type, and has been resolved by adding type="button" in the control so Edge will treat it as a submit button.
SR-D657 · Issue 439880
Corrected issue with Field Level Auditing re-adding deleted page list items
Resolved in Pega Version 8.3
Pressing a Save button that invoked the pyTrackSecurityChanges data transform caused deleted items to be added back to a page list. This was caused by pyPropertyIndex being set on the removed page in RUF-pzAddHistoryMemosForPageList, and has been corrected by removing that unneeded action.
SR-D4027 · Issue 439897
Explicit property evaluation added to correct visibility in Proposition Management sorting
Resolved in Pega Version 8.3
After navigating to the Decisioning: Proposition Management landing page (Configure->Decisioning->Decisions-> Proposition management -> Hierarchy), opening any Decision data and then switching to the Form tab to perform any sorting on the Form fields grid caused the UI to become unresponsive and generate the error "Uncaught SyntaxError: Unexpected end of input at pega.ui.Doc.evaluateVisibleWhens". This issue was traced to a 'when' condition which demanded explicit mention of whether the property value had been evaluated as true or false, and that result has now been added.
SR-C93572 · Issue 440078
Search initialization logic updated to ensure consistent node member information
Resolved in Pega Version 8.3
The search function was intermittently failing across nodes after restart. Investigation showed that this was due to inconsistent results from search initialization cluster logic using Hazelcast APIs to tell whether or not a given node was part of a Pega cluster. To resolve this, the logic has been updated to rely on ES APIs instead of Hazelcast cluster membership to determine offline nodes.