Command signature requests

Overview

If a command verification policy is associated with a signature template, and a command is issued against a batch, a

Command Signature

request is generated and a dialog box is displayed.

For example: If a HOLD command requires a signature, then when a HOLD command is issued against a batch, an electronic signature request is generated and a dialog box is displayed. For information on command signatures, see

Acknowledge a Command Signature

in the

FactoryTalk Batch View User Manual

, publication

FTBVS-UM002

.

Modifications made to support FactoryTalk Batch electronic signatures

Modifications made to support FactoryTalk Batch electronic signatures
Command Execute
Batch Server	When a legal command execute is received, the FactoryTalk® Batch Server checks the area model configuration to decide if a signature request is required. If yes, then the command action is queued and a signature request is generated. Exception: ABORT command is not queued.
Response	An ActionID is returned by the execute used to locate the generated signature.
Completion	When all signature signoffs generated by the queued command are complete, the command is issued to the target procedure. Exception: ABORT command is issued regardless of Signature state.
Cancellation	When any signature is user canceled, then the queued command is terminated and all other signature requests associated with the same command action are system canceled. Exception: The user cannot cancel the ABORT command.
Overlap	If a command execute is received by a procedure that has incomplete signature requests for a prior command execute action, then the new command execute fails. A failed execute’s response item has an appropriate error message. Exception: ABORT command creating a command overlap terminates the original command action causing a system cancel instead of a failure. If ABORT overlaps with an ABORT command, then any incomplete signatures for the first command are system canceled and a new signature request is generated for the second command.
Automatic Cancellation	When a procedure transitions to a state in which a queued command action is not legal, the command execute action is terminated, and its associated incomplete signature requests are system canceled.
Cmd	Commands used with command verification policies are: START STOP AUTO-MODE PAUSE HOLD RESTART MAN-MODE RESUME ABORT RESET CLEAR_FAILURES DISCONNECT SEMIAUTO-MODE

Phase Executes

Modifications made to support FactoryTalk Batch electronic signatures
Phase, Phase2, Phase3 Executes
Batch Server	When a legal command execute is received, the FactoryTalk Batch Server checks the area model to decide if a signature request is required. If yes, then the command is queued and a signature request is generated. Exceptions: Phase Reset and Phase Disconnect. Batch is created regardless of whether a Signature is required, or if the Signature is canceled. ABORT command is not queued.
Response	An ActionID is returned by the Execute used to locate the generated signature.
Completion	When all Signature Signoffs generated by the queued command are complete, then the command is issued to the target procedure. Exception: ABORT command issued regardless of Signature state.
Cancellation	When any Signature is user canceled, then the queued command is terminated and all other Signature Requests associated with the same command action are System Canceled. Exception: The user cannot cancel the ABORT command.
Overlap	If a Phase Execute is received by a procedure that has incomplete Signature Requests for a prior Phase Execute Action, then the new Phase Execute fails. If a Command Execute is received by a phase that has incomplete Signature Requests for a prior Phase Reset or Phase Disconnect, then the new Command Execute fails. The failed Execute’s response item has an appropriate error message. Exception: ABORT command creating a command overlap terminates the original command Action causing a System Cancel instead of a failure. If ABORT overlaps with an ABORT command, then any incomplete Signatures for the first command are System Canceled and a new Signature Request is generated for the second command.
Automatic Cancellation	When a procedure transitions to a state in which a queued Action would not be legal, the Execute is terminated, and its associated incomplete Signature Requests are System Canceled.
Warm Restart, Warm All Restart, or Hot Restart	Signature Requests generated in response to a Phase Execute Action are System Canceled in the event of a FactoryTalk Batch Server Warm Restart, Warm All Restart, or Hot Restart.