Abort Request#
This task receives an AbortRequest event from the Worker Manager and emits the outputs so that some custom logic can be done to decide if the Abort request will be allowed or denied. Based on that custom logic decision, this Task will either receive an Allow or a Deny input and will send the result to the WorkerManager, according with that received information.
Details#
| Fields | Details |
|---|---|
| Scope | Factory Automation Enterprise Integration Data Platform |
| Workflow | Data flow Control flow |
IsProtocol flag |
Inputs#
| Name | Data Type | Values | Description |
|---|---|---|---|
| Allow | any | Triggering this input will result in the AbortRequest success | |
| Deny | any | Triggering this input will result in the AbortRequest failure |
Table: Abort Request inputs
Outputs#
| Name | Data Type | Values | Description |
|---|---|---|---|
| job id | any | Triggered with the current JobId after receiving an AbortRequest event | |
| Raw | any | Emits the raw data received in the AbortRequest event | |
| Activate | any | Activates the task execution |
Table: Abort Request outputs
Settings#
On the General tab, you have the usual settings. Additional outputs can be defined in the Outputs tab.
Behavior#
This Task needs to be used with the Worker Manager which will start this Task through the AbortRequest event. After that, custom logic can be added to the Workflow and then link it to the Allow / Deny inputs of this Task, with the result decision.