Control the reset behavior for Attestation Approval Workflows (4322288)

Changes to workflows should work similarly to changes to processes.  For example, changes to processes do not affect running process instances, however, changes to approval workflows do affect running workflow instances.

Generally, there is a desire for versioning of workflows, e.g. is there any way to modify a workflow without resetting the escalation calculations within that workflow?

Modifying approval workflows for pending attestation cases

When approval workflows are changed, a decision must be made as to whether these changes should be applied to pending attestation cases. Configuration parameters are used to define the desired procedure.

Scenario: Another approval workflow was stored with the approval policy:

The newly stored workflow is only used in new requests. If changes have been made to the approval workflow in an approval policy, any pending approval processes are continued by default with the original workflow. The newly stored workflow is only used in new attestation cases. You can configure different behavior.

To specify how to handle pending attestation cases

In the Designer, enable the QER | Attestation | OnWorkflowAssign configuration parameter and select one of the following values.

• CONTINUE: Ongoing approval processes are continued with the originally applicable workflow. The newly stored workflow is only used in new attestation cases.
  • This behavior also applies if the configuration parameter is not set.
• RESET: In ongoing approval processes, all approval decisions already taken are reset. The approval processes are restarted with the newly stored workflow. The attestation cases are run through the approval process again.
• ABORT: Ongoing approval processes are stopped. All pending attestation cases are closed. The next automatic or manual start of the attestation uses the new approval workflow.

A working copy of the originally applicable workflow is saved. The working copy is retained as long as it is used in ongoing approval processes. All unused working copies are regularly deleted using the Maintenance approval workflows schedule.

Additional information can be found in the documentation linked here .