Which OmniScript element could save all of this data to Salesforce and to an AWS Order Management system?

Which OmniScript element could save all of this data to Salesforce and to an AWS Order Management system?

• A. DataRaptor Post Action
• B. HTTP Action
• C. Integration Procedure Action
• D. DataRaptor Load Action

Answer: (C)

In OmniStudio, orchestrating where and how data gets saved requires a server-side coordinator. An Integration Procedure Action serves exactly that role: it allows one OmniScript to drive multiple back-end operations in sequence or in parallel, all inside a single procedure. With this, you can save the collected data to Salesforce using a DataRaptor Load Action and at the same time push the same data to an AWS Order Management system via an HTTP Action, all within the same Integration Procedure. This centralized orchestration ensures you handle data consistently, manage errors, and map fields as needed for both destinations. The other options don’t provide that multi-target orchestration by themselves. A DataRaptor Load Action writes data into Salesforce but doesn’t send it to AWS. An HTTP Action can call an external API, but it isn’t by itself responsible for saving to Salesforce. A DataRaptor Post Action is used for posting data within a DataRaptor workflow and isn’t focused on coordinating saves to multiple systems.

In OmniStudio, orchestrating where and how data gets saved requires a server-side coordinator. An Integration Procedure Action serves exactly that role: it allows one OmniScript to drive multiple back-end operations in sequence or in parallel, all inside a single procedure. With this, you can save the collected data to Salesforce using a DataRaptor Load Action and at the same time push the same data to an AWS Order Management system via an HTTP Action, all within the same Integration Procedure. This centralized orchestration ensures you handle data consistently, manage errors, and map fields as needed for both destinations.

The other options don’t provide that multi-target orchestration by themselves. A DataRaptor Load Action writes data into Salesforce but doesn’t send it to AWS. An HTTP Action can call an external API, but it isn’t by itself responsible for saving to Salesforce. A DataRaptor Post Action is used for posting data within a DataRaptor workflow and isn’t focused on coordinating saves to multiple systems.