OmniStudio Integrity

Detect native vs packaged OmniStudio, map component dependencies, and catch broken references before you deploy.

Connect a Salesforce org

Scans OmniScript, DataRaptor, Integration Procedures, and FlexCards. Shares session with other OrgKit tools.

Nickname
Environment

Map OmniStudio dependencies before you deploy

OmniStudio components reference each other by name, and those references are not validated at deploy time. An OmniScript calls a DataRaptor, an Integration Procedure calls another Integration Procedure, a FlexCard points at a data source — and if one of them didn't come across in the deployment, or came across under a different version, nothing complains until a user hits the screen.

The second problem is provenance. Orgs migrating from managed-package Vlocity to native OmniStudio often end up running both, and telling which component is which from the UI is slow and error-prone.

Status: in testing. The dependency engine and resolver are built and covered by an automated test harness, but this tool has not completed acceptance testing on real orgs yet. It is published so the approach can be reviewed, not because it is finished. The other three OrgKit tools are live.

What it is designed to do

Common questions

Does it work on Vlocity orgs?

That is the primary case. It is designed for orgs running managed-package Vlocity, native OmniStudio, or both at once during a migration.

Does it modify components?

No. It reads component metadata and maps the references between them. It is read-only by design.

Why is it marked as in testing rather than live?

Because the honest label is the one that matches the evidence. The logic is certified by an automated harness; it has not been signed off against a range of real production orgs. Calling that "live" would be the kind of claim this project tries not to make.

Is my component metadata uploaded anywhere?

No. Same architecture as the rest of OrgKit — nothing stored server-side, calls go directly from your browser to your org. See the trust page.

What should I use in the meantime?

For data-model documentation on an Industries org, Schema Atlas is live and handles managed-package namespaces including vlocity_ins.