SR-D80539 · Issue 544795
Testcases are not available for 'access when' rules
Resolved in Pega Version 8.4.1
Attempting to create test cases for access when rules resulted in guardrail warnings about the need to create a test case. Because Test Cases are not available for the Access When rule type as per Pega expected behavior, the guardrail warnings are not valid and have been removed.
INC-200416 · Issue 699863
Updated AttachmentPreview control for Account Manager Access Group
Resolved in Pega Version 8.6.4
When using the Account Manager Access group as the default and only access group on a profile, attempting to render a PDF on the click of a link did not work as expected. The render-on-click worked as expected when logged in as the Author and the application was switched to Account Manager. This has been resolved by registering the activity pzAppStorageOkToAttachFile in the pzAttachmentPreview control.
INC-207210 · Issue 703701
Empty check added to OpenRuleAdvanced
Resolved in Pega Version 8.6.4
A blank screen was displayed when attempting to open a requirement set rule in Dev Studio. This was a missed use case while updating the OpenRuleAdvanced control to handle BAC compatibility, and has been resolved by adding an empty check in addition to the existing null check along with an 'if' condition to check for pyActivity input.
SR-D90544 · Issue 550808
Corrected row focus for deleting in App Studio case model
Resolved in Pega Version 8.4.1
When attempting to delete a row of properties from the 2nd page of the data model of a case type while using App Studio, clicking on the delete icon brought up a dialog box asking for confirmation for deletion but at the same time the screen went back to the first page of the data model instead of remaining on the second page. Because of this, clicking on the OK button to confirm the deletion caused a random property from the first page to be deleted instead of the targeted row of the second page as expected. This was due to the refresh being triggered immediately within overlay UI actions, and has been resolved by updating the first trash icon action set for the section pzExpressFieldActions to be a modal instead of an overlay when launching local action.
SR-D78467 · Issue 542319
Component rule check added to suppress unnecessary guardrail warnings
Resolved in Pega Version 8.4.1
After creating a component application using Configure > Application > Components, guardrail warnings were seen when saving the component. The component application allowed adding rulesets or other applications, but did not have all the tabs found in a normal application, so there was no option for adding the associated classes to define the UI class, Integration class and data class in the component application. As component is mostly a part of (or embedded inside) an application, this function was not given options to justify or suppress guardrail warnings like Rule-Application. To resolve this, a check has been added for component rule before generating guardrail warnings for Empty UI page, Empty Integration class, and Empty Data class.
INC-195793 · Issue 697921
Enhanced ruleset validation for portal creation
Resolved in Pega Version 8.6.4
Attempting to create a new portal (web channel) from the app studio using the Creation Wizard with "Branch development preferences" enabled resulted in the error message "No valid rulesets in application preferences". Investigation showed this occurred due to CPM-Portal being specified in the application as the UI class: when attempting to create the portal, the system was evaluating the class against ruleset candidates. The class was not visible to the rulesets in the stack and thus the portal could not be created. This has been resolved by adding validation on UI pages, Int and Data classes in the application to ensure that they exist in user rulesets, and by adding an allowance for classes to exist only in branched rulesets and not the base ruleset during check if the ruleset is present in application stack.
SR-D71475 · Issue 538722
Check added to apply values of newAssignPage.pxFormName
Resolved in Pega Version 8.4.1
After upgrade, trying to open existing assignments resulted in a different harness being opened. This was traced to changes in how the property newAssignPage.pxFormName was used, and has been resolved by checking whether the harnesspurpose is dynamic before setting the pxFormName. If formname is already present, the system will proceed with picking the harness from the shape.
INC-195790 · Issue 687810
Updated recording test scenario for attachments
Resolved in Pega Version 8.6.4
Recording scenario tests for a case type was not working as expected when attaching a document to a case as part of case flow. This has been resolved as part of the updates made for Pega Test Automation Kit (PTAK) v1.6.
INC-206782 · Issue 701142
BAC updated for delegated circumstanced decision table rule
Resolved in Pega Version 8.6.4
An unregistered request error was encountered while launching the DelegatedRulesPage harness when pyBlockUnregisteredRequests >=1. This was traced to a delegated circumstanced decision table rule which caused a request error for the @baseclass.pzLookupCircumList activity, and has been resolved by updating the BAC handling for this activity.
INC-209426 · Issue 706802
GetFunctionsForLibrary retrieves 10,000 rows
Resolved in Pega Version 8.6.4
Some functions were missing from the expression builder browser and search results when pyShowInternalLibrary was set to true for including internal functions in the results. To resolve this, the default value for "Maximum number of rows to retrieve" in pzGetFunctionsForLibrary has been increased to 10,000.