Active Step Change Signature request

When the

FactoryTalk Batch

Server receives a legal Step execute, the Area Model configuration is checked to decide if a confirmation signature is required for the Active Step Change action. If one is required, then a signature request is generated using the specified signature template and the Active Step Change action is queued pending signature request completion.

An ActionID is returned by the execute used to locate the generated signature.

When all signatures associated with a Step execute action are completed, then the queued Step execute action is performed if it is still legal.

When any signature generated by a Step execute action is cancelled, then the Active Step Change action is terminated and its associated incomplete Signature Requests are System Cancelled.

When a Step execute is received targeting a procedure that already has a pending Step execute action, then the new Step execute fails. The failed execute’s response item is populated with an appropriate error message.

For purposes of determining overlapping legality executes, the Command and Remove execute actions are treated as being Step execute actions. This means, for example, that if a Step execute action is pending signature completion, then an AUTO command issued via a Command execute to the same procedure fails because of the overlap with the Step execute action.

Signature requests generated in response to a Step execute action are cancelled in the event of a

FactoryTalk Batch

Server Warm Restart, Warm All Restart, or Hot Restart.