Dova 22.0.5: capabilities and acceptance

Scope of this edition

This manual describes Dova 22.0.5 capabilities. Check the version reported by your environment before following a procedure: a documentation version or downloaded file does not establish which code is active in your installation. Accepting a change requires checking its result as well as its version label. Use a separate laboratory destination for the following checks.

Navigation and canvas

The editor reduces repeated work through a bounded geometry snapshot and coordination of visual updates. This optimization concerns canvas presentation; it does not turn API documents, execution results or tenant data into a shared cache. It does not change the meaning of saving, publishing or executing.

To check it, open a laboratory Mapping, select components, move them, connect ports and resize panels. Inspect connection alignment, selection, the inspector and maximized behavior. Undo and redo must retain the expected edit. Responsiveness depends on the graph, device and workload; no universal duration is promised, and extra memory does not replace CPU work.

DovaAI and assisted design

DovaAI uses the authorized tenant and current view internally. Language follows the conversation and history continues across module changes within the permitted context. The chat supports a compact presentation and window controls; guides identify concrete actions with brief messages.

The assistant knows the purpose and settings of the 36 current components. For example, to replace exactly jorge with Jorge, it can recommend Replace values with exact matching; this does not capitalize every possible name. Field selector retains only selected fields in both rows and schema.

You can attach a supported file and describe a goal to prepare a configured Mapping. Design context uses schema metadata rather than providing a permanent execution input. Review components, connections, settings and missing information before confirming creation. Creating a draft neither publishes nor executes it. Plan quotas and authorization checks remain in force.

Retain operational controls

Mapping, Session and Workflow retain separate purposes: transformation, execution context and orchestration. Save and publish their versions deliberately; inspect dependencies before updating consumers. A public worker shares capacity rather than access to other tenants' Sessions or data. Successful publication does not itself prove output correctness.

Acceptance checklist

1. Confirm version, tenant, role and location.
2. Test the canvas with synthetic data and verify the saved edit after reloading.
3. Ask DovaAI for a concrete recommendation and review its proposal before applying it.
4. Run a controlled attempt and compare Monitor, schema and expected output.
5. If something fails, keep authorized evidence and inspect state before repeating actions with external effects.

Verified reference for 22.0.5

This edition uses Dova 22.0.5 as its reference. Inspection of the active product confirms the 36 Mapping catalog components and the Start, Session, Decision, Timer and End tasks. Consult the transformation reference for Unpivot, Sequence, Hash fields and Rank, including fields, failure conditions and examples. Review an assistant proposal like any other draft before publishing or executing it.

Configuration contains Runtime, Execution profiles, Workflow Scheduler, Runtime health and Git / DevOps. Available actions depend on your permissions and configuration. For cloud workers, VM state and agent Runtime are separate checks: a started VM does not establish eligibility or successful execution.

Follow the Session and Workflow laboratory to learn the complete chain. Its synthetic data contains four input records and three expected results with column and value checks. The normalization demonstration also explains the genuine CSV chain with 18 input and 10 output records. Historical examples retain their original identification; they are not new runs in your environment.