---
alias: user-guide-automation-task-opcua-oncommand
tags:
- automation tasks
description: "This task processes OPC UA method call arguments, preparing results for subsequent command handling"
---

# On Command

![Screenshot showing a command interface.](images/oncommand-lg.svg)

This task receives the input arguments of an OPC UA method call. To be used together with the CommandResult task.

![Screenshot showing a command parameter interface.](./images/on_command_parameters.png)

!!! warning
    This task is currently deprecated and will be removed in future versions.

## Inputs

None.

## Outputs

| Name     | Data Type | Values | Description                                                                   |
|----------|-----------|--------|-------------------------------------------------------------------------------|
| Id       | `Object`  |        | Uniquely identifies the OnCommand request                                     |
| Activate | `any`     | Yes    | Emits a true value whenever a new request is received (to active other tasks) |

## Settings

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

| Name    | Data Type | Default | Description  |
| ------  | --------- | --------- | --------- |
| Automation Command | `AutomationCommand` |  |  The command to send |

![Screenshot showing a UI with general parameter link options.](./images/on_command_settings.png)

On the *Parameters* Tab, you have entries for each of the parameters of the command:

![Screenshot showing a table with columns labeled "Name", "Data Type", and "Default" under the heading "On Command Settings Parameters".](./images/on_command_settings_parameters.png)

## Behavior

Select a command (corresponding to a OPC UA method) to subscribe and the task outputs will be generated based on the respective input arguments.

Every time the driver sends a message with the subscribed topic, the task parses the message contents and emits the values in the respective outputs.

## Remarks

None.