INC-127981 · Issue 563001
Rulesets removed from direct invocation ability
Resolved in Pega Version 8.4.2
Internal rules have been updated so that they are no longer available to be invoked directly by a client or service.
INC-131175 · Issue 571610
Branch rule deletion updated
Resolved in Pega Version 8.4.2
When two branches, for example Test1 and Test_1, were created and the rules were saved, deleting the Test1 branch also deleted the rules in Test_1, resulting in the remaining branch Test_1 not having any rules. This was traced to the Obj-List method in activity DeleteRuleset fetching the incorrect results, and has been resolved by replacing it with a report definition created in Data-Rule-Summary.
INC-133213 · Issue 572534
Merge group size decreased to match SQL list limits
Resolved in Pega Version 8.4.2
Duplicate rules were seen and the error "maximum number of expressions in a list is 1000" was generated after performing a ProvAuditFW merge. Before merge there was a property populated with a comma-separated list of instances to be merged: this was used later as the source of a report definition. This was presented as a value list because of the limitations of datapages to accept very large 'when' clauses. This comma separated list was split up into batches of 200 to keep the length of this 'where' clause low. However, the SQL that was generated exceeded the limit of 1000 items in a list, causing the error and duplicates. To resolve this, the group size has been decreased so that limit will not be hit.
INC-70005 · Issue 549397
Pagination added to MT Requestor Pools list
Resolved in Pega Version 8.4.2
The Admin Studio requestor pools list did not have pagination and always displayed only one page irrespective of the numbers of items, but only on a specific node. This was traced to the node in question having multiple tenants: the normal use case is that there are not very many Requestor Pools, and choosing a "Specific node" for Requestor Pools usually returns fewer than 10 results. However, on an MT system there could be substantially more Requestor Pools, and pagination has been added to pzRequestorPoolsDetailsGrid to handle this use case.
SR-D76492 · Issue 549970
Added check for test case creation when Cross-site scripting security enabled
Resolved in Pega Version 8.4.2
Test case creation was failing. Investigation showed that when the "Cross-Site Request Forgery" security setting was enabled, the CSRF token and Browser fingerprint were not included in AJAX calls, and the Ruleinskey was not getting passed. This has been resolved by adding a check to evaluate whether security measures are included or not when making a server call from AJAX, and including the tokens required when appropriate.
SR-D79831 · Issue 562802
Access Deny working as expected for Offers
Resolved in Pega Version 8.4.2
It was possible to Save-As an offer in PegaMKT-Work-Offer after encountering an access deny rule. The record was not created in Dev Studio, however, and an expected denial of access was not registered at runtime. This was due to Access deny rules not being considered as a part of validation, and has been resolved by adding the necessary permission validation to the new harness that will produce the error message informing the user that they are missing a permission. Additional work has also been done to pass the 'pzKeepPageMessages' parameter as true so that page level error messages are correctly displayed.
SR-D85111 · Issue 549198
Paging method updated for Select All in Broken Queue
Resolved in Pega Version 8.4.2
After clicking the 'Select All' box in Broken Queue In Admin Studio, scrolling up and down rapidly caused the checkboxes to be unselected. This was traced to the use of progressing paging in this scenario, and has been resolved by removing progressive paging and replacing it with the out of the box '1 of X' paging method.
SR-D90520 · Issue 552019
REST parameters updated for SauceLabs compatibility
Resolved in Pega Version 8.4.2
After configuring a call to SauceLabs testing through Deployment manager, the REST call was timing out. Investigation traced the issue to SauceLabs changing its parameter name from "browser" to "browsername", and the Pega parameter names have now been updated to reflect that change.
SR-D93181 · Issue 555469
Pega Org Structure Tools added
Resolved in Pega Version 8.4.2
An enhancement has been made available on Pega Marketplace to simplify working with large organizational structures with additional support for having more than 3,333 organizations. This allows choosing an Org, Div and Unit in the Operator ID and Application ruleforms using auto-completes rather than a tree, and can now handle up to 10,000 Organizations, 10,000 Divisions per organization, and 10,000 Units per Division. Installations exceeding those numbers will still be able to enter the name without validation problems, and a link to the Organization Chart landing page will be available for browsing that data in a tree.
SR-D95797 · Issue 556765
Branch Preference now considered for TestCase rule
Resolved in Pega Version 8.4.2
Setting branch preference from top right worked for all rule types and new rule dialog rightly set the branch, but when attempting to use this configuration for a test case, it only displayed the first branch in the app and did not follow the branch preference. This was due to the system using a separate save modal dialog for test case creation which did not consider this use, and has been resolved by implementing the branch preferences use case to show the direct preferred branch if present.