SR-D63031 · Issue 526243
Reusable assets default option populated correctly for new application
Resolved in Pega Version 8.2.6
When creating an application with at least two case types where each case type belonged to different class groups and pointed to different tables but were configured to have only one work pool, operator work pool values for pxThread and pxRequestor did not correctly reflect the different access group settings. This was traced to the inheritance of default values when the portal pyPortal.pyDesktopType was set to Composite, which caused the system to always take the value from the work pools in the application whether or not it was the same value as specified. A check has now been added so that the system will only default to using the value from the work pool if no value has been specified.
SR-D64528 · Issue 528758
Decision table rule scrolling fixed for low resolution screens
Resolved in Pega Version 8.2.6
While scrolling right, the Tool bar in a decision table rule was moving right while the remaining screen moved left. This was traced to the the screen resolution being less than decision table toolbar width, allowing an infinite scroll. To support low resolution screens, the decision table grid has been made scrollable to resolve this.
SR-D69927 · Issue 537485
Cleanup added for staging directory
Resolved in Pega Version 8.2.6
Temporary files from imports and exports (from DevOps) were filling up the staging area disk space because there was no automatic process for cleaning up these local files. This has been resolved by adding an enhancement that will clear the directory on Engine Startup and any time ParUtils.setStagingDirectory gets called to initialize the staging directory.
SR-D72141 · Issue 542662
Approved flow rule image unlocked
Resolved in Pega Version 8.2.6
When the Approval Required check box was enabled for rulesets (i.e another person with access to this work queue should approve changes to the rules), a rule which was approved was unlocked and moved back to the original ruleset as expected, but the binary image associated with the flow rule remained locked and any other user other than the one who previously checked in the rule was denied access with a "check out failed" error. This locking error has been resolved by modifying the Rule-Obj-Flow!CleanUp activity to set Param.IgnoreInstanceLockedBy = true.
SR-D72672 · Issue 536388
Security updated for CreateOperator
Resolved in Pega Version 8.2.6
In order to improve security, CreateOperator in Pega-ProCom will require authentication to run with pxCanManageUsers privilege.
SR-D75469 · Issue 538121
Resolved null-pointer exception in Expression Builder launch from activity rule
Resolved in Pega Version 8.2.6
A NullPointerException occurred in SafeURL when trying to launch the Expression Builder from an activity rule. This was trasced to a failure to get a value property in a target field due to the target element and its parent element containing the same value for name attribute. This caused the parent element to be considered instead of the target element. To resolve this, the search for the target element in parent tag will use '$p' along with 'target element name' in query selector.
SR-D78698 · Issue 545386
Improved temporary page clearing for UpdateAndDeleteAssignments
Resolved in Pega Version 8.2.6
When using the Change Stage shape in a flow to move it to the Complete stage, the expectation is that the status should be set to Resolved-Completed and all open assignments should be deleted. In some scenarios, the audit history showed the case moved to the Complete stage and the assignments deleted properly, but the case status was not set to Resolved-Completed. This was traced to the temporary page "pgWork_x" getting leaked from pzUpdateAndDeleteAssignments activity when a case is being processed to closure (via pzProcessResolutionStage > pxForceCaseClose path). When the same work object was reprocessed in the same thread and the findPageByHandle(WorkObjectID) function received this temporary page's reference, then the actual operation was not committed to the database. To resolve this, updates have been made to remove the precondition at step#15 of the pzUpdateAndDeleteAssignments activity to ensure the temporary page gets removed appropriately.
SR-A19119 · Issue 241157
Improved error handling for XML-executed BIX extract failures
Resolved in Pega Version 7.2.2
When BIX extracts configured through an XML script encountered a target table that did not exist, the script itself did not visibly fail even though the error "Table doesn't exist in target database" was logged, and any extracts that were executed after that error did not generate any output. This has been corrected to set the correct error flags to ensure expected behavior.
SR-A76706 · Issue 252781
Modified pyLoadDataTypes data transform to match expected type
Resolved in Pega Version 7.2.2
Activities configured with "Double" as the data type were converted to "String" datatype in the activity after upgrade. This was due to the Data Transform pyLoadDataTypes rule using the pyLabel "DOUBLE" for double parameter type instead of "Double", and has been corrected.
SR-A77495 · Issue 254777
Corrected delete error with first row of Decision Table
Resolved in Pega Version 7.2.2
After clicking 'delete row' on the first row of a decision table the first row was not visible, but it was observed that when saving the first row it remained as it was and instead the second row was deleted. This was an error in highlighting and positioning, and has been fixed.