INC-218543 · Issue 729993
Control added for Deployment Manager guardrail evaluations
Resolved in Pega Version 8.8
When using the Deployment Manager merge pipeline to merge branches from a development system, an exception was raised raised by the pzQueueProcessRuleForGuardrails activity of the Standard Queue Processor after every merge was completed even if it compiled successfully. As a result, after every branch merge a new broken queue item remained in the queue of this processor. Investigation showed the Deployment Manager creates and deletes Rule-Admin-Product instances faster than they can be queued for processing, resulting in this error. This has been resolved by creating pyIsApplicationGuardrailsEvaluationEnabled in Rule-Admin-Product that always resolves to false so that Product rules created by Deployment Manager do not create errors in pzQueueProcessRuleForGuardrails.
INC-218935 · Issue 728229
Keyboard access added for delegated decision tables
Resolved in Pega Version 8.8
Delegated decision tables were not accessible by keyboard, interfering with editing the table. This has been resolved by adding the tabindex and appropriate event handler of keyboard actions for the grid cells that are clickable/editable so the content of the popup to select the properties is accessible by the keyboard TAB and ENTER, and the decision table grid cells are now accessible via keyboard tab.
INC-219656 · Issue 717375
Null check added for Application/AccessGroup system pages
Resolved in Pega Version 8.8
In some scenarios the Application/AccessGroup system pages used by the Choose Best RuleSet API to group/cache the user's ruleset could be null, resulting in a null pointer exception when using the pxCreateRecord Activity for the data instance creation. A null check has been added to avoid the exception, and a complete resolution for the null pages will be available in a future release.
INC-220166 · Issue 724348
Declaratives processing temporarily disabled for DX API request
Resolved in Pega Version 8.8
After update, trying to navigate from one assignment to another assignment by using the DX API post assignment request displayed a date format error due to rule changes that caused the declare trigger to be called at the time of getting the response. This caused validation to fail. To resolve this, an update has been made to temporarily disable declaratives processing when processing DX API request content.
INC-220293 · Issue 726323
Operator ID ruleform "Reporting To" supports large number of users
Resolved in Pega Version 8.8
In a site with more than 10,000 operators, the "Reporting To" field in the operator ID rule form did not display operators beyond 10,000. This has been resolved by updating the Reports To component to an autocomplete in the Data-Admin-OperatorID!pzRoutingSettings, which is using the new data page D_pzGetOperatorsAndFilterByID and report pzGetOperatorsAndFilterByID.
INC-220385 · Issue 720008
Corrected Branch Code Score / Unit Test Rule count issue
Resolved in Pega Version 8.8
When reviewing branch quality, the "Rules with Test Cases" indicated 5 out of 7 rules were covered, but no rules were listed in the "rules without unit tests" tab and all rules within the branch had unit tests where applicable. Investigation showed the filter for withdrawn rules was not working correctly and they were shown as not having test cases. In addition, when a test case was in a branch but its tested rule was not in the branch, the test pass percentage calculation was being skipped and displayed as 0%. These issues have been corrected.
INC-220472 · Issue 729744
Circumstance template list correctly populated
Resolved in Pega Version 8.8
While creating the Circumstance definition, templates were populated on hit of the down arrow but the same configuration was not working for the dropdown for creating the circumstanced rule to select the template. Investigation traced this to an issue with the query generated in pzGetCircumstanceTemplateRules, and this has been corrected.
INC-220770 · Issue 718026
Null check added to getBaseRef
Resolved in Pega Version 8.8
When using a customized Cosmos portal that included tabs, some of the Pega APIs were not available in the child frame and javascript errors were generated when calculating the clipboard path for live UI elements. This was traced to invalid references to "pega.api.ui.util.getBaseRef", and has been resolved by adding null checks to the getBaseRef API call to make sure javascript errors are not thrown.
INC-222791 · Issue 721370
GET API will skip case locking
Resolved in Pega Version 8.8
After update, performing a GET call on an assignment was unexpectedly locking the case. This was traced to a difference in handling: Pega 8.3 performed an Obj-Open-By-Handle of the workobject without acquiring a lock, while Pega 8.6 calls Assign-.acquireWorkObject which acquires a lock on the work object thereby affecting the other requestors from accessing the case. An initial fix for this issue enabled optimistic locking, however this did not resolve the issue in scenarios where there were concurrent calls and optimistic locking was not used. This additional update will skip locks on the work object for V1 GET assignments/{id}, GET assignments/{assignmentId}/actions/{actionId} and GET cases/{caseId}/actions/{actionId} and corresponding action refresh APIs.
INC-224487 · Issue 729466
Security test status message includes assignment
Resolved in Pega Version 8.8
After update, the error message generated during a security test returned Status OK 200 but without any content. This was traced to a skipped step in pzGetAssignmentActionDetails activity and has been corrected.