Duaer

Guides

SAP SuccessFactors hiring process: see where each application waits

Connect SAP SuccessFactors Recruiting to Duaer. It reads each job application's steps from applied through screening, interviews and offer to start.

What does Duaer read from SuccessFactors?

Each job application is a case, with the job requisition, job title, department and location. Candidates' names and contact details are never read. The steps are Applied, each status the application moved to, and Started (the start date).

  • Statuses whose names say screening, interview, offer or offer accepted match the hiring and onboarding template's steps; others, such as rejected or withdrawn, keep their names.

How do you connect SuccessFactors to Duaer?

  1. In SuccessFactors Admin Center, register an OAuth2 client application, generate its X.509 certificate, and note the API key and the private key.
  2. Prepare a user who can view Recruiting applications and job requisitions.
  3. In Duaer, create an SAP SuccessFactors API credential with your data center's API host (such as api4.successfactors.com; China's is api.sapsf.cn), the company ID, the API key, the user ID and the private key.
  4. As an owner or admin, open Data sources, select Add source, choose SAP SuccessFactors under Hiring and onboarding, choose the credential, select Check connection and confirm.

How often does it read, and how much?

Each run reads the applications changed since the last one, with their status history; a first read starts two years back and finishes over several runs. A step is never written twice. Read only.

What are the limits?

  • The tables, entities and fields read follow the vendor's published documentation and are not yet checked against a real system; the first real read may need adjustments.
  • Interview feedback and offer details are not read.

Questions

Does Duaer read candidates' personal data?

No. It reads application numbers, the job and status changes; never names, emails, phone numbers or resumes.

In this section

Process

Add a process source in Duaer

A process source tells Duaer where to read the steps of your cases: a CSV or XLSX file, files dropped in an S3 or SharePoint folder, PostgreSQL, MySQL, Microsoft SQL, Oracle, TiDB, OceanBase, KingbaseES, SAP HANA, IBM Db2, Dameng DM8, Teradata, Vertica, Snowflake, BigQuery, Databricks, Microsoft Fabric, Amazon Redshift, Azure Synapse Analytics, ClickHouse, Trino, a Feishu Base, or Feishu, DingTalk or WeCom approvals. The wizard takes you through columns, mapping, a preview of issues and a schedule; after you confirm, Duaer reads new rows on that schedule.

Process

See the process in your data and generate workflows in Duaer

Duaer reads the steps every case went through from the tables, databases or Feishu apps you already have: where cases wait too long, where they branch and who did each step. From that it generates three kinds of workflow, Watch, Coordinate and Execute, and replays each over past days before you publish it.

Process

Process findings and SOP conformance in Duaer

Process findings list the steps where cases wait too long or are done again, and which kind of case they happen to most. Propose any of them as a card rule and compare the 30 days before and after it was adopted. SOP conformance compares the SOP in your knowledge base with the steps cases really took.

Follow-through

Oracle HCM hiring process: see where each application waits

Connect Oracle Recruiting Cloud to Duaer. It reads each job application's steps from its phase and state history.

Follow-through

Workday purchase to pay: see where each purchase order waits

Connect Workday to Duaer. It reads the requisitions, receipts, supplier invoices and payments of each purchase order through Workday Web Services, so you see where orders wait and for how long.