Set parameter signature request

If the target is a recipe phase parameter, the

FactoryTalk Batch

Server checks the area model to determine if a Signature Request is required for SetParm Execute confirmation. If yes, then a Signature Request is generated. The server also checks for deviations on the recipe phase parameter. If the SetParm Execute target is a formula parameter, then the server checks all recipe phase parameters that reference the formula parameter. If deviations are detected, then the appropriate Signature Request(s) are generated. If one or more signatures are generated, then storing the specified value to the parameter is deferred until all Signature Requests are complete.

An ActionID is returned by the execute that is used to locate the generated signature(s).

When all generated Signature Requests associated with the SetParm Execute are complete, then the value passed in the SetParm Execute Action is stored into the specific parameter.

When any incomplete Signature associated with the SetParm Execute is cancelled, then the entire SetParm Execute Action is terminated and all Signature Requests associated with the same SetParm Execute Action are System Cancelled.

If a SetParm Execute is received targeting a parameter that has incomplete Signature Requests for a prior SetParm Execute Action, then the new SetParm Execute fails. The failed Execute’s response item has an appropriate error message. The specified value is not stored in the specified parameter.

If any incomplete Signature Requests associated with a SetParm Execute is user cancelled, then the Execute Action is terminated and its remaining incomplete Signature Requests are System Cancelled.

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

FactoryTalk Batch

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