Command signature requests

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 Guide
.
The following is an explanation of the 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 determine 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:
ABORT command cannot be canceled by the user.
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 contains 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
When a Command Verification Policy is configured for a command, and the same Command is issued in Manual Phase Control against a Phase, a
Command Signature
 request is generated.
The following is an explanation of the 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 determine 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:
 ABORT Command cannot be canceled by the user.
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 contains 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 Reboot
Signature Requests generated in response to a Phase Execute Action are System Canceled in the event of a
FactoryTalk Batch
 Server warm boot.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal