Running the DTP
Run priorities¶
The process for running DTPs in various execution contexts is provided below.
| Element | Description |
|---|---|
| Runs several DTPs simultaneously | By default, it is not possible to run, in the same execution context (Process, Scenario, Period, Entity), at the same time DTP data processes containing at least one identical dataset/type. Any data processing started during the data processing that is already in progress will be carried out once it has ended, in the run order. Note: When data processing is run from a workflow task in parallel with a data processing already in progress, containing at least one identical dataset/type, the system displays a window in which the user can choose whether to cancel the launch, retry or put the data processing in the queue. In all cases (workflow, form, API, job) the system performs a check on the resources used by the DTP and Update Financial Workspace from Analytical Workspace running data processes; if there are resources already used by the current data processes, the booking is done automatically. The waiting time will be indicated in the audit under 'Data processing started' with the heading 'Wait before the run'. |
| Run DTPs with the run independently from context option active | A DTP containing tasks with the run independently from context option will never be queued, but run in parallel with any other data processing that is in progress. DTPs with the run independently from context option can be run in parallel with other data processing, whether or not they are associated with a task with "run independently from context". |
| Run DTPs simultaneously from task groups or workflows in grid | By default, concurrent data processing of the same type is not supported, whether the data processing is run from task groups or workflows in grid. Data processing by task group runs the different DTP tasks of the group in series, regardless of the order of the workflow. Launch workflow in grid: enables the simultaneous launch of different DTPs on different list elements |
| Run DTPs simultaneously from task groups or workflows in grid with tasks with the run independently from context option active and tasks on which the option is not active. | When the run independently from context option is only active on some workflow tasks, and several DTPs are run simultaneously, the system performs concurrency checks. Based on the outcome of the checks, run from tasks that do not have the option active, the data processing is run or added to the queue. |
| Run DTPs with activities or operations containing SQL scripts | Opens a window to define the parameters required at runtime. For further details on the definition of those parameters, see |
In all execution contexts, if the DTP contains personal data, the DTP data processing can only be run correctly if the data are properly encrypted (see Personal Data Protection).
Run the DTP for entity nodes¶
The DTP data processing involves data divided by Scenario/Period and Entity. When a data process is run for entity nodes, the DTP may behave differently based on the setup:
| If... | Then... |
|---|---|
| all the DTP targets are partitioned by Business Cycle and Entity. | the DTP is processed individually for each entity. The data processing can be run in parallel if all the execution conditions are satisfied. To run multiple data processing, all the entities must have the same workflow as the selected node. |
| the datasets are not partitioned by Business Cycle and Entity | the DTP is run just once, with a data process containing the data of all the entities present in the node. |
When the system detects a case that is different from those listed, it blocks the data process and reports the error.
Note: when several entities are selected in the contributor cockpit, the DTP execution can only be completed if the tasks selected in the detailed task list do not run the same DTP for the same entity.
To run the DTP data processing by entity node from forms, the following syntax is necessary: <$Entity.Dimension.hierarchyCode>|<$Entity(false).code>.
Run the DTP independently from the context¶
On DTP tasks it is possible, via forms, to activate the Run independently from context option, which allows you to run them in parallel with any other DTP data processing.
With the option active, the data on partitions with typologies other than Reporting layer will not be saved.
This option prevents the use of partitions with Calculation layer typology in read/write mode if these are the result of data processing originating from other DTPs.
Run the DTP from Jobs¶
When the execution of DTP data processing is run from a job, the statuses on the DTP cockpit are not updated. Both with jobs g run from the processes cockpit and with jobs run from a job's run menu, the system saves neither the anomalies deriving from the checking operations nor the operation start and end dates. The information on the last execution prior to being run from a job remains visible.
Data processing ended with anomalies¶
When the execution of DTP data processing involves check operations, these generate anomalies if the check fails.
Editability checks¶
When DTP is run, it does not apply editability checks on data.
Thus, for example, it is possible to process submitted entities, or data locked at process level (e.g. with the 'Lock Data' function).
Editability checks are applied instead, for example:
- when loading data via Datasource Mapping;
- during the Update Financial Workspace phase;
- when writing to the Reporting Layer, if the Loading operation 'Write to another dataset' is used.