Creating Applicant Statuses for Candidate Application

Considerations for the base set of applicant statuses include:

• Base set must be configured first

• Status sets are created from this base set

• Some statuses are in the system by default and cannot be removed (see green box in the figure shown above)

• All configurable base set statuses have one of the following status types (see red box in the figure shown above)

  • In Progress: Used when applicant is being processed

  • Disqualified: Disposition status, for example "Reject"

  • Onboard (not shown in the figure): Used with the integration of Verifications, Inc.

Statuses can be set up to automatically trigger certain actions, be viewable to certain roles, and be seen differently by internal users and applicants.

To access status options, click the status name or select Edit from the Take Action dropdown menu to open the status, as shown in the figure below.

Review the Field Options in Applicant Status table in the SAP SuccessFactors Recruiting Management Implementation Guide for comprehensive explanations of all fields.

Language to Translate

This field needs to include at least one language (if there are no values in this menu, your changes will not save).

Required

Check this box if the status is required in the talent pipeline/candidate workflow. When selected, the candidate must be placed into this status before being placed into subsequent In-Progress statuses.

The config options labels include the following:

Internal Label

This field is used internally by recruiters and others.

Candidate label

This field is displayed to internal and external candidates. It is common to use "In Progress" or something similar for candidate processing statuses

Next Step Text

This text displays for candidates on their jobs applied page and can inform them of the next steps.

• Enable this status only for internal candidates

  • Used for statuses that pertain to internal candidates only

• Enable this status only for external candidates

  • Used for statuses that pertain to external candidates only (for example, a background check status)

• Hide the status from users who do not have application statusVisible Toprivilege

  • Selected status will not be visible at all to the roles as defined in Visible To section (see the figure, Visible To Options for example of different views)

• Hide applicant count from users who do not have application statusVisible Toprivilege

  • The number of candidates is not displayed to the roles as defined in the Visible To section (see figures below for examples of different views.)

• The figure below displays the Visible To option with full permission.

  

• The figure below displays the view without Visible To permission and with applicant count hidden.

  

• The figure below displays the view without Visible To permission and with the status completely hidden.

  

Collect comment if this status is skipped

This box prompts the recruiter to add a comment if the status is skipped; the comment is then visible in the candidate audit trail portlet.

• This option is only enabled if the candidate status is optional. If the Required field is checked, then the candidate application has to go through this status in the recruiting workflow. This option is then disabled.

Hirable Options

This is used in Recruiting to EC integration.

• See the Recruiting Implementation Handbook for more information on this set up.

Emails can be triggered by status and automatically sent to the candidate and the recruiting roles.

1. First, the email template must be configured: Admin Center → Recruiting → Manage Recruiting Email Templates.

2. Then, the email template can be associated with a role.

   

It is common for a customer’s recruiting process to have steps permissioned or visible only to certain roles and not to other roles.

• The Selectable by feature allows customers to restrict permissions to move or advance a candidate to a particular status. For example, it may be that only the recruiter can move someone to an offer status, so only recruiter would be checked.

• The figure, Config Options Selectable By, shows an example of where the Interview status is selectable only by the Recruiter and Hiring Manager for that requisition. If the Financial Controller views the candidates and looks at the ‘Move Candidate’ option or the Status dropdown, the Interview status option is not listed.

  

The Visible To option allows selected roles to view the candidates within certain statuses.

If the Visible To option is not enabled for recruiting role status is available in the Candidate Pipeline but is grayed out for that role.

If the Visible To is not enabled then the following applies:

• If Hide applicant count from the users who don't have application status Visible To privilege is enabled: The role can see the status but is not able to see count of the applicant

• If Hide the status from users who don't have application status Visible To privilege is enabled: The role is not able to see the status within the talent pipeline neither the applicant count.

A status is not showing in the pipeline. Use the following questions as a checklist for troubleshooting:

• Has the status been created in the base set?

• Has the status been added to the status set?

• Has that status been enabled in the applicant status set?

• Has a label been added for the applicant status?

In summary, each requisition uses its own applicant status flow, which is linked via the JRDM. Applicant statuses allow applicants to be entered into the system and moved through the pipeline.