# Commands

{% hint style="info" %} <mark style="color:blue;">Path: SBO > Others > Commands</mark>
{% endhint %}

* [Definition](#id-1.16.x-commands-definition)
* [Create commands](#id-1.16.x-commands-createcommands)
* [Read the commands section](#id-1.16.x-commands-readthecommandssection)
* [Update commands](#id-1.16.x-commands-updatecommands)
* [Delete commands](#id-1.16.x-commands-deletecommands)
* [Related resources](#id-1.16.x-commands-relatedresources)

## Definition <a href="#id-1.16.x-commands-definition" id="id-1.16.x-commands-definition"></a>

The commands part in the SBO should work automatically, without particular modification.

A command is a scheduled task done by the server. For each task, it will execute a control at a given time. That means the server verify pieces of information on the platform a few times per day, or hour to do some automatic tasks. Some actions can be derived from it such as: sending emails, updating booking status, and more.

<mark style="color:red;background-color:yellow;">WHO CAN USE THIS FEATURE?</mark>

Logged super-administrators

## Create commands <a href="#id-1.16.x-commands-createcommands" id="id-1.16.x-commands-createcommands"></a>

Commands can not be created.

## Read the commands section <a href="#id-1.16.x-commands-readthecommandssection" id="id-1.16.x-commands-readthecommandssection"></a>

Each task that can be controlled is composed of (figure 1):

* The name: indicates what will be triggered.
* The description: it describes what will be triggered.
* The periodicity: it is the time of control. It is based on the Cron system.&#x20;
* The next run date: it is the next date and time when the control will be done.
* The button “run”

<figure><img src="/files/CbjdEfbosCPyMMKg3vsU" alt=""><figcaption><p>Figure 1</p></figcaption></figure>

{% hint style="success" %} <mark style="color:green;">To test the booking expiration or the booking validation (for example), you can configure negative values in SBO > Other > Configurations, and run commands.</mark>
{% endhint %}

## Update commands <a href="#id-1.16.x-commands-updatecommands" id="id-1.16.x-commands-updatecommands"></a>

Commands can be activated manually by clicking “run” (figure 2).

<figure><img src="/files/uw0qMmlspmjREksrsUww" alt=""><figcaption><p>Figure 2</p></figcaption></figure>

The “run” button, allows the super-administrator to execute the control and not wait for the next planned trigger.

## Delete commands <a href="#id-1.16.x-commands-deletecommands" id="id-1.16.x-commands-deletecommands"></a>

Commands can not be deleted.

## Related resources <a href="#id-1.16.x-commands-relatedresources" id="id-1.16.x-commands-relatedresources"></a>

* *Computes the periodicity:* <https://crontab.guru/>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://features.scnd.com/v2.0/superadmin/configurations/commands.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
