---
alias: user-guide-automation-task-fa-transportrequester
tags:
- automation tasks
description: "This documentation details a task for managing fleet operations through a message bus, handling requests and responses"
---

# Transport Requester

The task `Transport Requester` is a Task that performs fleet management (AGV) through the message bus. Sends a command request (to a "Receiver"), typically to other tasks of fleet managing related workflows (that have the specific vendor drivers). It also waits for and handles the reply.

![transportrequester_parameters][transportrequester_parameters]

## Inputs

| Name        | Data Type | Values | Description                          |
|-------------|-----------|--------|--------------------------------------|
| id          | `any`     |        | request id                           |
| rawValues   | `any`     |        | values to be included in the payload |
| source      | `any`     |        | source of the request                |
| destination | `any`     |        | destination task for the request     |
| priority    | `Integer` |        | request priority                     |
| unit        | `any`     |        | input data for the job to create     |
| Activate    | `Any`     |        | Activates the task execution         |

Table: Transport Requester inputs

## Outputs

| Name    | Data Type | Values | Description                                            |
|---------|-----------|--------|--------------------------------------------------------|
| id      | `any`     |        | job id                                                 |
| data    | `any`     |        | data for the job                                       |
| message | `any`     |        | message to send                                        |
| Success | `Boolean` |        | If there was no problem emits a true                   |
| Error   | `Error`   |        | Error that occurred during the processing of this task |

Table: Transport Requester outputs

## Settings

On the `General` Tab, you have the usual settings and the following options settings:

| Name                       | Data Type | Values                                                                              | Default          | Description                                                                                                               |
|----------------------------|-----------|-------------------------------------------------------------------------------------|------------------|---------------------------------------------------------------------------------------------------------------------------|
| Fleet Manager Type         | `enum`    | `KNAPP`<br />`MIR`<br />`Custom`                                                    | `KNAPP`          | Fleet manager type (to differentiate between implementations). If *Custom* selected, Fleet Manager Type must be specified |
| Command                    | `enum`    | `Transportation`<br />`Interaction`<br />`CancelTransportation`<br />`StatusUpdate` | `Transportation` | Command to send to the Fleet manager.                                                                                     |
| Attempts                   | `Integer` |                                                                                     | 100              | Initial command send request number of attempts before quitting                                                           |
| Sleep between attempts     | `Integer` |                                                                                     | 5000             | Initial command send request waiting time between attempts (in milliseconds)                                              |
| Command timeout            | `Integer` |                                                                                     | 7200000          | Command waiting time between attempts (in milliseconds)                                                                   |
| Clear Inputs (on activate) | `Boolean` |                                                                                     | `true`           | Defines if it is to clear the input values after receiving an activate                                                    |

Table: Transport Requester settings

![transportrequester_settings_step_one][transportrequester_settings_step_one]

Additional inputs can be defined in the `Inputs` tab:

![transportrequester_settings_step_two][transportrequester_settings_step_two]

Additional outputs can be defined in the `Outputs` tab:

![transportrequester_settings_step_three][transportrequester_settings_step_three]

## Behavior

This task is suppose to be used within the workerManager nested workflows (during a job execution). You should provide task related configurations, fleet related configurations (fleet manager type and command to perform) and also communication related settings (timeouts)

!!! info
	The `Transport Requester` task is only activated when a value different from *False* is sent to the *Activate* input.

## Remarks

None.

[transportrequester_parameters]: ./images/transportrequester_parameters.png
[transportrequester_settings_step_one]: ./images/transportrequester_settings_step_one.png
[transportrequester_settings_step_two]: ./images/transportrequester_settings_step_two.png
[transportrequester_settings_step_three]: ./images/transportrequester_settings_step_three.png