Swantide reads your org's OmniStudio configuration so you can work with it through the AI Assistant and the Data Dictionary. This article covers what Swantide retrieves, what you can do with it, and a few tips for getting the best results.
What Swantide retrieves
OmniStudio on standard objects
Component | What Swantide reads |
OmniScripts | Every step and element, conditional views, validations and messages, and the actions each step calls |
Integration Procedures | Every step in order, with the DataMappers, Integration Procedures, Apex classes and sObject operations it calls |
DataMappers (Extract, Turbo Extract, Load, Transform) | Source and target objects, field mappings, filters and formulas |
FlexCards | The data source behind the card, its fields, child cards and actions |
Expression Sets | Every step, formula and variable, and the Decision Matrices each step reads |
Decision Matrices | The matrix structure: input and output columns, ranges and versions |
Omni Interaction Configs | Configuration settings |
Designer status | Whether each component is managed in the standard OmniStudio designer |
Vlocity managed packages (vlocity_ins, vlocity_cmt, vlocity_ps)
Component | What Swantide reads |
Package data model | Every package object and field |
Your configuration around the package | Custom objects, fields, Flows, Apex, LWCs and anything else that references package components |
Components migrated to standard objects | Full detail, as in the table above |
DataRaptors, OmniScripts, cards and matrices authored in the Vlocity designers | These are stored as records in the package's objects, so they are reviewed in the Vlocity designer (see Limitations) |
What you can do
Explain an OmniScript step by step, including the conditions that stop or branch the flow, the messages users see, and every component it calls, down through the Integration Procedures it runs.
"Explain the OmniScript <name> step by step, including its conditional logic and every Integration Procedure, DataMapper and Apex class it calls."
Trace a FlexCard to its data, through its data source down to the Salesforce objects, filters and fields it reads.
"Trace the FlexCard <name> down to the Salesforce objects and fields it reads, naming each DataMapper or Integration Procedure in the chain."
Document an Integration Procedure as a technical design section: inputs, each step in order, what each step calls, error handling and outputs.
"Write a technical design section for the Integration Procedure <name>: its inputs, each step in order, every component it calls, and its outputs."
Explain pricing and rating logic in an Expression Set: each step, the exact formulas, the Decision Matrices it looks up and how the final value is built.
"Explain the Expression Set <name>: its inputs, each step in order, which Decision Matrices it uses, and how the final result is calculated."
Write test cases from an OmniScript, covering the happy path and each validation and error path, using the real conditions and messages in the script.
"Write UAT test cases for the OmniScript <name>, covering the happy path and each validation or error path in its logic."
Size a designer migration by type, from which components are still managed outside the standard OmniStudio designer.
"Which OmniScripts, Integration Procedures, DataMappers and FlexCards in this org are still managed outside the standard designer, with counts per type?"
Design something new from what exists. The Assistant names each existing DataMapper and Integration Procedure it reuses and marks which pieces would be new.
"Design a new OmniScript that <does X>. Reuse existing DataMappers and Integration Procedures wherever possible, name each one you reuse, and mark which pieces would be new."
Limitations
Content authored in the Vlocity designers. DataRaptors, OmniScripts, cards and calculation matrices built in the Vlocity managed-package designers are records, so review them in the Vlocity designer for now. As components move to the standard OmniStudio objects, they come into full view in Swantide with the next sync, which makes Swantide a good companion to a Vlocity to OmniStudio migration.
Decision Matrix row values. Swantide reads each matrix's structure. The row values themselves are data in your org, so view them in the matrix editor.
Usage tips
Name the object in mixed orgs. Where a Vlocity package object and a standard object have similar names, name the one you mean when you ask for a design.
Search the Data Dictionary by label. The search matches component labels, so
Billing Detailsfinds more thanBillingDetails.