Home / omnistudio
Omnistudio skills (34)
OmniStudio: OmniScripts, FlexCards, DataRaptors, Integration Procedures, Business Rules Engine, DataPacks.
- business-rules-engineUse when designing, building, or troubleshooting OmniStudio Business Rules Engine (BRE) artifacts: Decision Tables, Decision Matrices (rule matrices), and Expression Sets used for eligibility determination, pricing, discounting, or any complex multi-attribute...
- calculation-procedure-designDesign Calculation Procedures and Matrices for pricing, rating, and rules-heavy scoring.
- calculation-proceduresBuild and troubleshoot Calculation Procedures (Expression Sets) and Calculation Matrices.
- dataraptor-load-and-extractBuild or debug DataRaptor Extract and Load — multi-object extracts, upserts, iferror mapping. Triggers: DataRaptor Extract, DataRaptor Load, Turbo Extract debug. NOT for Extract vs Load design tradeoffs — use omnistudio/dataraptor-patterns.
- dataraptor-patternsDesign DataRaptors — Extract vs Turbo Extract vs Transform vs Load, mapping, performance.
- dataraptor-transform-optimizationUse when DataRaptor Transform operations are slow, hit governor limits, or use Apex where formula fields would suffice.
- document-generation-omnistudioGenerating documents (PDF, DOCX, PPTX) from OmniStudio using Document Templates, OmniDataTransform token mapping, and OmniScript or Integration Procedure orchestration.
- flexcard-container-compositionDesign FlexCard composition: parent/child state flow, layout modes, actions, event wiring, and data source selection.
- flexcard-design-patternsDesign FlexCard layout, data sources, states, actions, and child-card iteration.
- flexcard-state-managementFlexCard actions, conditional visibility, and state across navigation, refresh, and parent/child transitions.
- industries-api-extensionsEndpoint path, payload and error handling for a named Salesforce Industries API — Insurance Policy Business Connect, Communications Cloud TM Forum Open APIs (TMF679, TMF680), Energy and Utilities Update Asset Status, Service Process Studio Connect.
- industries-cpq-vs-salesforce-cpqUse this skill when comparing Industries CPQ (formerly Vlocity CPQ) with Salesforce CPQ (Revenue Cloud managed package) — covering feature parity, decision criteria, migration paths, and coexistence patterns.
- integration-procedure-cacheable-patternsUse when designing Integration Procedures (IPs) with platform cache to cut latency and callout load.
- integration-proceduresUse when building, reviewing, or debugging OmniStudio Integration Procedures.
- omniscript-design-patternsUse when designing or reviewing OmniScripts for guided experiences, step structure, branching, save/resume, and the boundary between OmniScript, Integration Procedures, DataRaptors, and custom LWCs.
- omniscript-session-stateUse when an OmniScript must persist mid-flow state across refresh, navigation, multi-device resume, or abandonment recovery.
- omniscript-versioningUse when managing OmniScript versions: activating new versions, deactivating prior versions, testing a specific version before activation, rolling back to a previous version, or understanding version identity (Type/Subtype/Language triplet).
- omnistudio-asynchronous-data-operationsUse Integration Procedures queues, DataRaptor Chain, and Remote Actions with async patterns for long-running OmniStudio flows. NOT for simple DataRaptor reads — use omnistudio/dataraptor-patterns.
- omnistudio-cache-strategiesConfigure caching on DataRaptors and Integration Procedures for response-time gains. Triggers: OmniStudio cache, DataRaptor cache, IP cache TTL. NOT for IP-specific cacheable design — use omnistudio/integration-procedure-cacheable-patterns.
- omnistudio-ci-cd-patternsCI/CD pipelines for OmniStudio — DataPack export/import, versioning, env promotion. Triggers: OmniStudio CI/CD, DataPack pipeline, OmniStudio deployment. NOT for manual DataPack operations — use omnistudio/omnistudio-deployment-datapacks.
- omnistudio-custom-lwc-elementsCreating and integrating custom Lightning Web Components within OmniScripts: LWC override patterns, pubsub event handling, custom validation, OmniStudio data passing conventions.
- omnistudio-debuggingUse when diagnosing failures, unexpected output, or silent errors in OmniScript, DataRaptor (Data Mapper), or Integration Procedure assets.
- omnistudio-deployment-datapacksUse when exporting, importing, or version-controlling OmniStudio components using DataPacks via the OmniStudio DataPacks tool or vlocity CLI.
- omnistudio-error-handling-patternsUse when designing fault behavior across Integration Procedures, DataRaptors, OmniScripts, and FlexCards — error routing, user-facing messaging, retry semantics, and idempotency.
- omnistudio-field-mapping-governanceGovern DataRaptor field mappings to prevent runtime errors when source metadata changes: naming, versioning, and dependency tracking. NOT for DataRaptor authoring fundamentals — use data/omnistudio-metadata-management.
- omnistudio-lwc-integrationUse when embedding OmniScripts in Lightning Web Components, registering custom LWC elements inside OmniScript screens, or calling OmniScript/Integration Procedures from LWC.
- omnistudio-lwc-omniscript-migrationMigrate classic Visualforce-based OmniScripts to LWC-based runtime with feature parity and regression testing. NOT for new OmniScript design — use omnistudio/omnistudio-lwc-integration.
- omnistudio-multi-languageLocalize OmniScripts, FlexCards, and DataRaptors using Label-based translation, multi-language JSON, and locale-aware number/date formatting. NOT for Salesforce Translation Workbench alone — use admin/multi-language-and-translation.
- omnistudio-performanceUse when diagnosing or improving runtime performance in OmniStudio assets: slow OmniScripts, Integration Procedures with high latency, DataRaptor caching, excessive API call counts, FlexCard rendering.
- omnistudio-remote-actionsUse when configuring, troubleshooting, or choosing between Remote Action types in OmniScript or FlexCard.
- omnistudio-securityUse when designing or reviewing OmniStudio security across OmniScripts, Integration Procedures, DataRaptors, custom LWCs, Apex actions, guest-user exposure, and outbound HTTP actions.
- omnistudio-testing-patternsTest OmniStudio components — OmniScript preview, IP step debugging, DataRaptor validation, UTAM.
- omnistudio-vs-flow-decisionUse when choosing between OmniStudio (OmniScript / Integration Procedure / FlexCard / DataRaptor) and Flow / Screen Flow / Apex for a given capability.
- vlocity-to-native-omnistudio-migrationUse when migrating an org from the Vlocity managed package (vlocity_ins, vlocity_cmt, vlocity_ps) to native OmniStudio.