Integration Procedure Best Practices (Managed Package)

For the managed package runtime, to maximize the benefits of Integration Procedures, follow the best practices whenever possible.

This information is for Omnistudio for Managed Packages. For Omnistudio on standard runtime, see Omnistudio Help.

• Use Integration Procedures for all data calls to Salesforce.

• To avoid SOQL limit errors, don't put too many data calls in the same Integration Procedure.

• To maximize reuse and performance, use a modular approach to implement a small group of related functions in each Integration Procedure.

• Use a Response Action for Integration Procedures (Managed Package) to trim the data and only return what is needed. For specific trimming strategies, see Manipulate JSON with the Send/Response Transformations Properties (Managed Package).

• To allow an Integration Procedure to exit early under appropriate conditions, use multiple Response Actions with different Execution Conditional Formulas.

• Use caching to store frequently accessed, infrequently updated data. See Cache for Omnistudio Data Mappers (Managed Package).

• To run data operations asynchronously, call Integration Procedures using these settings:

  • Use Future — Use when the calling Omniscript or Integration Procedure doesn't need a response and completion time isn’t critical.

  • Invoke Mode: Fire and Forget — Use Invoke Mode instead of Use Future when the calling Omniscript must invoke the Integration Procedure immediately.

  • Invoke Mode: Non-Blocking — Use to run the Integration Procedure immediately while continuing the user interaction of the calling Omniscript. A response is returned when the Integration Procedure is complete.

  

  Note When an Omniscript invokes an Integration Procedure asynchronously, the Integration Procedure continues running if the user goes to the next step, but not if the user navigates away from the Omniscript.

  For more information about these settings, see Common Action Element Properties (Managed Package), Integration Procedure Action (Managed Package), and Integration Procedure Action for Integration Procedures (Managed Package).

To determine whether an Omnistudio Data Mapper or an Integration Procedure is best for your use case, see Omnistudio Data Mapper or Integration Procedure? (Managed Package).