This document discusses pre-day 1 onboarding data flow. It explains that recruiting sends candidate and applicant IDs to onboarding. Onboarding then sends these IDs plus a unique HRDataID to its management data file table after post-hire verification. This allows managers to provide pre-day 1 access to new hire onboarding content. When new hires complete onboarding paperwork, employee central pulls over the data including HRDataID. After hiring, employee central matches new employees to their pre-day 1 records using HRDataID to merge the temporary and permanent records. The data flow ensures a smooth pre-day 1 onboarding experience.

1. HR AS A SERVICE:
Driving Workforce Competitive Advantage
HR AS A SERVICE:
Driving Workforce Competitive Advantage
Onboarding Pre-Day 1 Data Flow
Curtis
Weldon03/17/2016

2. What is
Pre-Day 1?
Pre-Day 1 is the ability to provide the
New Hire with access to Onboarding
Mobile and the Home Page prior to
the Start Date.
• Increase employee engagement
• Connect new hires with the right
people and relevant content
before they start
• Improve process efficiency and
compliance

3. Pre-Day 1 Data Flow
Recruiting sends Onboarding two fields from the Candidate Profile:
• candidateId
• applicantId
These are the only fields that can be sent from the Candidate Profile
and are sent through the background of the integration.
After the completion of the Post Hire Verification Step, Onboarding sends
these three fields to the Onboarding MDF Table so the Manage Activity
Process can be created/started.
• candidateId
• applicantId
• HRDataID
Onboarding creates a unique ID for every candidate and user. It’s
called the “HRDataID”. It’s used to tie the various elements of a
record together in Onboarding.

4. Pre-Day 1 Data Flow (cont.)
The Hiring Manager works the Manager Activity Wizard allowing the
content of the Home Page Tiles / Mobile Tiles to be viewed by the
New Hire. If Pre-Day 1 functionality is turned on the New Hire will be
able to view the content immediately (following day for HRIS –
OnStartDate job must run).
Once the New Hire completes their Onboarding paperwork and
finishes the New Employee Step Employee Central pulls the New Hire
Data into Manage Pending Hires including the following 3 fields:
• candidateId
• applicantId
• HRDataID
Once the New Hire is “Hired” into Employee Central the permanent
employee record is created. The system looks for original HRDataID of
the New Hire in the MDF table to merge with the Pre-Day 1 record.

5. Additional Knowledge
When Pre-Day 1 is turned on in Provisioning it automatically adds the
OnboardingID field to the User Data File. This field is populated with
the Onboarding HRDataID.
If a customer is not using Employee Central the HRDataID must be
added to the Onboarding Data Export to go to the HRIS System. The
HRIS must add this field to the OnboardingID field on the User Data file
to go back to SuccessFactors.
If the HRDataID field is not populated on the User Data field the
system will hold two records for the New Hire. One for the Pre-Day 1
access, and another for the permanent Employee Central record.

6. Recruiting
Onboarding
Employee
Central /HRIS
SuccessFactors
Platform
ONB
Candidate
MDF Table
RCM sends “candidateId” and “applicantId” in
the background of integration from the
Candidate Profile.
ONB Manager
Activity Wizard
Upon completion of the ONB PHV step ONB sends the
“HRDataID”, “CandidateId”, and “applicantId” to the MDF Table.
The Manager Activity Process is Started. The Employee can now
view their Home Screen Tiles Pre-Day 1 Employment.
Pre-Day 1 Data
After the New Hire completes the NES step in Onboarding the
“HRDataID” is automatically sent to EC.
EC/HRIS takes the “HRDataID” and places it in the
“OnboardingID” field to send it to the SF platform after the New
Hire Start date. This matches the temporary record with the
permanent record. The two records are then merged.

7. Aasonn