Financial Service Processes in Unified Catalog
Use the Unified Catalog to set up and manage financial service processes. The Unified Catalog standardizes these processes by defining them as products in your Salesforce instance. Manage both financial products and services in one place.
Required Editions
| Available in: Lightning Experience |
| Available in: Enterprise, Unlimited, and Developer Editions with Financial Services Cloud and Unified Catalog. |
The Unified Catalog streamlines the service lifecycle to improve request management efficiency and data capture accuracy. Guided, prebuilt Omniscripts make sure that both service representatives and end users submit complete request details upfront. This guidance minimizes errors. Prebuilt flow orchestrators automate record updates and task assignments. Also, standard integration definitions simplify connections to external systems without requiring custom code.
Why Unified Catalog Over Service Process Studio for Setting Up Financial Service Processes?
Compare Service Process Studio with the Unified Catalog to understand the key differences and benefits.
| Capability | Service Process Studio | Unified Catalog | Benefit of Unified Catalog |
|---|---|---|---|
| Service Process Templates | Not available. Service Process Studio doesn’t contain prebuilt financial service process templates. | Available. Hosts all prebuilt financial service process templates. | Deploy service processes immediately by using prebuilt templates instead of designing intake forms and flows from scratch. |
| Customization | Pro-code. Uses Apex class to create case requests. Customizations, such as the addition of a new data attribute, requires writing a new Apex class. | Low-code. Uses a Data Mapper to visually manage data attributes without custom code. | Add or modify data attributes by using a visual drag-and-drop tool, such as the Data Mapper instead of rewriting complex Apex code. |
| Setup Data Model | Uses custom setup objects, such as SvcCatalogItemDef and svcCatalogItemAttributes. | Uses standard objects, such as Product2, ProductCatalog, and ProductCategory. | Store your service processes as standard products, making them compatible with other Salesforce apps. |
| Runtime Data | Stores requests in SvcCatalogRequest and Case. | Stores requests in SvcCatalogRequest and Case, similar to Service Process Studio. | Keep all historical reporting and audit trails intact without data migration, as both these frameworks use the same underlying storage objects. |
| API Integration | Uses the service process Connect API specific to financial services. | Uses the Unified Catalog Connect API. | Use a single, universal API endpoint to submit requests for any service type across sectors, such as banking, wealth management, or insurance, by simply specifying the product ID. |
| Flow Triggers | Triggers flow based on a text string, such as the Developer Name from a service process definition. | Triggers flow based on a unique product ID. | Trigger automations by using unique, unchangeable record IDs so that renaming a service process definition never breaks the underlying fulfillment process. |
| Auto-Generation of Intake Forms | Not Available | Automatically generate screen flows or Omniscripts based on service attributes, data types, and attribute groupings. These forms integrate directly with the Unified Catalog API to create case records upon service request submission. |
Reduces the manual setup time by instantly creating ready-to-use forms. |
