Standard vs Custom Jobs

This article provides information on standard jobs versus custom jobs in Fullcast. A standard job allows for more user control over the fields and settings involved in the integration and export/import of information between the two systems. In contrast, a custom job requires more support from your Fullcast team to make changes.

Scenario	Standard Job	Custom Job
Ability to add a field for import to Fullcast.	Yes	No
Ability to add a new object/entity for import into Fullcast.	Yes	No
Ability to add a new Salesforce connection for import into Fullcast.	Yes	No
Ability to add a new role to export to Salesforce.	Yes	No
Ability to export data from Fullcast to more fields outside of the standard job e.g. Account Owner, Custom Fields.	No	Yes
Scheduling of import and export jobs.	Yes	Yes
Auto Rerun Rules.	Yes	Yes
Modify Import Configuration: Add a field, add a new object or entity, or add a new Salesforce connection.	Yes	No
Modify Export Configuration: Add a new role for export.	Yes	No
Ability to add a new Salesforce connection for import into Fullcast.	Yes	No
Ability to add a new role to export to Salesforce	Yes	No
Ability to export data from Fullcast to more fields outside of the standard job e.g. Account Owner, Custom Fields.	No	Yes
Scheduling of import and export jobs	Yes	Yes
Auto Rerun Rules	Yes	Yes

Standard Job Considerations

Data is exported only to the Account Teams, Territory Members, and GTM Objects.
The field population on the Account object must be completed using the Salesforce Flow Builder.
We maintain control over Flow logic and the ability to troubleshoot data issues without Fullcast support.
Data flowing into these objects typically has a lower likelihood of failure due to reduced automation and validation, ensuring better synchronization between Fullcast and Salesforce.

Custom Job Considerations

Turnaround time for updates to import jobs is 2 - 3 days
Turnaround time for updates to export jobs is 3 - 5 days
Higher likelihood of data difference between Fullcast and Salesforce due to failures from governor limits and validation rules in Salesforce.