The main functionality of Data Governor is used to execute “jobs” which consist of a sequence of “tasks”.
When viewing the tasks for a job, the “Sequenced Tasks” list shows which tasks will run in and in what order they will run in.
With this in mind, Data Governor jobs can be seen as a list of tasks which will execute individually in order.
All of the functionality detailed in this page require the user to at least be a “BI Developer” or higher.
If you wish to add a task to a job which doesn’t exist yet, clicking the “Add Task” button in the page header will take you to the new task form. Once you submit the new task, it will automatically be added to the sequenced tasks for the related job.
Tasks that are created in projects are completely re-usable across multiple jobs.
To add an existing task to a job, use the “Available Tasks” lists and select the tasks you wish to add with the + button.
Using the drag handles on the left of the tasks, you can easily drag and drop tasks in the order you wish them to be executed.
On the right side of the task sequence entry, you will notice there are a few actions that can be used to configure the task sequences even more.
These include (from left to right):
By default this is checked, “Enabled” sequenced tasks will be ran as part of the job. When unchecked, the sequenced task is skipped for future job executions until it is enabled again.
When a job runs, by default a failed task will not stop latter tasks from executing. By configuring task dependencies, tasks can require earlier steps in a job run to succeed before it can run. If any dependency fails, the tasks execution will be considered a failure.
Certain task types allow for parameters to be set when the task is sequenced. This allows for the same task to be re-usable across different jobs with different configurations.
Task parameters in Data Governor will always be treated as a
varchar, this means your tasks must explicitly
convert parameter values to other types such as numeric types explicitly.
Clicking the “Edit Parameters” button allows you to edit the parameter values for that particular task sequence.
In some cases your task parameter values will be shared across multiple jobs. Rather than providing the same values multiple times, you can easily provide Parameter Defaults in the task create/edit form.
Parameter Defaults will only be used when there has been no parameter value provided for the tasks usage in a job.
If we used a simple Powershell script as an example, where
$Name refers to a parameter with the same name:
Write-Output "Hello $Name";
We could map the defaults and values to an output like so:
|Parameter Default||Parameter Value||Final Output|
You can edit a task directly from the sequence list by clicking the “Edit Task” button.
Editing the task in the sequence will affect the task in all jobs. If you don’t wish to affect other jobs that use the task, it may be worth either creating a new task or cloning the task you wish to edit.
Clicking the trash button on the task sequence will remove it from the job sequence. Removing the task from the sequence does not delete the task and you can re-add the task to the job sequence from the “Available Tasks” list.