Standard features versus the managed package in a new implementation
Key Takeaway
For a new implementation, Salesforce recommends building on standard features and keeping the managed package to a minimum. Turning on the "Financial Account Management Standard Objects" setting gives you the standard Financial Account objects and the standard console apps, such as Retail Banking. You don't need to install a package for either.
Agentforce Financial Services features come from two places. They come either from standard features built into the core Salesforce platform or from the managed package, which delivered the product's original features. Most features are now standard, so a new design starts there and uses the package only for something that exists only in it. The two also use different data models, which changes how you model account owners, record details, and field validations.
Standard features and the managed package
Agentforce Financial Services first delivered its features through the managed package. Today, most features run on the standard platform and don't need the package installed. Foundational capabilities became standard features with Winter '23 and Summer '24. Examples are Financial Goals, the Financial Accounts data model, Groups and Households, and Rollups.
The default and recommended way to implement Agentforce Financial Services is directly on the core Salesforce platform. Most features an org needs are available without a managed package. Building on the platform simplifies implementation and gives users a more streamlined experience.
The managed package carries these costs:
- Extra implementation steps
- A push upgrade for each release, which means the package can fall out of sync with standard release schedules
- Less access to the latest standard platform innovations
- More effort spent on maintenance