MuleSoft Accelerator for Financial Services Release Notes
1.11
March 26, 2024
What’s New
The Unlock Jack Henry SilverLake Core use case now includes fee reversal, stop check, and stop ACH transaction capabilities. The SilverLake Accounts System API and Salesforce Financial Services Cloud Setup Guide are updated to accommodate these new features.
1.10
January 30, 2024
What’s New
This release introduces the Unlock AMS Through Hyperautomation for Insurance Brokers use case. MuleSoft’s hyperautomation suite enables customers to leverage the power of automation and integration to solve complex issues in their organization. Hyperautomation is an ideal solution for integration with closed-box systems, because traditional integration methods with such systems are often unsuccessful.
The Unlock AMS Through Hyperautomation for Insurance Brokers use case provides an RPA Bot and pre-built APIs and templates to unlock data from Agency Management System (AMS) platforms for insurance brokers, and then connects that data to Financial Services Cloud (FSC) as the system of engagement. These pre-built assets eliminate the need for dual data entry and swivel chair analysis, enabling a full Customer 360 in a CRM platform.
An AMS platform is the source system for the insurance policy data leveraged in this use case. The RPA Bot extracts the insurance data from the AMS platform into a CSV file. Then, the AMS data in the file is mapped to FSC objects for presentation in the CRM platform, resulting in the Customer 360 view.
1.9
August 31, 2023
Thought Machine’s Vault Core delivers an expanded view into a customer’s financial account information by leveraging the Vault Core platform as the source system for the financial data leveraged as part of this use case.
This use case includes pre-built APIs and templates to unlock data from Vault Core and connect that data to Salesforce Financial Services Cloud as the system of engagement. By using the pre-built assets, customers can accelerate the process of getting critical customer data into Salesforce Financial Services Cloud so that they can access financial account data and the corresponding transactions.
The Vault Core platform will be used as the source system for the financial data that is leveraged as part of this use case. The Vault Core data objects will be mapped to CIM data objects.
In addition, all BIAN assets that are listed as version 11 on the BIAN Assets page in Exchange were either created or updated as part of this release.
1.8
March 21, 2023
This use case introduces the Salesforce org sync, which enables syncing customer profile data between Salesforce Sales Cloud, Salesforce Service Cloud and Financial Services Cloud.
Since many Salesforce customers opt to implement a multi-org solution for their Salesforce instance, this means that Salesforce customers must also have an org migration strategy defined to support the sharing of data between orgs. Defining a migration org strategy is a complex activity, often requiring the assistance of a third party. This solution enables the actual movement of data between orgs, including the data objects - accounts and contacts - and the order of those objects.
From a technical perspective, this release introduces major changes to the way the synchronization of customer profiles is handled. Customers will now have the ability to sync multiple reference data providers by using the runtime properties, as well as onboard any reference data provider to the sync process without making any code changes. The result is a simplified set of data synchronization processes with support for plugging in different reference data providers, such as Salesforce.
In addition, this release introduces platform events to capture data changes in Salesforce. Scripts for platform event creation and triggers are also added.
1.7
December 13, 2022
Unlocking Jack Henry SilverLake Core Use Case
This use case introduces the Jack Henry SilverLake core as the Core Banking system implementation, which allows customers to synchronize Salesforce Financial Services Cloud data with SilverLake.
From a technical perspective, this release introduces major changes to the way the synchronization of customer profiles and financial data is being handled - particularly with respect to the management of reference data. The net result is a simplified set of data synchronization processes with support for plugging in different reference data providers (for example, Salesforce) in a future release.
The generic database implementations were also migrated from a MySQL provider to MariaDB. This change makes it feasible to publish database-dependent assets to GovCloud without sacrificing support from AWS RDS.
Finally, although the net impact on API implementations is minimal, it is important to note that the custom FINS data models (provided via the FINS Common Library, FINS Banking Library, and FINS Insurance Library assets) have been consolidated within the existing CIM model by introducing two new libraries: the CIM Setup Library and the CIM FINS Extension Library. This moves us closer to having a consistent canonical model that is more closely aligned with the Salesforce Customer 360 Data Model.
1.6
September 13, 2022
1.4
April 28, 2022
Address Change Orchestration Use Case
Introduces the Address change orchestration use case. There are two extensions of this use case:
-
Use Case 4a - Address Change Orchestration: Insurance — Streamline downstream events that result from policyholder or carrier postal address adjustments. The address change orchestration use case for insurance delivers a solution for address confirmation, seamless policyholder data updates, and single home policy coverage assessments, resulting in faster policyholder premium updates.
-
Use Case 4b - Address Change Orchestration: Banking — Enhance your customer service teams’ upsell, cross-sell, and service opportunities that result from customer postal code address changes. The address change orchestration use case for banking supports faster address validation and increased customer service opportunities, including personalized products and offers.
1.3
March 21, 2022
Minor Updates
A few assets were updated to correct minor issues, including:
-
Database creation scripts
-
Visualizer layer assignments
-
Documentation updates
January 28, 2022
Payments Modernization Use Case
Introduces the Payments Modernization use case, which accelerates the development of modern payment solutions for Financial Institutions. Banks and Credit Unions will be able to deliver a diverse payments landscape that can address multiple types of financial transactions and customer needs.
1.2
November 16, 2021
Core Banking Enhancements
This release includes the following enhancements:
-
Added more information to both the customer accounts sync and customer onboarding use cases
-
Added credit card functionality
-
Added full two-way synchronization capabilities between customer accounts, transactions, and credit cards
See the Upgrade Notes for more information.
1.1
September 9, 2021
Customer Onboarding Use Case
Introduces the Customer Onboarding - Banking use case, which allows leverages Salesforce Financial Services Cloud as the system of engagement, DocuSign as the document management system, and Equifax as the credit analysis system.
1.0
July 27, 2021
Initial Release
This is the first release of the MuleSoft Accelerator for Financial Services.
This accelerator also introduces the Unlock Any Core use case, which allows for the display of a customer’s financial summary from multiple systems. The customer and customer service representative (CSR) views are supported in this release.