Report parameter deviation signature requests

The following is an explanation of how report parameter deviation signature requests are handled by the
FactoryTalk Batch
Server:
Report Parameter Deviations
Batch Server
The
FactoryTalk Batch
Server validates all real and integer report parameters according to the report parameter’s verification method as part of the upload process. In all cases, except one, the upload is completed and recorded in the event journal regardless of whether a deviation is detected. The exception occurs for a verification policy of "Not Allowed". In this case, the request fails and the value is not uploaded.
When the verification policy is "None", no electronic signatures or failures are generated, even if a deviation exists.
When the verification policy is "Signature Template", the server initiates any required signature prompts as defined by the signature template. The report upload is completed without failure – even if a signature is pending.
If a report limit value is not known, the server processes all the other report parameters, recording deviations, and report values then fails the upload request.
Response
An ActionID is returned by the execute used to locate the generated signature.
Completion
Completion of a signature generated for report deviation acknowledgment does not result in any additional action.
Cancellation
Report deviation signature requests cannot be cancelled.
Automatic Cancellation
There is no scenario under which a report deviation signature request is system cancelled.
Warm Reboot
A
FactoryTalk Batch
Server warm boot restores report parameter deviation signature requests.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal