INC-125706 · Issue 565518
Expression Builder test functionality updated to improve context resolution
Resolved in Pega Version 8.4.2
After upgrade, running a test in Expression Builder to evaluate an expression resulted in a 'Property undefined' error. Although the test functionality failed, the data transform rule was properly saved and no issues were observed at runtime. This was traced to a change made in the way the IDs on input elements were made unique. This caused an issue with Expression Builder resolving the correct context when the Source property page was not the primary page class, such as in these cases:1) For Each Page with the "Also use each page as source context" checkbox checked 2) Update page using the "with values from" 3) Append and Map to with "an existing page" 4) Append and Map to with "each page in" To resolve this, the pzEBHiddenElement function has been updated.
INC-125803 · Issue 568663
Cross-site scripting updated for pzTransformAndRun
Resolved in Pega Version 8.4.2
Additional Cross-site scripting work has been done on the pzTransformAndRun activity.
INC-126813 · Issue 565864
Handling added for Decision Table test case with "call"
Resolved in Pega Version 8.4.2
Clicking on the Convert to test button to launch a Test Case rule form did not load all of the options to create the UTCs, and the screen seemed stuck on the message “Loading..”. This was a corner case that happened when the decision table's return value had "Call" in it: the table believed there was the need to call another decision table, which was traced to "Call" being present on the RUT's label values. To resolve this as avoid regressions, quotes have been added to the returned value so that the value is picked instead of trying to call another decision table.
INC-127291 · Issue 562778
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-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.