analyzing-omnistudio-dependencies

Analyze OmniStudio component dependencies and generate impact reports.

803|289|Updated Nov 7, 2025
One-click install
npx skills add https://github.com/forcedotcom/sf-skills --skill analyzing-omnistudio-dependencies
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: analyzing-omnistudio-dependencies
Source: https://github.com/forcedotcom/sf-skills/tree/main/skills/analyzing-omnistudio-dependencies
Command: npx skills add https://github.com/forcedotcom/sf-skills --skill analyzing-omnistudio-dependencies

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It removes the guesswork involved in understanding which OmniStudio components depend on others, which namespace they live in, and what impact a change will have across OmniScripts, Integration Procedures, FlexCards, and Data Mappers.

Core Features & Use Cases

  • Detects OmniStudio namespace (Core vs vlocity_cmt vs vlocity_ins) to ensure queries and field/object names match the org.
  • Builds directed dependency graphs by parsing embedded JSON configs such as PropertySetConfig, DataSourceConfig, and Data Mapper items.
  • Produces impact analysis with circular reference detection and outputs Mermaid diagrams plus JSON and human-readable reports.

Quick Start

Ask the skill to analyze OmniStudio dependencies for your target org alias and return a Mermaid diagram and a JSON summary of the components and their impact relationships.

Frequently Asked Questions about analyzing-omnistudio-dependencies

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I map OmniStudio dependencies to see which FlexCards or Integration Procedures are affected by a change?

OmniStudio dependency mapping parses embedded JSON configs like PropertySetConfig to build a directed graph, identifying which FlexCards, Integration Procedures, and Data Mappers affect each other for impact analysis.

How does OmniStudio namespace detection work for Impact Analysis across different vlocity packages?

OmniStudio namespace detection identifies whether components use Core, vlocity_cmt, or vlocity_ins namespaces, ensuring SOQL queries and field names match the specific org configuration before performing org-wide inventory and impact analysis.

Can I visualize OmniScript dependency relationships using Mermaid diagrams?

Yes, the dependency analysis generates Mermaid diagrams to visualize OmniScript relationships, applying circular reference detection to the directed graph and outputting both human-readable reports and JSON summaries.

What's the best way to perform org-wide OmniStudio inventory and identify circular references?

Building a directed dependency graph by parsing Data Mapper items and DataSourceConfig fields enables org-wide OmniStudio inventory, detecting circular references and emitting component namespaces, dependency edges, and impact results in JSON format.

How do I parse OmniStudio configuration JSON fields to build a dependency graph for Data Mappers?

Parsing OmniStudio configuration JSON fields like PropertySetConfig and DataSourceConfig builds a directed graph with circular reference detection, mapping Data Mapper dependencies and emitting results in both human-readable and JSON forms.

Does OmniStudio dependency analysis require SOQL queries to extract Integration Procedure relationships?

OmniStudio dependency analysis applies namespace detection to ensure SOQL queries and field names match the org, then parses embedded JSON configs to build directed graphs mapping Integration Procedure relationships and impact analysis.