SAP Knowledge Base Article - Public

2472497 - Single-Stage, Late Stage and Multi-Stage Application - Recruiting Management

Symptom

This article provides information regarding the Single-Stage, Late Stage and Multi-Stage Application environments.

Environment

SAP SuccessFactors Recruiting Management - All Versions

Resolution

  • Single-stage application environment: Candidates complete the application data at the initial application point and cannot change or add to their data later. Recruiting users can see all fields in all application statuses.
  • Multi-stage application environment: The fields available to a candidate or recruiting user vary, depending on the current status of the application. That is, the candidate completes a set of application data at the initial application and can be granted permissions to edit that data, or access other fields depending on the status of the application. Recruiting operators can view and write to different fields depending on the status of the application

When the multi-stage environment is enabled in Provisioning, the majority of the application field-permissions are removed from the Application XML and defined in the Requisition XML, underneath the <applicaton-status-config> element, referencing the appropriate statuses.

The fields statusId, resume, coverletter, comments must remain defined in the Application XML field-permission elements when multi-stage application functionality is enabled.

In a multi-stage environment, all required fields for all status operators must be filled out before a recruiting user can successfully change the applicant’s status to any In Progress status. An applicant can be moved to a disqualification status at any point, regardless of whether or not required fields are completed. When configuring multi-stage application, define all statuses in the status in the candidate permissions model, or else the candidate can view all fields.

If the "Enable Multi Stage Application" feature is enabled in Provisioning, while uploading a Job Requisition template, the status names were not validated by the Recruiting system although wrongly typed status names could cause system errors.

It is also important to mention that when you are using Odata upsert queries to add or edit applications within job requisitions, it will not be possible to add information to any random set of application fields, instead, it will only be possible to upsert information if you also choose to provide information to all mandatory fields in the application, regardless of the application status the candidate could be.

  • Late-Stage application environment: Some clients may ant to allow recruiting users to place a candidate in the main applicant status pipeline, even if the candidate has not yet completed an application. The late stage application feature supports this need.

When late stage application is enabled in Provisioning, an Add To Requisition option becomes available in the Actions menu and as a button on the applicant record of forwarded candidates.

Unlike the Invite to Apply functionality available in the Forwarded status, the late stage application Invite to Apply can be selected multiple times. Both Invite to Apply features use the same e-mail template.

If late-stage application is used with multistage application, a candidate who responds to the invitation to apply sees all fields exposed in all statuses up to and including the status they are in.

Note to consider: The recruiter will be able to move the candidates through application statues even if there are some mandatory fields not filled.

Keywords

Single Stage, Late Stage, Multi stage, Single-Stage, Late-Stage, Multi-Stage , KBA , LOD-SF-RCM-APP , Applicants and Job Applications , LOD-SF-RCM-JOB , Job Postings & Requisitions , How To

Product

SAP SuccessFactors Recruiting all versions