What is the role of the managed package?
A managed package is used to continuously execute the operational components of your GTM plan directly within Salesforce. This native architecture allows Fullcast logic to run against your records for processes like territory assignments and lead routing. As a result, core operations are performed securely in your environment, minimizing data transit and API call usage.
How are package versions installed and maintained?
The process is handled in two phases:
Initial installation: Your Implementation Consultant (IC) will guide you through the Fullcast provisioning process. They will provide the installation link for the version of the package required for the initial setup.
Upgrades: Your Customer Success Manager (CSM) will notify you when upgrades are available and provide the corresponding installation links. You can also view the managed package release notes for information on new versions.
What types of components are in the managed package?
The package installs a comprehensive set of components into your Salesforce instance. There are four main categories:
Automation and business logic: Includes Apex classes, triggers, and validation rules that execute core GTM processes like territory assignment and lead routing directly on standard and custom objects.
Custom objects and data model: A robust data model with custom objects designed to manage GTM plans, sales territories, user assignments, routing queues, and system jobs.
User interface components: A suite of Lightning Web Components, Visualforce pages, and page layouts that provide the UI for admins and users to manage assignments, configure policies, and view territory details.
Configuration and security: Key administrative components, including permission sets to manage user access, custom metadata for flexible configuration, and remote site settings for required integrations.
What impact does the package have on my Salesforce limits?
As a native application, the package's custom objects and the data they store will count against your organization's schema and data storage limits.
Fullcast’s design philosophy is to minimize this footprint, particularly on core standard objects. For example, while our processes interact with objects like Account and Account Team Member to perform assignments, the package does not add any custom fields to the Account object. This approach contains the package’s impact and helps prevent schema bloat on your most critical data object.
Are there other technical requirements or impacts on my Salesforce org?
Yes. The two main implications are enabling a standard Salesforce feature and authorizing communication with our platform:
Account teams must be enabled: The package requires Salesforce Account Teams to be active in your org, as this functionality is fundamental to our core assignment logic. The feature does not need to be exposed on user page layouts, but it must be enabled.
Remote site settings configuration: The package installation includes Remote Site Settings. These are required to authorize secure communication (Apex callouts) from your Salesforce org to the Fullcast platform API, which is necessary for certain operations.