Setup and Configuration of the Notify Travel Plans Service Process for Retail Banking
Use Service Process Studio to enable the Notify Travel Plans service process to give your service reps an easy-to-follow process for capturing upcoming travel plans of your customers.
Required Editions
| Available in: Lightning Experience |
| Available in: Professional, Enterprise, and Unlimited Editions where Financial Services Cloud is enabled |
Here are the artifacts and components used for this process.
| TYPE | NAME | WHAT IT DOES |
|---|---|---|
| API Endpoint | /customers/{customerId}/travel-notifications | Triggers the fulfillment flow to process the request in MuleSoft (or other middleware). |
| Integration Definition | FSC_NotifyTravelPlans | Calls the API to submit a client’s request in the card management system. |
| Apex | fscserviceprocess.NotifyTravelPlansIntegrationProvider | Implements the business logic required for the service process integration. |
| Omniscript | FSC/NotifyTravelPlans | Gives a guided path for completing the request intake process. |
| Flow Orchestrator Work Guide | Process Notify Travel Plans | Orchestrates the request processing flow, triggered by a record update, and takes action based on the outcome. |
| Service Process Template | Notify Travel Plans | Creates a unique version of the service process from a predefined template. |
| Action Launcher Deployment | /FSC/NotifyTravelPlans/Multi-Language | Adds an Omniscript to the action launcher component. |
- Assign Permissions for the Notify Travel Plans Service Process for Retail Banking
To use the Notify Travel Plans service process, assign the relevant permissions to your users. - Connect to MuleSoft and Create a Named Credential for the Notify Travel Plans Service Process
Turn on Financial Services Cloud Integrations and connect your external banking system to Salesforce - Create an Integration Definition for the Notify Travel Plans Service Process
The Notify Travel Plans Service Process uses the FSC_NotifyTravelPlans integration definition. It calls the API to submit the client’s travel request in the card management system. You can use this integration definition, or create your own. - Clone the Omniscript for the Notify Travel Plans Service Process
Give your users a guided path for completing the request intake process in the Notify Travel Plans service process. Use the Omniscript as it is, or customize it to meet your business needs. - Clone the Notify Travel Plans Salesforce Flow
Show your users the step-by-step instructions to submit a Notify Travel Plans request for a client. You can customize the flow to meet your business needs. - Incorporate Your Company Logo in Notify Travel Plans Service Process Communications for Retail Banking
Use your company logo in an email template and use the template with the Notify Travel Plans service process for customer interactions. - Create a Notify Travel Plans Service Process from a Template
Create a unique version of the Notify Travel Plans service process to provide a personalized and seamless experience for your users. - Add Data Attributes for the Notify Travel Plans Service Process
Create data attributes to store information that a customer provides. The Notify Travel Plans service process has predefined data attributes. Create more data attributes based on your business needs. - Create a Notify Travel Plans Action
Create an action launcher deployment that uses the service process template to give your users quick access to the Notify Travel Plans Omniscript. If you have an existing action launcher deployment, add the Notify Travel Plans Omniscript to it. - Add the Notify Travel Plans Action to the Account Page
Add the Notify Travel Plans action launcher component to the account page layout to give your users quick access to the Notify Travel Plans Omniscript. - Add the Notify Travel Plans Action to the Card Record Page
Give your users quick access to the Notify Travel Plans Omniscript. - Configure State and Country or Territory Picklists for Notify Travel Plan Service Process
Standard or custom address fields use picklists for the State and Country address fields. Before you enable standard or custom address fields, configure the State and Country or Territory picklists. Configuring picklists ensures continuity and data integrity with existing state, country, and territory data and customizations.
Did this article solve your issue?
Let us know so we can improve!
