INC-135751 · Issue 587289
Null check added for embedded section pyInclude tag
Resolved in Pega Version 8.3.5
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.
INC-135335 · Issue 588512
Parent flow next step will take precedence over sub-process
Resolved in Pega Version 8.3.5
A Breadcrumb 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-133615 · Issue 581399
Rendering corrected for contextual prompt in Case Type
Resolved in Pega Version 8.3.5
In Case Type with multiple stages, clicking to add step->More at the last stage caused the More menu to be distorted and not usable. Investigation showed that whenever the contextual prompt was opened in this way and the layout had no space on the right side, it shifted left and moved beyond the visible layout. This was traced to the two column layout in pxContextualPromptWithPreview having display styling set to block, and has been resolved by updating this setting to display as table.
INC-136327 · Issue 591468
Stage keeps proper order placement on restart
Resolved in Pega Version 8.3.5
When a user restarted a stage, the stage moved to the end of the list of stages and stayed there even when completed. Investigation showed that when pxRestartStage was configured as a post-processing activity for a flow action, pxStageHistory was updated with a new list item which considered pxCameFrom and pxStageId as the same. Due to this, the current stage was moved to last in the chevron. This has been resolved by adding a new 'when' condition to pzLoadStageStatusDP that will skip the item of pxStageHistory (Alternate stage) if both .pxCameFrom and .pxStageId are same.
INC-139861 · Issue 594008
Cross-site scripting protections added to Case Email
Resolved in Pega Version 8.3.5
Cross-site scripting updates have been added to rules handling linked email correspondence.
INC-161463 · Issue 638001
Case Dependency corrected for different access groups
Resolved in Pega Version 8.6.1
Creating a queue item as part of the case dependency was not working as expected when the access groups of the dependent cases were different. Investigation showed that in this scenario, the logic was looping differently and the DependencyList page in pxCheckFlowDependencies was getting removed. To resolve this, the DependencyList page has been moved so it is processed inside the DependencyList.pxResults loop.
INC-161948 · Issue 638961
Locking settings enabled for circumstanced case types
Resolved in Pega Version 8.6.1
Optimistic locking options were not present for a circumstanced case type, and the option to select the "Lock parent case when an action is performed on this case" check box was not available. However, when the parent case type was enabled with optimistic locking, a circumstanced child case could inherit a lock from its parent. Because "Lock parent case when an action is performed on this case" was not enabled on the circumstanced child case type, trying to update the parent case from the child case and save the parent case resulted in a "Lock not held on parent" error. This was a missed use case, and has been resolved by enabling locking settings in Case Designer for circumstanced case types.
INC-162168 · Issue 634933
Refresh works for nested lists
Resolved in Pega Version 8.6.1
After creating Pagelist A with another Pagelist within (B), a section was created with a repeating dynamic layout to display Pagelist A and a button was added with action set to refresh this section. In the embedded section of the repeating dynamic layout, a nested repeating dynamic layout was created for Pagelist B and a button was set to refresh this section. When using this configuration, the refresh was returning the actionID for Pagelist A regardless of which button was used. To resolve this, an update has been made which will iterate over the stack and append the individual indexes to the encoded value in the pzAPICreateJsonForField function.
INC-162763 · Issue 646112
Case creation and Save As performance improvements
Resolved in Pega Version 8.6.1
Performance improvements have been made to the getApplicationRuleSetList() function to avoid unnecessary and repetitive database calls.
INC-163154 · Issue 638098
Code updated for bulk actions buttons
Resolved in Pega Version 8.6.1
After update, hovering over the "Filter case" button in pzBullkUpdate and the "Create" and "Clear" buttons in pzBulkAddActions caused them to disappear. The warning "This button generates markup that was used to support the older browsers. It is recommended that you update it to the newer markup" was shown, and an update code button appeared. Some custom rules exhibited the same behavior initially, but worked as expected after updating the code and saving them. This has been resolved by updating the buttons in pzBulkUpdate and pzAddBulkActions with the latest UI technologies used for button control codes.