Fusion is currently in development and scheduled for release in June 2026. The information in this article reflects the planned design. Features and interface details may change before launch.

The Transformation Editor is the primary workspace inside Fusion. It provides a visual, card-based interface for creating and managing the field-level rules that govern how data moves between an external system (such as XactAnalysis) and FileTrac.

Each card in the editor represents a single transformation — a rule that maps a source field to a destination field and defines how the value should change (if at all) during transfer. Cards are organized into a scrollable list, and selecting any card opens a side panel with full editing controls.

The Transformation Editor is built around three areas:

The center of the screen displays all transformations in the current mapping as a vertical card list. Each card shows three sections:

Cards can be filtered and sorted to help administrators locate specific field mappings quickly in large configurations.

Selecting a card opens the side panel on the right, which provides the full editing interface for that transformation. The side panel includes fields for source and destination selection, transformation type, lookup assignment, and validation status.

Multiple side panel configurations exist for different editing contexts — for example, the panel for a simple one-to-one copy looks different from the panel for a nested, multi-step transformation chain.

When a mapping has no transformations yet, the editor displays a guided empty state that walks administrators through creating their first rule. This ensures new users are not dropped into a blank screen without direction.

Fusion supports two broad categories of transformation:

A non-nested transformation is a single-step rule. The source value is read, optionally converted or looked up, and written directly to the destination field. Most field mappings fall into this category — for example, mapping a claim number from XactAnalysis to the corresponding claim number field in FileTrac.

A nested transformation chains multiple steps together. The output of one step becomes the input to the next, allowing complex, multi-level data processing. For example:

Nested transformations are displayed in the editor with a visual chain indicator so administrators can see at a glance how many steps a rule contains.

To add a new transformation, use the "Add" control at the top of the card list. The side panel opens with an empty form where you select the source field, destination field, and transformation type. If you choose a lookup-based transformation, you can assign an existing lookup table or create a new one inline.

Select any card in the list to open it in the side panel. Changes are saved when you confirm in the panel. The card in the main list updates immediately to reflect the new configuration.

When you pair a source and destination field, Fusion automatically compares their data types. If there is a mismatch — for example, a numeric source mapping to a text destination — the editor displays a warning with the compare-type detail so you can add an appropriate conversion step.

The Transformation Editor includes carefully designed interaction patterns (documented in the Fusion design system as version 1.3) that provide visual feedback during drag, select, expand, and reorder operations. These micro-interactions help administrators stay oriented when working with large mapping configurations that may contain dozens or hundreds of field rules.