Design Simple Integration Procedures

Learning Objectives

After completing this unit, you’ll be able to:

• Describe data input and data output for Integration Procedures in Omnistudio for Managed Packages.
  
• Explain how to design an Integration Procedure to get data.
  
• Describe how to design an Integration Procedure to save data.
  
• Explain how to design an Integration Procedure to get data from an application programming interface (API).
  

Data Input and Data Output

In this unit, you learn about using Integration Procedures for three different design scenarios. Before we dig into the design scenarios, let’s quickly review data input and data output for Integration Procedures in Omnistudio for Managed Packages. 

Data Input

Remember, the data source determines which element you use.

Data Output

The Response Action element is unique to the Integration Procedure. It passes data back to the tool that launched the procedure. In addition to getting and processing data, you can use an Integration Procedure to output data.

Got it? Great. On to the scenarios! 

Scenario 1: Design an Integration Procedure to Get Data

Imagine that you’d like to see sample data replaced with live data in an Omniscript that edits account details.

You’d like ‌Omniscript to be able to extract the data from Salesforce and save the changed data back into Salesforce. So, your task is to design this first Integration Procedure for an edit account Omniscript. 

There are two requirements for the Integration Procedure.

• Extract Account data from Salesforce.
  
• Send that data to ‌Omniscript.
  

Where do you begin? Let’s take it step by step, choosing the Integration Procedure elements that address the data requirements. Don’t forget that, in this scenario, you’re focusing on getting data. 

Select an Actions element that gets Account data from Salesforce. Here are your choices.

1. Data Mapper Post Action
   
2. Data Mapper Turbo Action
   
3. Data Mapper Transform Action
   

Which is correct? Well, if you look at the earlier data input table, you see that because you’re getting data from Salesforce, the Data Mapper Turbo Action is the correct choice. This action calls a Data Mapper Turbo Extract to get data from Salesforce.

Select an Actions element to send that data back to the Edit Account Omniscript. Here are your choices.

1. Data Mapper Post Action
   
2. Response Action
   
3. HTTP Action
   

The correct Actions element is the Response Action. Remember that it passes data back to the launching object or whatever called the Integration Procedure. In this scenario, that was an Omniscript.

Scenario 2: Design an Integration Procedure to Save Data

Let’s look at our scenario again but change our focus a bit.

You now want ‌Omniscript to extract the data from Salesforce and save any data that you change back into Salesforce. So, your task is to design an Integration Procedure to save data for the Omniscript. 

Select an Actions element that saves Account data back to Salesforce. Here are your choices.

1. Data Mapper Post Action
   
2. Data Mapper Extract Action
   
3. Integration Procedure Action
   

In this case, the correct choice is Data Mapper Post Action because it saves updated data back to Salesforce.

Scenario 3: Design an Integration Procedure to Get Data from an API

Now imagine that for a Flexcard that displays weather, you want sample data replaced with live weather forecast data that comes from an external source. Your task is to design an Integration Procedure for the Weather Flexcard.

There are a few requirements for the Integration Procedure.

• Get weather data from an application programming interface (API).
  
• Trim and remap weather data (many fields).
  
• Send that data back to the tool that calls the Integration Procedure, which is the weather Flexcard.
  

Let’s choose the Integration Procedure elements that address the data requirements. 

First, select an Actions element that gets current weather forecast data from an API. Here are your choices.

1. Data Mapper Extract Action
   
2. Data Mapper Transform Action
   
3. HTTP Action
   

The correct choice is HTTP Action. This Actions element can be configured to get data from a web API.

Now select an Actions element that trims and remaps weather data. Here are your choices.

1. Data Mapper Post Action
   
2. Data Mapper Transform Action
   
3. HTTP Action
   

What’s the correct choice? If you said Data Mapper Transform Action, you’re right! Remember that a Data Mapper Transform can be configured to trim and remap the data received from the web API.

Finally, select an Actions element that sends data back to the weather Flexcard. Your choices are:

1. Response Action
   
2. Data Mapper Post Action
   
3. HTTP Action
   

The correct choice is Response Action. The Response Action passes data back to the launching object, which, in this scenario, is the weather Flexcard.

Super job on the scenarios! Ready to kick the learning up a notch? Head to the next unit to get even more hands-on with Integration Procedures.

Resources

• Salesforce Help: Integration Procedure Actions (Omnistudio for Managed Packages)