🗓️ Join us for Annual Planning Office Hours: biweekly Wednesdays, Oct 7 - Feb 10. Learn more.

Standard and custom jobs

Prev Next

A standard job is a pre-configured integration process that allows users to customize certain aspects of the import and export process, such as adding fields, creating new objects or entities, and adding new Salesforce connections. A custom job is a more complex integration process that requires technical expertise and support from Fullcast. Custom jobs are used for scenarios that involve custom logic, specific data transformations, or integrations with non-standard Salesforce objects.

Scenario

Standard Job

Custom Job

Add a field for import to Fullcast.

✅ Yes

❌ No

Add a new object or entity for import into Fullcast.

✅ Yes

❌ No

Add a new Salesforce connection for import into Fullcast.

✅ Yes

❌ No

Add a new role to export to Salesforce.

✅ Yes

❌ No

Export data from Fullcast to more fields outside of the standard job (Account Owner, Custom Fields).

❌ No

✅ Yes

Schedule 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

Add a new Salesforce connection for import into Fullcast.

✅ Yes

❌ No

Standard job

  • 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

  • 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.