Glossary

Corresponds to a DataChain Instance, referenced in DC-Maestro and selected by a user from the list. The Working Instance allows users to access the Scheduling functionality for this specific DataChain Instance.

Elle est obligatoirement liée à une unique version de Projet DataChain et possède un unique Propriétaire. It is necessarily linked to a single DataChain Project and has a single Owner.

User in whose name tasks are executed. The Owner must have appropriate rights on the selected DataChain item for the task to be performed (for example the right to persist the DataBlock My DataBlock). By default, the Schedule’s creator is its Owner.

The notion of Project is inherited from DataChain. Chaque Planification est reliée à une unique version d’un Projet DataChain. Each DC-Maestro User only has access to the versions of DataChain Projects of which they are a member.

A Project version belongs to a DataChain Project and has a version number.
In DC-Maestro, the version associated with a Schedule defines the DataChain elements available for its tasks.
This number refers neither to the DC-Maestro software version nor to the latest saved state of the Workflow.

The active version is the version designated as active in the DataChain Project (the reference version).
This indication is distinct from the active or inactive status of a Schedule.

Executing a Schedule is equivalent to carrying out all the tasks it contains. Execution* can be manual or automatic, i.e. it can be carried out automatically on a recurring basis. Each execution is historied and it is possible to consult each task execution log.

A DC-Maestro task is an action to be performed. DataChain tasks correspond to a specific action to be carried out (Export of a DataBlock, Extraction of an Entity, Publication of a dashboard, etc.) and applied to a precise DataChain element (DataBlock A, Publication B of Dashboard A).

Each time a Schedule is executed, the status of each of its tasks is updated.
The Schedules list and Workflow display the last known status of the tasks.
The execution history allows you to see the status of each task for each past execution.

Each time a task is executed, it is possible to access its execution log by clicking on the task status icon.
The execution log provides access to a lot of information about the task execution.

A set of associated tasks is called a pipeline of tasks.
The pipeline is created from the Workflow of a Schedule and must be a valid DAG (Direct Acyclic Graph).
When a Schedule is executed, every task within its pipeline runs either in the pre-established sequence or simultaneously for or unconnected tasks.
If a task, which has dependent tasks, fails during execution, the dependent tasks will not be executed.

The Workflow allows you to see how the different tasks of a Schedule are organized, as well as adding, deleting and modifying tasks. Only the Owner can modify the Workflow.