Prepare a laboratory
Use synthetic data, a separate destination and an authorized identity. Confirm the selected tenant and active role before creating objects. A Repository location organizes items; it does not grant permissions. Use a read-only source Connection when the exercise does not require changing the source. Enter credentials only through the protected Connections mechanism, never in names, descriptions, example parameters or messages to DovaAI.
Build a verifiable chain
- Create a small Mapping and configure its source, transformation and target. To test exact replacement, use Replace values with
field=name,find=jorge,replacement=Jorge,matchMode=exactandcaseSensitive=true. - Validate and save the draft. Publish the accepted version: saving and publishing are separate actions.
- Create a Session referencing that Mapping version. Review connections, inputs, outputs, execution profile and authorized capacity.
- Create a Start → Session → End Workflow. Save, validate and publish deliberately.
- Start one laboratory attempt; compare Monitor and the produced file with the expected result.
An execution file path must exist where the worker can use it. Attaching a file to DovaAI to inspect its schema does not establish a permanent worker input. Keep the laboratory destination separate from business output throughout the exercise.
Accept before scheduling
For this example, verify that jorge becomes Jorge and ana remains unchanged. If you add Field selector with fields=["name","amount"], check that the output schema and final header contain only those fields. A succeeded status does not replace this functional comparison.
Enable a schedule only after accepting the result. Check its timezone, published dependencies and destination effects. A public worker offers eligible capacity: it does not publish another tenant's Session or data. Available slots do not guarantee access to a Connection either. Record the accepted versions so a later change can be reviewed against the same baseline.
Resolve incidents without duplicate effects
If the client times out, inspect the attempt before submitting another. Cancel, terminate, rerun and recover are different actions. A retry may repeat external writes; review idempotency and persisted state. When a dependency changes, inspect consumed versions before publishing consumers again.
Keep authorized result evidence and remove only reviewed laboratory objects. Purge contents is destructive and requires scope confirmation; it is not a routine error-recovery step. For denied access, check membership, role, plan and resource eligibility before requesting additional permissions.
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.