omnistudio-dependencies-analyze

OmniStudio dependency mapping identifies whether your org uses Core, vlocity_cmt, or vlocity_ins namespaces. It then parses metadata to resolve cross-component references for FlexCards, Integration Procedures, Data Mappers, and OmniScripts, producing a clear structural relationship graph.

Performing OmniScript impact analysis involves tracing downstream integrations and referenced Data Mappers to visualize what components are affected. This targets specific OmniStudio assets to reveal potential circular links and downstream dependencies before changes are applied.

Yes, you can generate Mermaid diagrams for FlexCard dependencies. The mapping process parses OmniStudio metadata, resolves cross-component references, and outputs Mermaid visualizations alongside JSON summaries and human-readable reports for documentation.

Dependency mapping works with both Core and Vlocity environments by applying namespace detection first. It identifies whether your Salesforce org uses Core, vlocity_cmt, or vlocity_ins before resolving references and generating cross-component graphs.

Circular references are detected by parsing OmniStudio metadata and resolving cross-component links across OmniScripts, FlexCards, and Integration Procedures. The system traces these dependency paths to identify and report any circular links found within the graph.