Integrate Process Step
The Integrate Process step retrieves data from an execution already completed in Dattos, allowing you to reuse data and results from other processes that have already been configured. This avoids rework and ensures standardization. The step is located in the Data Source category of the designer toolbar.
Before you begin
The type of process you are editing determines which sources Integrate Process offers. In a Standard process, the available sources are Process | Standard, Process | Turbo AI, and Package configuration. In a Turbo AI process, the sources are Process | Standard and Process | Turbo AI. The selected source indicates the type of process the data comes from: a Turbo AI process can import the result of a Standard process without any issues.
In environments where the legacy screens are disabled, you cannot create a new Standard process.
Define the data source
When adding the step, define the data source according to the process type.
In a Standard process, choose from:
Process | Standard: uses data from a process configured in the Standard model.
Process | Turbo AI: consumes data or results from a process configured in the Turbo AI engine.
Package configuration: uses a previously packaged configuration, with its structure and rules already defined.
In a Turbo AI process, choose between Process | Standard and Process | Turbo AI. In this model, integration focuses on existing processes, ensuring compatibility with current workflows and full use of the new processing engine.
Select the process and result
After defining the source, provide:
Select the process: displays the list of data preparation processes executed in Dattos. Choose the process to be imported.
Select the result: based on the selected process, select the result to be integrated into the current workflow.
Step name: identifies the step. By default, the platform fills it in with the name of the data preparation or source configuration package, and the field is editable.
Configure import conditions
Choose how the results will be imported from three conditions.
Single date based on the Execution Frequency Calendar imports the results available on the reference date calculated by the calendar and the offset specified when the data preparation was executed. You define:
Execution Frequency Calendar: displays the calendar registered in the imported result; if there is none, it uses the Calendar Days calendar by default.
Offset relative to the period: numeric field, default 0. Enter how many days before (-) or after the reference date the result was executed.
Date range based on the Execution Frequency Calendar imports the results available within a range, calculated from the initial and final offsets relative to the execution reference date. Imports whose reference date is greater than or equal to the calculated start date and less than or equal to the calculated end date are considered. You define:
Execution Frequency Calendar: same behavior as in the previous condition.
Initial offset: numeric field, default 0, with the number of days added to or subtracted (-) from the initial reference date.
Final offset: numeric field, default 0, with the number of days added to or subtracted (-) from the final reference date.
Last import execution performed imports the results from the last import executed at the source, regardless of the reference date.
Offset examples
For the single date condition:
Reference date 03/01, import the results from 01/01: Calendar Days calendar, -2 offset.
Reference date 31/01, import the results from 30/10: Last day of the month calendar, -3 offset.
For the date range condition:
Reference date 31/01, import everything executed between 01/01 and 30/01: Calendar Days calendar, initial offset -30 and final offset -1.
Reference date 31/01, import everything executed between 30/06 and 31/12: Last day of the month calendar, initial offset -6 and final offset -1.
Filter during import
You can bring in only the rows you need instead of importing the entire result and filtering it later with another step. The filter is applied before the data enters the workflow, reducing the volume at the source.
In the expression filter section, click Edit expression. Without an expression, the section displays No filter applied (optional).
In the editor, write one or more conditions using the columns from the source result. The result must be a logical expression, that is, something that can be answered with true or false. Example:
NUMBER({Cliente}) > 0.Click OK to apply, or Back to exit without making changes.
The editor is the same as the one in the Transform step, with the available columns, formula syntax, and functions on the left.
Tip: to avoid filtering, leave the expression empty. The step remains valid without a filter.
Configure optional information columns
The optional information columns add columns that are part of the imported execution to the step's output. They are visible in the Data Sample on the designer screen. The number of options displayed depends on the source result.
Always available:
Reference Date
Folder Code
Folder Name
Folder Path
Only when the source is the result of a reconciliation:
Justification Text
Reconciliation Status
Reconciliation ID
Rule Code
Rule Name
When you select a column, you can change the name under which it enters the workflow.
Tip: to carry forward only unreconciled items, select Reconciliation Status and then use the Filter step to keep only unreconciled rows.
Import the data sample
The platform lets you view a sample of the imported data, including the column, data type, and data sample from the configured source. Use Refresh Sample to reload a sample of the source columns. At the end, Save records the settings and Close returns to the designer without saving.
Related articles
Introduction to Processes
Configure Process
Run Process