First Workflow: from design to result

Before you start

Prepare a laboratory location in the selected tenant and permission to create, publish and run artifacts. You need a worker compatible with the files and an output you can inspect. The goal is retaining active customers, not load testing. Use synthetic data only.

The three artifacts serve different purposes: Mapping transforms; Session pins the revision and execution context; Workflow coordinates the task. Review each publication before moving to the next level.

Procedure

1. Create a UTF-8 CSV with header id,name,status and three synthetic rows. Include two active rows and one inactive row.
2. In Mappings, connect Flat File input → Row filter → Field selector → Flat File output.
3. Set Row filter to field=status, operator=equals, value=active. Set Field selector to fields=["id","name"]. Enable the output header.
4. Validate, save the draft and publish the Mapping. Create a Session referencing that revision, configure worker and file bindings, and publish the Session.
5. Create Start → Session → End in Workflows. Select the published Session revision, validate, save and publish.
6. Run manually and open the attempt in Monitor.

Synthetic example

Input:

id,name,status
1,Jorge,active
2,Ana,inactive
3,Bea,active

Expected output with these settings:

id,name
1,Jorge
3,Bea

Names and identifiers are fictitious. The file must be available to the chosen runtime; writing its name in a description does not create a binding.

Verify the result

Confirm terminal Workflow and task states, two data rows, header id,name and no status column. Verify that the Session references the revision you published. A file from an earlier attempt is not evidence of the current result; use a unique output or a mechanism identifying the attempt.

Only after acceptance should you consider scheduling. Review timezone, next execution and permissions. An active schedule does not replace verifying the next actual attempt.

Troubleshooting

For no rows, compare active exactly with source values: equals is case-sensitive. If status appears, inspect Field selector and the consumed revision. For waiting, inspect worker capacity and policy. For missing files, correct Session bindings. Do not blindly repeat writes after a timeout: check Monitor. DovaAI explains which components to use and how to configure them; you create, edit, publish and run the artifacts.

Environment context

Before using this module, confirm Tenant, Domain and Environment in the user menu. The initial environment is Development. Module, Domain and environment capabilities apply together; Production is read only without explicit authorization. Switching the selector does not move artifacts or publish or execute their data. See environments and recovery and environment promotion.