Academy
Process Automation

Execute a process

A process can be executed in two ways: manually, when you import files and trigger the processing immediately, or automatically, when the platform loads and processes data on its own — by scheduling, from another process, or through an external API trigger. This article covers both methods.

Complete flow: it is only possible to execute a complete data preparation flow, meaning with error-free steps and at least one data source step and one output step.

Manual execution

The Execute button opens the process execution screen, where you import the files that will run through the flow on a specific reference date. Finally, the platform loads and processes the files and directs you to the results viewing screen.

On the import screen, you need to:

  • define a reference date, the date on which the process results are stored;

  • select the files to be processed, choosing them from your computer or dragging them into the upload area;

  • associate the files with the flow's data sources, either manually or via identification rules, if no automatic identification rules exist.

Dates with results: in the reference date calendar, days that already have results appear with a green mark. You can navigate through the calendar and view results for different dates.

Import type

Still on the execution screen, you choose the data import method. The options appear only when there is no import on the execution date and vary according to the type of analysis.

Replace data is available in Turbo AI and Standard analyses and is the default option. It deletes all imported data and previous analyses for the date and replaces them with the new imported data.

Update execution is available in Turbo AI analysis and applies to Table Analysis and Reconciliation Analysis steps. It allows updating data from an execution without deleting the entire history, using a row identifier when configured. With the identifier, the platform compares the existing data with the new import:

  • records with the same key and the same data remain as they are and are not duplicated;

  • records with a new key are inserted as new records;

  • records with the same key but different data have the existing record updated;

  • old records whose key does not appear in the new import are not changed and remain in the history.

Without a row identifier, the platform cannot compare records between executions. In this case, all records from the new import are inserted in an incremental behavior, which may generate duplicates since old data is preserved.

Increment data is available in Standard analysis. It maintains previously imported data and increments the new ones. The incremental behavior refers to the data entry, not the analyses: if you import and an analysis has already been performed in Analytics or Recon, the data is cleared from the analysis to receive the new import.

In summary, when comparing Update execution and Replace data:

  • Objective: update data while maintaining history, versus recreating the execution data.

  • With row identifier: the update maintains the history, updates previously sent records, adds new ones, and preserves what was not resent; replacement removes all previous data and keeps only the new ones.

  • Without row identifier: the update increments the data and inserts everything from the new import; replacement deletes everything and inserts only the new ones.

  • Records not resent: remain in history during the update and are removed during replacement.

  • Recommended use: update is used for partial or recurring loads; replacement for full reprocessing.

Always replace: imports via API and the Integrate Process step always have their data replaced, without incrementing.

Process results

With the files selected and associated with the correct sources on the reference date, click Execute Process. The platform processes the results and displays the analysis screen.

Automated execution

In addition to manual execution, it is possible to automate data import. Automation can be triggered in three ways — by scheduling, from another process, or via an external API trigger. Settings are located in Settings (gear icon) → Automation. Under Automation type, you choose between:

  • None: does not apply any automation rule.

  • Scheduled process: defines the automation calendar that controls the reference dates, the execution time (with the option to add more times), and the offset relative to the period of the calendar.

  • Sequence from processes: triggers the execution of this process based on the execution of another. You select the desired process and the offset relative to the reference calendar period.

  • Sequence from Automation Flow: triggers the execution from an existing flow in the Automation Flows within the General Process Settings. You provide the trigger code — which also allows triggering the execution via an external trigger, such as an API call — and the offset relative to the reference calendar period.

How the offset works: the Scheduled process imports results for the reference date calculated by the automation calendar and the offset. For example, when executing the process on 03/01 with the Calendar Days calendar, it imports the data available on 03/01; with a "-2" offset, it imports data from two days prior, i.e., 01/01.

  • Introduction to Processes

  • Create a process

  • View and analyze

Was this helpful?
Was this helpful?