Add Event Signature request

If a Comment Command Verification policy is configured in the area model and it is associated with a Signature Template, then an
Add Event Signature
 Request is generated when a user attempts adding a comment to a batch. For information on the AddEvent execute, see the
FactoryTalk Batch
 Server API Communication Language Reference Guide.
The following is an explanation of the modifications made to support
FactoryTalk Batch
 electronic signatures:
AddEvent Execute
Batch Server
When the
FactoryTalk Batch
 Server receives a legal AddEvent, AddEvent_Phase, or AddEvent_CI execute, it checks the Area Model configuration to determine 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.
Response
An ActionID is returned by the execute used to locate the generated signature.
Completion
When all Signature Signoffs associated with an AddEvent execute are completed, then the AddEvent action is handled if it is still legal.
Cancellation
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.
Overlap
AddEvent executes targeted at the same batch are permitted to overlap. If the batch has a Remove Action pending, then AddEvent execute fails.
Warm Reboot
Signature Requests generated in response to a AddEvent execute action are restored 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