Status: Shipping June 2026
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.
What Is the Fusion Wizard?
The Fusion Wizard is a guided, step-by-step setup flow for creating new transformation configurations. Rather than starting with a blank editor and requiring administrators to know exactly which fields to map, the Wizard walks through the process in a structured sequence — from selecting the source and destination systems to reviewing and activating the finished mapping.
When to Use the Wizard
Use the Wizard when you need to create a brand-new mapping from scratch. Common scenarios include:
Connecting a new external claims system to FileTrac for the first time.
Building a custom mapping for a partner or carrier whose data format does not match any existing default template.
Creating a specialized subset mapping — for example, a configuration that only transfers financial fields for a specific integration use case.
If you are starting from the pre-built XactAnalysis default mapping, you do not need the Wizard. Instead, copy the default mapping and edit the copy directly in the Transformation Editor.
Wizard Steps
Step 1 — Select Source and Destination
Choose the external system (source) and the FileTrac target (destination) for the new mapping. The Wizard presents the available system connectors and validates that the selected pair is a supported combination.
Step 2 — Define Field Pairs
The Wizard displays the available fields from the source system alongside the available fields in the destination system. Administrators select which source fields should map to which destination fields. Fusion highlights data type compatibility as you pair fields, flagging any mismatches that will require a transformation rule.
Step 3 — Configure Transformations
For each field pair, choose the transformation type. Simple one-to-one copies require no additional configuration. For fields that need value translation, the Wizard prompts you to create or assign a lookup table. For complex scenarios, you can define nested transformation chains directly within the Wizard flow.
Step 4 — Set Up Lookups
If any transformations reference lookups that do not yet exist, the Wizard collects the value pairs in a streamlined entry form. You can add, edit, and reorder entries, and configure multi-value or Select-First-From-List priority if needed. Lookups created during the Wizard are saved to the Fusion lookup library and can be reused in other mappings.
Step 5 — Review and Validate
The final step displays a summary of the complete mapping: all field pairs, transformation types, lookup assignments, and any validation warnings. Fusion runs an automated check for unmapped required fields, data type mismatches without conversion rules, and orphaned lookup references.
If validation passes, the mapping is ready to activate. If issues are found, the Wizard highlights them with links back to the relevant step so you can correct them without starting over.
Step 6 — Activate
Once review is complete, activate the mapping to make it available for live data transfer. Activated mappings appear in the Fusion main screen alongside the default templates and any other custom configurations.
Editing After the Wizard
The Wizard is a creation tool — it produces a new mapping configuration. Once the mapping exists, all further editing happens in the Transformation Editor. You can return to the editor at any time to add new field pairs, modify transformation rules, update lookups, or adjust the configuration as requirements change.
Tips for a Smooth Setup
Prepare your field inventory. Before starting the Wizard, have a list of the source system's fields and the corresponding FileTrac fields you intend to map. This speeds up Step 2 significantly.
Start with required fields. Map the fields that are mandatory in FileTrac first, then layer in optional fields. This ensures the mapping is functional from the start and can be expanded incrementally.
Use the default mapping as a reference. Even if you are building a mapping for a different system, the XactAnalysis default mapping demonstrates best practices for transformation structure, lookup organization, and naming conventions.