(Internal) SuccessFactors Integration Customer Eligibility and Setup

🔍 Articles in This Section

Please use the following list to see additional internal articles regarding the SuccessFactors integration:

• (Internal) SuccessFactors Integration Overview
• (Internal) SuccessFactors Integration Customer Eligibility and Setup (📍you are here)
• (Internal) SuccessFactors Integration Available Features and FAQ
• (Internal) SuccessFactors Integration Expected Real-time Webhooks

Customer Eligibility and Prerequisites

The customer must use SuccessFactors as their ATS.

Basic Integration Setup

Through the Support Dashboard on the team’s Overview tab, under ATS Settings, select SuccessFactors from the dropdown menu and click Save.

Advanced Integration Setup

Summary of the steps needed:

1. Complete initial setup (to be completed by the customer)
2. Field mapping (to be completed by the CSM)
3. Deep sync begins (to be completed by the CSM and Engineering)
4. Pipeline Stage Mapping (to be completed by the customer)
5. Configuring Reportable fields (to be checked by the customer)

Note: Like the iCIMS and Workday integrations, this integration is team-level, meaning that once the integration is set-up for the team, every user on that team will be able to use it immediately.

(1) Complete initial setup (to be completed by the customer)

Most of the basic integration setup will be done by the customer with guidance from their CSM which is detailed in the customer-facing resource Setting up Your SuccessFactors Integration.

If the customer completes the steps required of the SuccessFactors deep sync integration, the rest of the onboarding will be completed internally by the CSM and Engineering using the following steps.

(2) Field mapping (to be completed by the CSM)

This is very similar to iCIMS field mapping. Both ATSes are very configurable. This means that customers can change standard field names - for e.g. they can rename the standard “recruiter” field on a Job to “coordinator”.

Note: this is different from custom fields in other ATSes. This is customers renaming standard ATS fields.

Field mapping is about mapping the customer’s field names to the standard SuccessFactors fields that Gem understands.

Please create an Asana task with Engineering, who should follow the steps here +SuccessFactors Steps for Manually Mapping Properties and generate a spreadsheet of fields that need to be mapped. The spreadsheet will look similar to this one.

After you have the spreadsheet, a 30 minute meeting with the customer and the engineer should be sufficient to confirm the mapping.

(3) Deep sync begins (to be completed by the CSM and Engineering)

Make sure there is an Asana task with engineering. Once the field mapping is confirmed, engineering can kick off the deep sync.

Once kicked off should complete in about 1 week.

Note: After the initial deep sync the data will be primarily kept up to date via an incremental sync that runs daily.

(4)Pipeline Stage Mapping (to be completed by the customer)

For pipeline stage mapping this should be similar to other ATSes. Some caveats:

• SuccessFactors doesn’t have stages. It has “statuses” and “status groups”. It’s most similar to iCIMS.
• Note: rejection reasons will appear as statuses. Remember that these shouldn’t be mapped as Gem stages.

(5)Configuring Reportable fields (to be checked by the customer)

Once the sync is complete and the customer starts using/testing the product (e.g. Talent Compass), see if any of the standard Gem fields are missing. For e.g. use the different group bys in PA. If some of the group bys appear as “none” or “not set” it is likely that we were not able to sync one of the core standard fields.

The likely reason is that these fields were not marked as “reportable” in the customer’s SuccessFactors instance and thus are not visible via the OData API which Gem uses to integrate.

The customer needs to put in a request with their SF/SAP admin to make any such fields reportable.

• Customer Eligibility and Prerequisites
• Basic Integration Setup
• Advanced Integration Setup
• (1) Complete initial setup (to be completed by the customer)
• (2) Field mapping (to be completed by the CSM)
• (3) Deep sync begins (to be completed by the CSM and Engineering)
• (4)Pipeline Stage Mapping (to be completed by the customer)
• (5)Configuring Reportable fields (to be checked by the customer)