To successfully send webhook notifications from SAP SuccessFactors, follow these steps in your SAP SuccessFactors account and complete the necessary actions.
Background Check Central Configuration
Other Background Check Vendor
Go to Integration Center
My Integrations
.Select the Type of Integration Center Template
+ Create
button and select More Integration Types to access the list of available integration types.Create
buttonJobApplicationBackgroundCheckRequest
, and then select it from the search results.Options Step
Next
button to proceed with further configuration steps. You can also click the Save
button to save the current step’s configuration.Configure Fields Step
+
button > Insert Sibling Element, then click on the inserted element to open a prompt where you can enter the name of the element.+
button > Add Child Element for the added element and then click on the inserted element to open a prompt where you can enter the name of the child element.Set as Associated Field
icon.Change Association
button.Please follow the mapping below to receive the correct order notification
Expected properties of data fields | To | Corresponding properties in the OData API entity |
---|---|---|
backgroundCheckInfo/requestId | -> | requestId |
backgroundCheckInfo/bgiAccountId | -> | jobApplication/jobRequisition/bgiAccountId/id |
backgroundCheckInfo/packageId | -> | jobApplication/jobRequisition/packageId/id |
backgroundCheckInfo/packageExternalCode | -> | jobApplication/jobRequisition/packageId/externalCode |
backgroundCheckInfo/packageLocaleLabel | -> | jobApplication/jobRequisition/packageId/localeLabel |
createdByUserInfo/userId | -> | createdByUserNav/userId |
createdByUserInfo/firstName | -> | createdByUserNav/firstName |
createdByUserInfo/lastName | -> | createdByUserNav/lastName |
createdByUserInfo/email | -> | createdByUserNav/email |
createdByUserInfo/jobRole | -> | createdByUserNav/jobRole |
createdDateTime | -> | createdDateTime |
lastModifiedDateTime | -> | lastModifiedDateTime |
orderStatus | -> | orderStatus |
responseCode | -> | responseCode |
responseDetail | -> | responseDetail |
vendorCode | -> | vendorCode |
vendorOrderNo | -> | vendorOrderNo |
applicationInfo/applicationId | -> | jobApplication/applicationId |
applicationInfo/appStatusName | -> | jobApplication/jobAppStatus/appStatusName |
jobRequisitionInfo/jobReqId | -> | jobApplication/jobReqId |
jobRequisitionInfo/externalTitle | -> | jobApplication/jobRequisition/jobReqLocale/externalTitle |
jobRequisitionInfo/hiringManager/usersSysId | -> | jobApplication/jobRequisition/hiringManager/usersSysId |
jobRequisitionInfo/hiringManager/firstName | -> | jobApplication/jobRequisition/hiringManager/userNav/firstName |
jobRequisitionInfo/hiringManager/lastName | -> | jobApplication/jobRequisition/hiringManager/userNav/lastName |
jobRequisitionInfo/hiringManager/email | -> | jobApplication/jobRequisition/hiringManager/userNav/email |
jobRequisitionInfo/hiringManager/operatorRole | -> | jobApplication/jobRequisition/hiringManager/operatorRole |
jobRequisitionInfo/hiringManagerTeam/usersSysId | -> | jobApplication/jobRequisition/hiringManagerTeam/usersSysId |
jobRequisitionInfo/hiringManagerTeam/firstName | -> | jobApplication/jobRequisition/hiringManagerTeam/userNav/firstName |
jobRequisitionInfo/hiringManagerTeam/lastName | -> | jobApplication/jobRequisition/hiringManagerTeam/userNav/lastName |
jobRequisitionInfo/hiringManagerTeam/email | -> | jobApplication/jobRequisition/hiringManagerTeam/userNav/email |
jobRequisitionInfo/hiringManagerTeam/operatorRole | -> | jobApplication/jobRequisition/hiringManagerTeam/operatorRole |
candidateInfo/candidateId | -> | jobApplication/candidate/candidateId |
candidateInfo/firstName | -> | jobApplication/candidate/firstName |
candidateInfo/lastName | -> | jobApplication/candidate/lastName |
candidateInfo/primaryEmail | -> | jobApplication/candidate/primaryEmail |
candidateInfo/contactEmail | -> | jobApplication/candidate/contactEmail |
Response Fields Step
Switch to Field Mapping View
option,+
button and select the JobApplicationBackgroundCheckRequest
entity. Then click Add
and proceed by clicking the Next
button.Filter and Sort Step
Next
button.Destination Settings Step
REST Server Settings
and input the following details:Basic Authentication
from the dropdown menu.External Trigger Token
that you receive from the StackOne Integration Hub
during the connection setup.POST
method under REST Operation Settings.Next
button to proceed.Review and Run Step
Save
option. After creation, the template will run in the background, eliminating the need to click Run Now
.Last Run Time
link.Go to the Manage Data
Recruiting External Vendor
from Create New dropdownBackground Check
as the Integration Type from the dropdown menu. Click on Save
to create the vendor.External Code
refers to a text string that serves as a code for the background check vendor. The OData API entities use this value to facilitate communication between the third-party vendor and SAP SuccessFactors. If this information is not entered correctly, certain integration scenarios may fail to function properly.Go to the Manage Data
Recruiting Vendor Integration Mapping
from Create New dropdownYes
.Enter a numeric value in the Hours Before User Can Reinitiate field. This field currently has no functionality in SAP SF.Save
to save the mapping between the vendor and integration.Recruiting Vendor Integration Mapping
can be active at a time. To set the selected vendor integration as active for the instance, select Yes
in the Default Integration field.Go to Manage Templates
Standard Job Requisition
.How to Locate the Job Requisition Template Name
i
icon to view the Job Requisition Template.Add bgiAccountId & packageId fields in template
You can specify the standard fields `bgiAccountId` and `packageId` using the Job Requisition XML as well.
Publish
button.Go to Manage Templates
Field Permissions Defined
, and then click on Add Field Permission
from the modal.Write Permission
Recruiter
bgiAccountId
& packageId
fieldsAll
or pre-approved
from dropdownPublish
to save your changes.Go to background check accounts
PickList Center
bgiAccountId
Add New Accounts
bgiAccountId
. This will direct you to the Picklist Values page where you can add different Background Check Accounts
.Go to the packages
PickList Center
packageId
Add New Packages
packageId
to go to the Picklist Values page, where you can add different Background Check Packages
.Background Check
stage in the talent pipeline for the Job Requisition.Go to Applicant Status Configuration
Edit Applicant Status Configuration
.Select the specific Applicant Status Set currently in use for the job requisition, such as the Standard Status Set
.Standard Status Set
,Edit Applicant Status Set configurations
Background Check
stage, edit and select none
from the Status Group
dropdown. This will make the Background Check visible as a separate stage in the Job Requisition’s Talent Pipeline.Save and Finish
button to save your changes.Where can you verify the added stage
Go to Job Requisition
View or Edit Requisition
.Save Changes
button.If fields are not visible after adding fields & permissions in above steps
OData API Metadata Refresh and Export
Refresh
button next to Cache.Background Check
as a separate step in the current Job Requisition, please visit this step.Go to Talent Pipeline
Move Candidate
option from the Take Action menu.Background Check
from the dropdown menu, then click Apply Updates
to move the candidate forward.Send Background Check to Candidate
Initiate Background Check
option in the Take Action menu.If `Initiate Background Check` option is not present
Assign Background Check Initiate Permission
Assign Background Check Initiate Permission
Background Check Initiate Permission
and Allow users to execute “Application/UI” or “Event-based” Integrations role-based permissions from Admin Center.Confirm
to send the Background Check. You’ll get the success on the same modal.How to view the requested background check?
Go to Background Check portlet
Background Check
stage, The results will be available in the Background Check portlet within the candidate application.