Unit Bind Signature request

When the

FactoryTalk Batch

Server receives a legal Bind execute, the Area Model configuration is checked to determine if a confirmation signature is required for the Bind request. If one is required, then a Signature Request is generated using the specified Signature Template and the Bind action is queued pending Signature completion.

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

When all Signature Signoffs associated with a Bind Execute Action are completed, then the Unit Requirement targeted by the Bind Execute Action is bound to the specified Unit if the bind action is still legal.

When any Signature generated by a Bind Execute Action is cancelled, then the Bind Action is terminated and its associated incomplete Signature Requests are System Cancelled.

If a Bind Execute is received while an earlier Bind Execute Action is pending for the same target Unit Requirement, then the new Bind Execute fails. The failed execute’s response item is populated with an appropriate response string. For purposes of determining the legality of overlapping executes, Command, Step, Remove, and BindPhase Executes are treated as being Bind Executes. This means, for example, that if a Step Execute Action is pending Signature completion on a procedure, then a Bind Execute to the same procedure fails because of the overlap with the Step execute.

If any step associated with the Unit Requirement being targeted by a queued Bind Execute Action becomes an active recipe element, then the Bind Execute Action is terminated and its associated incomplete Signature Requests are System Cancelled. This happens because the Bind action is not legal for a Unit Requirement associated with any active steps.

Signature Requests generated in response to a Bind Execute Action are restored in the event of a

FactoryTalk Batch

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