Management of a Schedule tasks

In summary

  • A task corresponds to an action to be performed, inside or outside DC-Maestro

  • A DataChain task corresponds to an action to be performed on a specific element (for example: Exposure of DataBlock - My DataBlock A)

  • Only the Owner and contributors can modify its tasks

  • All DC-Maestro users can see the Pipeline of a Public Schedule

  • Each task must be parameterized before being saved and executed

  • The setting varies according to the type of task

  • When a Schedule is executed, the execution request includes all the configured tasks visible in the Workflow

  • The execution status of a task is updated with each execution

Introduction

The notion of execution task is central in DC-Maestro.
A task is used to describe and manage the processing to be performed on a specific element.

Each task has metadata and several additional information

  • Task type: defines the action performed on the target element(s)

  • Label: briefly describes the task

  • Description: describes the task more precisely

  • Execution status: indicates the status for a given execution

  • Execution duration: indicates the execution duration for a given execution

  • DataChain element(s): specifies the element(s) on which the processing is carried out

Type of tasks

The number and type of tasks in a Schedule are not limited.

All DC-Maestro userscan create any type of task, but some may not be able to be configured or executed if the user does not have sufficient rights or permissions in the third-party application.

DC-Maestro does not allow you to manage the rights and permissions on the elements or the actions to be performed in third-party applications.
If necessary, go to GenericsData or HandleData to modify element.

DataChain task

Each DataChain task performs a defined action on a specific DataChain element.
From DC-Maestro, each user has access to the same elements as in DataChain (Depot, Business Entity, etc.)

The elements available for a task depend on several parameters:

  • the DataChain Project selected when the Schedule was created

  • the user’s DataChain global permissions

  • the rights on the element for the user

For example, to select DataBlock_A which is part of Project-P on an Exposure task, the user must:

  • be a member of Project-P

  • have "DataBlock" global permissions

  • have write permission on the DataBlock_A

Tasks -Description of DataChain tasks
Task Description

Business Entity Persistence

Updates the data of the Business Entity by a repersist action (depersists then persists).

DataBlock Persistence

Updates the data of a DataBlock by a persistence action.

DataBlock Exposure

Updates the exposed data of the DataBlock according to the parameters defined in DataChain. 2 options to "Publish" and "Activate" the API

Update API data BETA TESTEURS DCC V1.9 uniquement

Update API Publication data (API Exposure shared from HandleData)

DataBlock export

Performs an export of DataBlock data from an export template predefined in DataChain Core.

Dashboard publication

Update a publication

Executing Tasks

Tasks must be set up correctly to run.+

They are executed on behalf of a Schedule’s Owner, and therefore according to their DataChain permissions and rights to use elements at the time the execution request is received by DataChain.

For example, to run a Dashboard publication task on Dashboard "Dashboard A", the Owner must

  • have "Dashboard" and "Publication" global permissions

  • have the right to use publications on "Dashboard A"

If a contributor adds a task linked to an item to which they have access but the Owner does not, then the task will fail.

At each execution, DC-Maestro sends a new request: if the user’s rights change from one execution to another, the execution of the tasks will be impacted accordingly.

To learn more about executions, see the page dedicated to the execution.

Related pages