A public sector agency has implemented Public Sector for Licenses & Permits.

An OmniStudio Integration Procedure is the appropriate orchestration layer because the transaction requires information from multiple sources and several server-side processing steps. Salesforce describes Integration Procedures as declarative server-side processes that can retrieve, transform, and send information between Salesforce and external systems, perform REST API calls, apply conditional processing, and execute several actions within a single server request.

In this scenario, the Integration Procedure can retrieve the base permit fee from the external system, retrieve the site or address information and applicable discount from the Salesforce custom object, apply the required processing logic, and return the resulting fee to the calling application experience. Salesforce explicitly recommends Integration Procedures when data must be accessed from multiple data-source types or when processing cannot be handled by a simple single-object extraction. A Data Mapper is optimized for comparatively focused Salesforce data operations and transformations. An OmniScript controls the guided user interaction, while a FlexCard primarily presents information and actions. Neither replaces the server-side orchestration required to combine external fee information with Salesforce data.

Study Guide References: OmniStudio Integration Procedures; External Data Integration; Data Mappers; OmniScripts; Licensing and Permitting Fee Processing.