Before you start
A Mapping defines the transformation algorithm. A Session supplies execution context and a Workflow coordinates tasks. Select the correct tenant and an authorized Repository location. Editing permission is required; publishing and running are additional actions. Prepare synthetic input and expected output without credentials or customer data.
A component in the palette does not guarantee compatibility with every worker. Check the runtime, especially for external connections and graphs containing Join.
Procedure
- Open Mappings and create a draft in the appropriate Domain and Folder. Use a descriptive name.
- Add components from their categories and connect each output to the next input. Select a component to configure its inspector.
- Set source headers, names and types before configuring transformations. Review Join keys and the columns reaching the target.
- Use Validate to resolve graph problems. Save persists the draft. A local-save indicator does not replace this action.
- Publish only after saving every change. Publish requires a saved draft with no pending edits; it does not execute the Mapping.
Field selector: keep only selected fields
To retain only two CSV columns, connect Flat File input → Field selector → Flat File output. Set hasHeader=true, delimiter=, and fields=["name","amount"]. The selector preserves values and rows but removes all other columns from the schema. The target uses that schema; fileName does not select fields.
Verify the result
Reopen the draft to verify persistence. Review the published revision before binding it in a Session. Execute a sample using authorized capacity and compare headers, rows and values with the expected result. Successful structural validation does not establish that files exist on a worker or that the output meets the business rule.
Ask DovaAI which components, connections and values fit your goal. The assistant gives brief instructions; you configure, save, publish and run through the normal Dova controls.
Troubleshooting
If Publish is disabled, check saving, pending changes, location, permissions and editing locks. If extra columns appear, inspect saved Field selector settings, the connected branch and the revision used by the Session. Correct runtime bindings for missing files. For streaming incompatibility, check the adapter: generic streaming requires a supported linear path. Do not remove necessary steps merely to make validation pass.
Apply different operations to different fields
Connect two Clean text components in series:
Raw file → Clean text 1 → Clean text 2 → Target
- Clean text 1: Fields =
first_name; Operations =trim. - Clean text 2: Fields =
last_name; Operations =upper.
Both fields travel together. Each component changes only its selected field and preserves the others. These two operations need neither a split flow nor Field mapper.
Delete a canvas selection
Select the item and press Delete with focus inside the canvas. The shortcut must not remove components while typing in an input, textarea or another editor. Review affected connections and validate the graph after deletion; the change remains in the draft until you save and publish.
Columns for dependencies and publication
In Columns, choose Used by (Sessions), Location, Last published and Description. Used by (Sessions) counts the Sessions using the Mapping; select the number to inspect their names and referenced Mapping versions. Location combines Domain and Folder. Last published shows the most recent publication time and publisher separately from Updated, which can reflect draft changes. Description summarizes the Mapping purpose. When historical evidence is missing, the grid reports that instead of inventing a time or user.
A new grid configuration displays Mapping, Version, Status, Used by (Sessions), Location and Updated. Existing column choices are retained; enable additional columns in Columns. The Status filter offers Draft and Published, matching the editing and publication lifecycle.
Full screen without losing your work
Full Screen expands the Mappings or Workflows canvas in the same editor. Entering and leaving updates the layout immediately and preserves selection, zoom and position. Use the same button or Escape to return. DovaAI remains available in this view; expanding the canvas does not save or publish the draft.
Grid actions
When an Actions option starts, a progress indicator appears on its control and blocks other actions in that grid while the request is pending. Wait for the result before repeating it. A started request does not establish that saving, publication or another operation has finished.
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.
Compact list and icon buttons
The list brings Search, Status and actions into one compact toolbar. Refresh, Columns, Export CSV, Delete selected, New Mapping and Clear filters use icons; hover over a button or focus it with Tab to identify its action. Actions still respect selection, permissions and disabled states.
The Mappings list has no Environment or Runtime filter. Its environment comes from the active context in the bottom operational status bar; the worker and capacity are configured in the Session. Use Search, Status and column filters to inspect objects in that context.
Design, save and publish in the editor
Advanced, Validate, Save draft and Publish appear as icon buttons with accessible names. Button help identifies the action and, where applicable, the save or publication environment. The header does not repeat a DEV badge: confirm Tenant, Domain and Environment in the bottom operational status bar.
Mappings has no Run button. A Mapping defines the transformation; to execute it, save and publish the reviewed version, select it in a Session and configure its inputs, targets and compatible worker. Run the Session directly or through an authorized Workflow. Publishing a Mapping neither starts an execution nor assigns capacity.
Component Configuration
Select a component to inspect its sections and fields in Configuration. Labels, controls and help fit the available width. For sources with Header mapping, the sample-load, add-field and delete buttons retain their own space beside the title. Review Source, Output and Type in the table; scroll it horizontally when the columns do not fit the panel. A header sample configures the schema and does not replace the file the Session reads on its worker.