Product | SuccessFactors integration |
Expert(s) | Brad Edwards, John Yamashiro (Enterprise EPD team) |
Slack channel | |
This article was last verified on | 04/09/2024 |
🔍 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
- (Internal) SuccessFactors integration: Available features and FAQs (đź“Ťyou are here)
- (Internal) SuccessFactors integration: Expected real-time webhooks
Available Features for this integration
- Basic Integration
- Duplicate check and upload
- Advanced Integration (includes duplicate check and upload)
- ATS Candidate Rediscovery
- Talent Pipeline
- Application Review
- Dashboards and Pipeline Analytics
- Data Retention
Basic Integration
Duplicate Check against SuccessFactors
As with our other ATS integrations, we first check whether the candidate exists in SuccessFactors and show you in the minimized Gem extension. We surface potential duplicates based on name & emails.
Once duplicates are surfaced, the user can select which one they want to link to this Gem person
OR, they can upload as a new candidate:
Uploading New Candidates to SuccessFactors
If there are no duplicates or none of them match, you can upload the candidate to SuccessFactors from Gem. Required fields are:
- Name
- Email address
- Country (country has separate dropdown on the component with sticky setting, so it’ll remember the last country you selected)
You cannot upload a candidate to a specific job or create an application for them on the job, but you can forward the candidate to a job (“Job Forwarding,” as SuccessFactors calls it), as well as kick off the “invite-to-apply” flow from the Gem extension. See full details in the “FullFunctional Details” section below.
Please note: these are known required fields based on our instance and a convo with a sales prospect, Owens Corning, who said that was their required fields as well. I believe it is possible to create custom required fields, so if a customer has configured these they’ll need to let us know so we can add them to the extension for them.
We automatically upload the following fields when creating a new SuccessFactors profile:
- Name
- Email address
- Phone number
- Work experience (employer, title, start/end date)
- Education (school, start/end date)
- Current Title
- PDF resume
Advanced Integration (includes basic integration features)
SuccessFactors Feature Capabilities (based off of the Gem Feature Capabilities by ATS)
ATS Candidate Rediscovery
Area | |
Filters | • Job
• Rejection reason
• Reached interview stage
• Candidate tags
• Last in process
• Location
◦ for location normalization, we use a method of extrapolating their current job’s location as the normalization base, instead of a provided location by the candidate |
Columns | • Job applications
• Last in process
• Source
• Rejection reason
• Stage |
Talent Pipeline
Area | |
Sync timing | Real-time |
Views | • Active view
• Consolidated view
• Single job view |
Filters | • Job
• Recruiter (on job)
• Source
• Candidate tag |
Staging | • Stages by job
• Mapped stages (consolidated view) |
Card content | • Last ATS Activity |
Actions | • Link to Candidate in ATS
• Move stage by menu
• Open person modal on click |
Analytics bar | |
Status & SLA | • Touchpoints
• Email notifications on touchpoint SLAs |
Application Review
Area | |
Filters | • Change stage
• Resume keyword search
• Recently rejected
• Multiple apps
• Previously screened
• Previously contacted - Gmail only
• Seen
• Past SLA |
Profile | • Resume
• Custom application questions
• Job applications
• Scorecards |
Actions | • Advance to next stage(s)
• Reject w/ rejection reasons
• Advance/reject with message
• Reject with nurture
• Bulk reject |
Keyword search | • ATS Resume |
Profile
Area | |
Applications tab | • Current stage
• Last activity
• Scorecards (Detailed)
• ATS link
• Hiring team
• Stage reached (Closed only)
• Rejection reason (Closed only) |
Data Retention
- Candidates that have been deleted/anonymized in the ATS will be deleted/anonymized in Gem the next time a full sync occurs. See +ATS Data Sync Overview for how this timing varies by ATS
- Gem profiles will not be deleted/anonymized, even if some of the data in the profile was imported from an ATS candidate that no longer exists
FAQ
Q: Do we support custom SuccessFactor fields for the job metric in Talent Compass reporting?
A: No, but there is an Asana task requesting this.