OmniStudio is Salesforce's declarative framework for vertical / industry-specific applications. Originally Vlocity; now part of Industries Cloud.
Components:
- FlexCards — declarative UI cards, more flexible than Lightning Record Pages.
- OmniScripts — guided workflows (think Wizard) with branching logic.
- Integration Procedures (IP) — declarative server-side integrations and data orchestration.
- DataRaptors — declarative data transformations between Salesforce and external.
When OmniStudio beats standard:
- Industry Cloud licensing — included.
- Complex multi-step workflows with branching, validation, callouts. OmniScripts handle these declaratively.
- Highly customised UI — FlexCards more flexible than Lightning Record Pages.
- Server-side orchestration — Integration Procedures handle complex flows without writing Apex.
- Declarative team — admins can build what would otherwise need devs.
When standard Salesforce beats OmniStudio:
- No Industry Cloud — OmniStudio licensed separately at significant cost.
- Simple workflows — standard Flow handles fine.
- Team familiar with Apex / LWC — standard stack often better than OmniStudio's curve.
- Performance-critical — OmniScripts have more overhead than custom LWCs.
- Long-term maintainability — OmniStudio is its own ecosystem; specialised talent.
Architectural decisions:
- All-in on OmniStudio — useful in Industry Cloud-heavy implementations. Single framework.
- OmniStudio for some, standard for others — workable but adds complexity.
- No OmniStudio — for non-Industry-Cloud orgs or where standard suffices.
Common patterns:
- OmniScripts for guided processes — onboarding, application processing, complex case workflows.
- FlexCards for record-360 displays — composite views from multiple data sources.
- Integration Procedures for complex data flows — chain SOQL, callouts, transformations declaratively.
- DataRaptors for ETL — between Salesforce objects and external systems.
Trade-offs:
- Pros: declarative, faster build for complex workflows, vertical alignment.
- Cons: licensing cost, vendor-specific patterns, smaller talent pool.
Architect role: decide the OmniStudio strategy — all-in, partial, none. Communicate to team. Stick with the choice; don't drift.
The senior insight: OmniStudio is a tool, not a religion. Use where it fits; resist where it doesn't.
Common pitfall: implementing OmniStudio for everything because Industry Cloud "comes with it" — produces orgs that no one outside the project can maintain.