Connect the Service Process ID to the Intake Form
Make sure that the intake form submits data to the correct service process record and triggers the exact fulfillment flows assigned to that service.
Required Editions
| Available in: Lightning Experience |
| Available in: Enterprise, Unlimited, and Developer Editions with Financial Services Cloud and Unified Catalog. |
| User Permissions Needed | |
|---|---|
| To install a template: | Industry Service Excellence admin user |
After installing the service process template, you have a service process record and the required components. Link the specific service process record ID, which is the product ID for the service, to your Omniscript and flow orchestrator. This ID acts as the unique identifier that tells which service is requested. Linking this ID makes sure that the intake form submits data to the correct service process record, and triggers the specific fulfillment flow assigned to that service process.
Before you begin, make sure that you have the product ID generated for the service process record during the template installation.
Use one of these two methods to pass the product ID of the service process to the intake Omniscript.
-
Embed the product ID in the integration procedure that’s specific to a service
process.
Use this method if you’re setting up a single service process and want to hardcode the ID directly into the integration procedure of the service process.
- From the App Launcher, find and select Omniscripts.
- Open the new version of the Omniscript for the service process.
- Locate the integration procedure action element named CreateCase.
- Click the element to view its properties.
- Locate the integration procedure it calls.
- Open the integration procedure that you located.
- Click the dropdown menu next to Save, and then click Create Version.
- In the new version, click the InvokeCreateCaseConnectAPI element.
- Expand the Additional Input, Additional Output, and Failure Response section.
- In the Additional Input tab, add a new key-value pair.
- Enter productId as the key.
- Enter the alpha-numeric product ID of the service as the value.
- Save your changes.
- Activate the integration procedure.
- Return to your Omniscript.
- Confirm that the Omniscript references the active version of the integration procedure.
- Activate the Omniscript.
-
Map the product ID in the centralized mapping integration procedure.
Use this method if you want to manage the product IDs to service process mappings for all your service processes in one central place without cloning and updating the integration procedures of individual service processes.
- Open the integration procedure called by your Omniscript's CreateCase integration procedure action element.
- Select the InvokeCreateCaseConnectAPI component.
- Expand the Additional Input, Additional Output, and Failure Response section.
- In the Additional Input tab, locate the svcCatalogItemDefApiName key.
- Copy the value associated with this key.
- From the App Launcher, find and select Integration Procedures.
- Open the ServiceProcess_MapServiceNameToProductId integration procedure.
- Click the dropdown menu next to Save, and then click Create Version.
- Select the ServiceNameToProductIdMap component.
- In the Element Value Map section, locate the key that matches your svcCatalogItemDefApiName.
- Update the value for that key with your specific product ID.
- Save your changes.
- Activate the integration procedure.
The Intake Omniscript is now linked to the service process.

