ReactivateStep
The
REACTIVATESTEP
execute causes the FactoryTalk Batch
Server to journal a Step_Reactivation Request event.The format and return for this execute includes:
Execute Format | A FactoryTalk Batch Server supports an execute with this format:[REACTIVATESTEP( Item,UserID,RecipePath,StepIndex,
ReactivationNumber )] | |
where: | Item | Item name as specified by the client. |
UserID | User identification entered into the event journal associated with this event. | |
RecipePath | Path that represents the part of the recipe where the step originated. | |
StepIndex | Number representing the position of the step within the phase. | |
Reactivation
Number | Number representing the number of times the step has been reactivated. | |
Action | A successful REACTIVATESTEP execute results in a Step_Reactivation_Request event being queued pending a Signature Confirmation or a Step_Reactivation_Request event being written to the event journal. | |
Return Format | The item populates with this data: SUCCESS: | SUCCESS: <ActionID> | FAIL: <message> | FAILED | |
where: | ||
Field | Format | Description |
<ActionID> | ASCII – Integer | ActionID associated with the signature(s) generated in response to the execute. |
<message> | ASCII - String | Error message appropriately formatted for operator display. |
The following table shows an example of the return on this execute.
Example: | An execute string: [REACTIVATESTEP(Item321,JoeOperator,45133:CLS_FRENCHVANILLA\CLS_SWEETCREAM_UP:1\
CLS_SWEETCREAM_OP:1\ADD_EGG:1-1,4,0)] |
Provide Feedback