---
title: "Boss’nX scenario actions: commands, values, delays and order"
description: "Add the actions of a Boss’nX scenario: command datapoint, value to send, delay in h m s and order of the actions per gateway, sequential or parallel."
canonical: https://wiki.can-nx.com/en/guides/boss-scenarios-actions/
language: en
product: Boss’nX
audience:
  - utilisateur
  - administrateur
  - installateur
context: "Boss’nX Time Programming editor: THEN — Actions section, including in Tuning mode"
---

# Boss’nX scenario actions: commands, values, delays and order

Context: Boss’nX Time Programming editor: THEN — Actions section, including in Tuning mode

The **THEN — Actions** section of the **Time Programming** editor defines what a Boss’nX scenario does: which command datapoint receives which value, after which delay and in which order. Actions are grouped by gateway.

For the person authorized to prepare or adjust the commands of the installation. To set when the scenario triggers, follow [the times and conditions guide](https://wiki.can-nx.com/en/guides/boss-scenarios-schedule/).

## Before you start

- The components, command datapoints, addresses and values to send are identified.
- To add or remove actions, your role has the **Edit scenarios** permission. In **Tuning mode**, only the existing rows can be changed.

## Add an action

1. In the relevant supervision, open **Menu → Time programming**. On a tablet or phone, **Menu** is at the right of the bottom bar.
2. Click **New scenario** or the pencil **Edit scenario** of the desired card, then scroll down to **THEN — Actions**.
3. Open **Component — Select a component...**, use **Search component...** if needed, then choose the right row. Its subtitle may specify the gateway.
4. Open **Datapoint — Select a datapoint...** and choose the intended command datapoint. Its address appears in the suggestions. If you change the component, select the datapoint again.
5. Fill in **Value** with the command suited to this datapoint, then click **Add action**. The button becomes available as soon as the component and the datapoint are chosen, without checking the value for your device.
6. Check the new row: component, datapoint, address, value and gateway group. The add selectors return empty; the added row is what counts.
7. Add the other necessary actions, then set their delays and order.

An empty list may come from the context, the accessible components or their gateway and address configuration. If the datapoint is missing or only intended for status feedback, have the command datapoint checked by the installer. Do not use a feedback address as a command without appropriate validation.

## Choose the value to send

**0 is an explicit value.** A cleared field is not equivalent to zero: always enter the desired command, without leaving the field empty to mean “off” or “no change”.

The row accepts a numeric or text value, whose meaning depends on the datapoint and its data type: 0 does not always mean Off, nor 1 On. The units and conversions of a displayed measurement are not enough to deduce the raw value to send. For an unknown value or data type, ask the installer or support for confirmation.

## Correct or remove an action

To correct an action, change the small field to the right of the **=** sign in its row. With the **Edit scenarios** permission, the cross on the right removes the action from the current edit. The address and the data type come from the chosen datapoint: the row offers no field to reassign them.

## Set the delays and order

Actions are grouped under their gateway; click the group header, with its chevron, to collapse or expand it. **Sequential** indicates the order of the actions in the same group. Between two groups, **Parallel (different gateways)** indicates that you should not count on a single order across all gateways.

Each row has three small fields on the left, **h**, **m**, **s**: the delay before this action in its sequence. Use positive integers or zero; minutes and seconds range from 0 to 59. For example, first action at 0 h 0 m 0 s, second at 0 h 0 m 5 s. This sequence delay does not check that the first device has finished its movement or its processing.

With the **Edit scenarios** permission, drag the vertical dotted handle on the left of the row to move it within its gateway. **In Tuning mode, keep the order of the rows**: adjust only their values and delays. Review the order, the datapoints, the values and the delays together before saving.

A datapoint can use a different gateway from the rest of its component: check the group actually displayed after adding. If the component or the datapoint has been reassigned since the scenario was created, have the existing actions checked, because they do not automatically follow the new assignment.

## Check the result

Click **Save** at the top right, wait for **Scenario created** or **Scenario updated**, then reopen the pencil from the list. Check the saved values, delays and groupings, as well as the final activation of the scenario, as described in [the creation and saving guide](https://wiki.can-nx.com/en/guides/boss-scenarios-create/).

Adding a row and saving do not test the hardware, and the actions form has no test button. To start the scenario on demand with **Execute**, follow [the viewing guide](https://wiki.can-nx.com/en/guides/boss-scenarios-consult/), then watch the devices.

## Troubleshooting

If a row is missing after saving, if the order or a value has changed, or if the command does not have the expected effect, note the scenario, the component, the datapoint, the expected result and the attempts made.

If the checks in this guide do not succeed, contact support@can-nx.com with this information. A screenshot without sensitive data can complement it; no password, key or internal log is needed.

French labels: **ALORS — Actions**, **Composant**, **Point de données**, **Valeur**, **Ajouter une action**, **Séquentiel**, **Parallèle (gateways différentes)**, **Enregistrer**, **Mode ajustement**.