Omnistudio Integration Procedures for server-side calls to external systems

Key Takeaway

When no user interaction is needed, use an Integration Procedure to fetch, transform and send data in a single server call.

Omnistudio Integration Procedures are declarative, server-side processes that move data between Salesforce and external third-party systems with no user interaction. They can call REST APIs, run Apex, read and write Salesforce data, and transform the results, all in a single server call. A consultant recommends them when a solution needs to fetch, combine or send data behind the scenes, not guide a user through screens.

When to use an Integration Procedure

Use an Integration Procedure when no user interaction is required during execution. Typical goals are to retrieve, transform and send data between Salesforce and external systems.

An Omniscript guides a user through a process, but an Integration Procedure works on the server and hands back data. So start by asking whether a user needs to take part while the process runs.

Salesforce Accredited Agentforce Health Professional Study Guide

Checklist progressProgress

0/167Learned

Checklist progressProgress

0/167Learned

Given customer requirements, determine how to create the solution for Agentforce Health features according to best practices

0/2

Given customer requirements, understand how to model patients, providers, healthcare facilities, etc., using the appropriate Agentforce Health objects

0/14

Given customer requirements, determine how to create the proper application solution design leveraging Agentforce Health best practices

0/5

Given customer requirements, determine when to use specific Agentforce Health capabilities

0/8

Given customer requirements, determine how to create the design solution for a specific Agentforce Health vertical to meet those requirements

0/6

Given the business processes/requirements, determine how to create the solution design utilizing best practices and Agentforce Health modules

0/5

Given a customer's business objectives and goals, define success-metrics/KPIs and configure Salesforce to enable reporting on these metrics

0/5

Given a customer's security/compliance requirements, design and implement the appropriate organizational security and data access considerations

0/8

Given a customer's external systems and data requirements, determine the optimal integration strategy for the customer's Salesforce org

0/7

Integration pattern selection for health data exchange

Learn this concept

Middleware versus point-to-point integration in a multi-system health landscape

Learn this concept

EHR clinical data integration into the FHIR-aligned clinical data model

Learn this concept

Omnistudio Integration Procedures for server-side calls to external systems

Learn this concept

Salesforce Connect data virtualization versus copying external health data into the org

Learn this concept

Data 360 for unifying patient data across external systems

Learn this concept

Securing integrations that exchange protected health information

Learn this concept

Given a customer's business requirements, design the future state business processes

0/4

Given the data requirements, create a migration strategy considering the legacy /future state system landscape ensuring accuracy and integrity

0/9

Prepare for the Exam

Play Today's Certle

Study Community

Ask questions and get the latest info from other Salesforce Accredited Agentforce Health Professional studiers.

Go to Discord

Omnistudio Integration Procedures for server-side calls to external systems

Key Takeaway

When no user interaction is needed, use an Integration Procedure to fetch, transform and send data in a single server call.

When to use an Integration Procedure

Use an Integration Procedure when no user interaction is required during execution. Typical goals are to retrieve, transform and send data between Salesforce and external systems.

An Omniscript guides a user through a process, but an Integration Procedure works on the server and hands back data. So start by asking whether a user needs to take part while the process runs.