An Integration Procedure Action is the most appropriate element as it is designed to execute multiple server-side operations in a single transaction from an OmniScript. The developer can configure the Integration Procedure to first use a DataRaptor Post Action to save data to Salesforce and then use an HTTP Action to send data to the external AWS Order Management system. This allows the OmniScript to trigger both distinct data-saving operations through a single, efficient, server-side call, which is ideal for complex transactions involving multiple systems.

1. Salesforce Help

OmniStudio Integration Procedures: "Integration Procedures can read data from and write data to Salesforce and external systems... For example

an Integration Procedure can get data from an external system using an HTTP action

transform it using a DataRaptor Transform action

and save it to Salesforce using a DataRaptor Load action." This demonstrates the capability of an IP to orchestrate actions involving both Salesforce (via DataRaptors) and external systems (via HTTP Actions).

2. Salesforce Help

OmniScript Actions: "Integration Procedure Action: Runs a server-side Integration Procedure without navigating from the current OmniScript step." This confirms it is the OmniScript element used to invoke the multi-step server process.

3. Salesforce Help

DataRaptor Post Action: "A DataRaptor Post Action saves data that the user enters in an OmniScript to Salesforce." This source explicitly limits its function to saving data to Salesforce.