Managed package installation and unmanaged extension packages
Key Takeaway
Configure Lightning Experience before you enable Agentforce Financial Services. The package links are on your order form under Product Specific Terms. Mortgage flows come by default, but insurance and retail banking flows need the Lightning Flow for Agentforce Financial Services package.
A managed package is an installable collection of metadata designed to enhance a Salesforce org. Salesforce periodically pushes updates to the package. The default and recommended approach is to implement Agentforce Financial Services directly within the core Salesforce platform. A managed-package implementation is for use cases that need features only available with the managed package, such as a dependency on an Independent Software Vendor (ISV) solution. The setup has three parts. First, you prepare the org. Next, you confirm the trial org or install the packages. Last, you add the separate packages that each line of business in the design needs.
Prepare to use Agentforce Financial Services
A few things must be in place before you install or enable anything.
- Configure Lightning Experience before you enable Agentforce Financial Services, because Agentforce Financial Services requires Lightning Experience.
- Set up accounts and user profiles before you install.
- Confirm that the org is Professional, Enterprise, or Unlimited Edition, where Agentforce Financial Services is available.
When you create custom fields or objects, don't use the same API names as any packaged objects or fields. Matching names can interfere with flows, processes, and triggers in Agentforce Financial Services.
A credit union's design depends on an ISV solution that needs the managed package. Before anything is installed, the consultant confirms three things: the org is Enterprise Edition, Lightning Experience is configured, and the accounts and user profiles are set up. Later, the team plans a custom field for member tenure. The consultant checks that the field's API name doesn't match any packaged field, so the field doesn't risk interfering with the package's flows, processes, and triggers.