Salesforce Integration Requirement
The Fullcast - Salesforce integration is necessary to access data used for GTM planning in the Fullcast App, migrate planned data, and execute policies within Salesforce. The integration includes importing data, exporting data, and accessing Salesforce/Fullcast metadata.
Fullcast provides a standard out-of-the-box integration with Salesforce that requires the below requirements to be met.
Data Access Requirement
Object and field access required for each of the integration types is listed below.
Import into Fullcast
Read-only access to the below objects and fields is required for importing data into Fullcast
|Account Name||Name||Name||AccountId||OpportunityId||Role Name||Account/User/Product Reference|
|Parent ID||First Name||Product code||OwnerId||Product2Id|
|Parent Name||Last Name||Quantity Unit of Measure||Type||UnitPrice|
|Last Modified Date||Last Modified Date||Family||StageName||Quantity|
|Created Date||Created Date||isActive||Amount||ListPrice|
|Billing or Shipping Address||Address||isArchive||RecordType.Name||Opportunity.StageName|
|Owner ID||User Role name||Last Modified date||IsDeleted|
|Owner Name||Profile name||Created date|
|Owner Role Name||User Type|
|Owner Profile Name||User Name|
|Record Type ID||isDeleted|
|Record Type Name||Title|
Export Into Salesforce
Modify All access is required for the below objects to export GTM data into Salesforce.
- Account Team (Standard Object)
- Fullcast Custom objects
Fullcast App - Motion Package API integration:
The Fullcast app and motion package is integrated via REST API, Apex REST API, and Apex REST callout.
- Fullcast Motion Policy Configuration: Configured in Fullcast and available in Salesforce during policy execution. Requires access to Salesforce standard object/field metadata.
- Leads: If Lead Routing Policy is configured
- Accounts: If Account Routing Policy is configured
Pre-requisite: Import & Export data requirements are met.
The below setup is required to enable standard integration successfully in Fullcast.
- Motion Package installation (Salesforce managed package)
To install the managed package in Salesforce request the Motion package URL from your Business Partner and follow the instructions for installation.
- Salesforce API user:
An API integration user must be created in Salesforce. This user will be the main authentication method for the Import and Export of data and also for Rest API-based app integration with Salesforce.
The API user needs to be created based on the below field selections.
- License: Salesforce Platform/Standard User
- Profile: API Only/System administration/Any custom profile
- Profile access: Provide access from either of the below steps
Option 1: Provide access to objects and fields.
Option 2: Assign Permission Sets to users (Available from Motion package V2.177):
- Fullcast Import permissions: View All access (objects listed under Import)
- Fullcast Export permissions: Modify All access (objects listed under Export)
- Fullcast Motion permissions: Modify All access to all Fullcast objects and fields
Note: Currently the integration authentication is not available within Fullcast. If API user access cannot be managed by Fullcast, the business partner will assist in setting up the integration.
- Connected App Setup
After the managed package is installed, a connected app needs to be created. The Connected App will be leveraged for
- Fullcast app- Salesforce policy metadata configuration
- Territory routing via API integration (e.g dynamic territory routing of leads/accounts)
- Self-service workflows (Canvas app) in Salesforce
Frequently Asked Questions
What are the options if specific objects or fields cannot be provided access?
A custom integration needs to be built that will not have the ability to use all the features provided by the standard integration.
Are there any field limitations to what can be pulled into Fullcast?
There are no limitations on the type of fields that can be imported into Fullcast from Salesforce.
What Salesforce editions is Fullcast compatible with?
Enterprise and Unlimited.
Are new custom Objects being introduced into the Salesforce instance? Which object permissions are needed as part of this integration?
Yes. The Motion Managed Package will add custom objects for which the solution will require permissions. For the standard objects, the fields that are imported will be based on whether it's needed for planning or not. This is fully configurable and will be based on the needs of the RevOps team. The standard objects we need for planning are accounts, users, and opportunities. Once planning is done certain information such as Territory, Account Team, and Quota information can be pushed back into Salesforce. This is also configurable based on needs. We recommend using a unique/separate integration user.
What's the frequency and volume of transactions in 24 hours time frame?
This is configurable but usually once every 24 hours. We pull in delta changes in the past 24 hours for the standard objects mentioned above. The volume will depend on how much volatility you have in Account and user data, or any other objects/fields needed for planning. For most of our customers, this is minimal with imports not exceeding 2K records every 24hrs.
What kind of Salesforce APIs are being used? (APIs being leveraged for Salesforce integration use REST/ SOAP/ Events API)
For Import and Export - Salesforce Bulk API.
For App to Salesforce metadata integration - REST API.
Is It a Synchronous or Asynchronous transaction?
Configurable based on the salesforce environment and governor limits. Defaults to Asynchronous.
Does this package require a Full admin profile and a specific license?
No, though a separate integration user is recommended.
Does Fullcast provide the ability to customize the batch size?
Yes. You can control the batch size to deal with governor limits.
Is there error logging available?
A custom error logging object is available for any errors in Salesforce. This can be enabled and disabled via configuration and can be set up for automatic purging of error logs. Fully compatible with Salesforce debugging and logging capabilities.
What are the disable options for the package integrations?
Standard Salesforce Connected App/OAuth Settings is used for integration providing the ability to control access for the App to Salesforce REST API integration. For the Import/Export data integration, access can be controlled via the integration user.