MuleSoft Accelerator for Financial Services icon

MuleSoft Accelerator for Financial Services

(5 reviews)

Use case 6 - Salesforce org sync

Deliver a multi-org strategy faster with the Salesforce org sync use case.

Financial institutions are increasingly implementing a multi-Salesforce org strategy, which allows them to tailor the enterprise data strategies, back-end architecture, and governance structure for each business unit. This simplifies the configuration and management of org-wide settings and offers greater flexibility and speed for delivering enhancements. However, keeping data up to date across orgs is complex and time consuming.

Organizations need a solution that supports one-time and ongoing org synchronization so that financial institutions can have a complete and accurate view of their customers.

Ultimately, financial institutions will be able to better serve their customers and deliver innovations faster.

Overview

See also

Description

This use case establishes the foundation for the Salesforce org to org synchronization process. Pre-built APIs and templates map Accounts and Contacts from Financial Services Cloud to Financial Services Cloud and from Financial Services Cloud to Sales Cloud and Service Cloud and vice versa.

Glossary

TermDefinition
CIMThe Cloud Information Model for MuleSoft Accelerators defines a set of standard data structures that can be used as canonical representations of common entities for integrating systems.
FINSAbbreviated term referring to the Financial and Insurance industries consisting of the Banking, Insurance and Wealth Management domains.
FSCSalesforce Financial Services Cloud. Provides capabilities to support Banking, Insurance & Wealth and Asset Management sub-verticals.
Global DataA Global Data service provides an accurate, consistent, and complete copy of business data for use by enterprise applications and business partners while also providing a means to link that copy to occurrences in other systems.
OrgAbbreviation for Salesforce Organization. A Salesforce org contains all of an organization’s data, processes and business functionality.

Solution overview

The org sync solution enables organizations that have a multi-org strategy for their Salesforce instance to migrate data between their Salesforce orgs by enabling the creation and update of consistent and connected customer profiles across relevant applications, regardless of where the customer's journey starts. Salesforce Core data objects - accounts and contacts - can be connected from FSC to FSC and from Salesforce Core to FSC. Financial institutions need the ability to move data between Salesforce orgs to ensure customer service representatives have the most up to date data to support their customers.

Sync the following data objects in this order between FSC orgs:

  • Contact objects
  • Account objects

Sync the following data objects in this order between Salesforce Core and FSC orgs:

  • Account objects
  • Contact objects

Syncing occurs when the data change is noted.

Assumptions and constraints

  • Organization is not yet syncing data between orgs.
  • Organization has Sales Cloud, Service Cloud, or FSC.
  • A MariaDB database will be used as the back end for the generic systems.
  • The solution can be extended to use any salesforce cloud which support core objects.

Before you begin

bulb.png The Getting Started with MuleSoft Accelerators guide provides general information on getting started with the accelerator components. This includes instructions on setting up your local workstation for configuring and deploying the applications.

API-led diagram

fins-api-led-diagram-org-sync.svg

Goals

  • Provide an org migration solution for customers who take a multi-org approach to their Salesforce implementations.
  • Support the creation of customer profiles across relevant applications.
  • Support the creation of Global Customer ID & ID attribution.
  • Orchestrate customer updates across designated applications.

Use case considerations

  • A Global Data service will provide the golden copy of the customer profile.

Technical considerations

  • Use CIM as the canonical model, where applicable (e.g., for Customers).
  • Only core objects Account and Contact are part of the sync process.

High-level architecture

The following diagram represents the portion of the overall solution that pertains to the org to org sync use case.

fins-salesforce-org-sync.png

Processing views

The diagrams below illustrate the processing sequences for the integrations and data synchronization activities included in this release.

Customer update sync

This activity diagram describes the process of synchronizing updates made to customers in any Salesforce Cloud to downstream systems.

fins-activity-customer-update-sync.png

Contact update sync

This activity diagram describes the process of synchronizing updates made to contacts in any Salesforce Cloud to downstream systems.

fins-activity-contact-update-sync.png

Systems involved

  • Global Data (generic)
  • Salesforce Financial Services Cloud
  • Salesforce Sales Cloud
  • Salesforce Service Cloud

back to top

Downloadable assets

Shared APIs (can be used across any use case)

Custom components


back to top


Reviews

DU
Deleted UserNov 3, 2023, 1:29 PM
Few Serious Gaps
First of all Slack is not used by any reportable financial institution as messaging system. All financial messaging related to investments MUST be recorded as per regulatory and company security controlled. Hence more likely you should integrate it with Symphony (project backed up by Goldman Sachs and used by serious financial institutions... also can be integrated with custom bots and AI). For sure Slack is not approved by vast majority of financial institution so ownershipby Salesforce has no bearing to what they choose in regulated world. Also data between private and public sector must be segregated by financial regulations. Security of many financial areas requires tokenization and hence you do not have ability to market based on data analysis in bulk, but perhaps only based on individual relationship of bankers and wealth managers without releasing this information to global financial population. Also flows are not part of any standard. I have worked in financial company (hedge fund) where every division had different and optimized approach and you would not change it. And for the record the name should be more of prospect investor onboarding than "client". We did full conceptual analysis with diagrams from CRM systems to asset management down below many others. Add to this that every financial company has their silos and with this accelerator and approach of pushing it on industry experts (even during your webinars) you have recipe why Mulesoft cannot get into financial market that easily.
TypeCustom
OrganizationMuleSoft
Published by
MuleSoft Solutions
Published onAug 31, 2023
Contact nameMuleSoft Solutions
Contact emailsolutions-questions@mulesoft.com
Asset overview

Asset versions for 1.9.x

Asset versions
VersionActions
1.9.0

Categories

Accelerator
Financial ServicesNo values left to add
Industry Vertical
Financial ServicesBankingNo values left to add

Tags