SR-A10040 · Issue 219561
Section refresh added to Integrator shape
Resolved in Pega Version 7.2
The Integrator shape in Data class was not showing parameters in the properties screen. A section refresh has been added to "pzIntegratorTab" that will be triggered upon selection of the rule in the integrator
SR-A10040 · Issue 219304
Section refresh added to Integrator shape
Resolved in Pega Version 7.2
The Integrator shape in Data class was not showing parameters in the properties screen. A section refresh has been added to "pzIntegratorTab" that will be triggered upon selection of the rule in the integrator
SR-A12450 · Issue 223679
Trailing line removed from breadcrumb
Resolved in Pega Version 7.2
When creating a work item, the breadcrumb showed a trailing line when it displayed "Review and Confirm". This was an issue with a page change class in middle of a screenflow, and has been fixed.
SR-A12537 · Issue 224734
Optimistic locking honors OfflineEnabled function
Resolved in Pega Version 7.2
After upgrade, if a top level case type rule was checked out through the Case Explorer by opening the Case Designer and then changing the locking mode to Optimistic, the value reset back to Default after check-in. This was an issue with the pyOfflineEnabled setting being honored, and has been corrected.
SR-A13730 · Issue 226426
Localization added to pyWaitLabel and pyInstructions
Resolved in Pega Version 7.2
The Rule-Obj-Activity Dependency of class 'Work-' was creating pyWaitLabel and pyInstructions which were not localized. This has been fixed.
SR-A6996 · Issue 215315
Localization added to pyWaitLabel and pyInstructions
Resolved in Pega Version 7.2
The Rule-Obj-Activity Dependency of class 'Work-' was creating pyWaitLabel and pyInstructions which were not localized. This has been fixed.
INC-128571 · Issue 584752
Auto-process assignments cleanup improved
Resolved in Pega Version 8.6
After configuring auto process with an assignment at the flow end, the perform harness was being presented at the end of the assignment during runtime. This was the result of the newAssign page not being removed as part of the cleanup after auto-processing was done, causing the performB2BAssignmentCheck activity to believe the next assignment existed. This has been resolved by ensuring that auto-process assignments have the newAssignPage removed after the assignment is deleted.
INC-134113 · Issue 591542
Child case locking error message has correct parameter
Resolved in Pega Version 8.6
A locking error message was appearing without the case parameter, showing "Error Message : Could not lock the cover ; has it. Please wait and try again later." This was traced to the cover already being present, causing the step to open the Cover Object to fail. To resolve this, and update has been added to pass the Cover case ID to the field value.
INC-135335 · Issue 588511
Parent flow next step will take precedence over sub-process
Resolved in Pega Version 8.6
ABreadcrumb configured in the screen flow was not displaying at the last assignment when there were multiple embedded sub processes and the last assignment was called in a sub process. This was traced to the parent flow next step information not being passed due to the next step in the sub process being marked as an end shape. To resolve this, the pzFlowSteps7 html control has been updated to pass the parent flow's next step information in this situation.
INC-135751 · Issue 587288
Null check added for embedded section pyInclude tag
Resolved in Pega Version 8.6
When attempting to implement a call to the Pega API casetypes endpoint, the end point /casetypes/{id} returned data for only some of the casetype IDs. For others there was no content in the response and in the logs the error "null at com.pegarules.generated.pzAPICreateJsonForGroup" was seen. This was traced to the use of an old section which did not generate the embedded section pyInclude tag. When the API was called on the same section, it tried to perform an equality check on the variable which gets the pyInclude value, and the null value caused the null pointer exception. This has been resolved by adding a null check to cover pyInclude in an embedded section.