Add Event Signature request

When the

FactoryTalk® Batch

Server receives a legal AddEvent, AddEvent_Phase, or AddEvent_CI execute, it checks the Area Model configuration to decide if a confirmation Signature is required for the AddEvent action. If one is required, then a Signature Request is generated using the specified Signature Template and the AddEvent action is queued pending completion of the Signature Request.

An AddEvent is not generated when all batches are selected.

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

When all Signature Signoffs associated with an AddEvent execute are completed, then the AddEvent action is handled if it is still legal.

When any Signature generated by an AddEvent execute action is cancelled, then the AddEvent execute action is terminated and its associated incomplete Signature Requests are System Cancelled.

AddEvent executes targeted at the same batch are permitted to overlap. If the batch has a Remove Action pending, then AddEvent execute fails.

Signature Requests generated in response to a AddEvent execute action are cancelled in the event of a

FactoryTalk Batch

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