Describing the New Features and Enhancements for the 2H 2024 Release

Candidate and applicant skills data are now reportable using Story reports.

A query on the Candidate Skill entity or Applicant Skill entity displays the skills and the skill extraction status from the resume. The report also shows whether the candidate or applicant validated their skills.

The enhancement helps recruiters audit skills-related data for candidates and applicants and use it to comply with regulations.

• Enable Assisted Applicant Screening in → AI Services Administration → Feature Settings → Recruiting → Assisted Applicant Screening.
• (Optional) Enable the Assisted Applicant Screening and Allow Applicants to Manually Add Skills options in Admin Center → AI Services Administration → Feature Settings → Recruiting.
• Enable Stories in People Analytics and Recruiting.
• Candidate Skills are available when Mobile Apply is enabled.

• Enable the Create Story permission in Administrator → Reports Permission.

In the previous version, the Candidate Skill and Applicant Skill entities were unavailable in Story reports.

The Audit Trail - Job Requisition, Job Posting Audit History, Application History, and Candidate Profile Fields Audit tables are now available in Story reports.

The enhancement helps generate audit data related to Audit Trail - Job Requisition, Job Posting Audit History, Application History, and Candidate Profile Fields Audit tables.

Job Location and Job Location Short Format generic objects for job requisitions are now reportable using Stories reports.

A query on the Job Location and Job Location Short Format table in the Job Requisition table displays the job description's External Name and Code.

The enhancement helps you generate reports on the location data of the job requisition.

In the current version, the Job Location entity is available in Story reports to generate reports on job location data.

In the current version, the Job Location Short Format entity is available in Story reports to generate reports on job location short format data.

In the previous version, the Job Location and Job Location Short Format entities were unavailable in Story reports.

Email notifications of Ask for Feedback in Performance Management and Recruiting in Recruiting now use the customized single sender inAdmin Center → Manage Email Notifications.

When you've enabled and configured a customized single sender in Manage Email Notifications, email notifications in the following scenarios now use the customized single sender:

• During a performance review, when the manager uses the Ask for Feedback feature in Team Overview, people who are requested will receive an email with the customized single sender name and address.
• In Recruiting, all system email notifications now use the customized single sender.

This enhancement is from customer idea 42973.

A single job code can now be mapped to multiple job roles by creating a unique combination of the job code and a custom field, which can then be linked to specific job roles.

Job Profile Builder now allows you to associate a job code to a custom field. The combination of job code and custom field can then be mapped to a job role. The combination of job code and custom fields must always be unique before associating it with a job role.

The following example illustrates how a job code can be mapped to multiple job roles, by using a unique combination of custom fields.

In SAP SuccessFactors Recruiting, the integrations where you create job requisitions using Position from Position Org Chart or using Succession Org Chart or from OData API need configuration changes to determine the correct job role association with a job requisition when using one-to-multiple mapping of the job role to job code. For more information about the configuration changes, refer to the Associating Multiple Job Roles to a Job Code topic in the Related Information section.

This enhancement is based on the Customer Community Idea 47197.

The enhancement simplifies the work of administrators by not having to maintain different job codes for different job roles.

As an administrator, you can now manage access to the legacy candidate workbench using the Hide Legacy Workbench setting from Manage Recruiting Settings → Enable Latest Applicant Workbench.

Enabling the Hide Legacy Workbench setting will hide the New Applicant Management Experience switch within the redesigned Applicant Management tool.

We've implemented the new setting so that administrators can help their users fully adopt to the redesigned Applicant Management tool.

Historical results on Candidate Assessments and Screening Information are now available in the Detail View of the redesigned Applicant Management tool.

You can now use historical results to derive insights about the applicant by:

• Viewing the screening questions and responses from other jobs that the applicant has applied.
• Viewing the status, score and recommendation of the assessments that were initiated for other applied jobs applied, and decide if an assessment is needed for your current job requisition. You could also compare the results with the assessment made for your job requisition.

This feature helps recruiters make informed decisions based on a detailed understanding of an applicant's historical results in the Detail View of the redesigned Applicant Management tool. This feature is from a Customer Community Idea 311636.

How It Looks Like

In this version, the redesigned Applicant Management tool displays historical results for:

• Screening Questions in the Application Information → Screening Information → Applicant History tabs.
• Candidate Assessments in the Activity and Applicant History tabs.

In the previous version, historical results weren't available in the redesigned Applicant Management tool.

Onboarding Initiation Status is now available in the redesigned Applicant Management tool for applicants in a Job Requisition. You can choose to include Onboarding Initiation Status as a column to display and filter.

Onboarding Initiation Status shows the submission status and can have the following values:

• Success: First-time onboarding initiation is successful.
• Canceled: A user canceled the onboarding process in SAP SuccessFactors Onboarding. You can re-initiate onboarding by selecting Initiate Onboarding.
• Success (reinitiated): Re-initiation of the onboarding process, after it has been canceled, is successful. This status is displayed for any consecutive successful initiation, starting with the second one.
• Failed: If there’s a technical issue, the status appears as Failed. In this case, you can choose Initiate Onboarding to try again. In case this status keeps appearing, recheck the configuration.

We've implemented this enhancement in the redesigned Applicant Management tool so that Recruiters can get a quick snapshot of the applicant's onboarding initiation status.

In the redesigned Applicant Management tool, you can now download documents—Resume and Cover Letter, of up to 50 selected applicants. if more than two documents are selected, they will be downloaded as a ZIP file.

The selected documents are zipped and downloaded in the background, allowing you to continue with other tasks while the download proceeds eventually. Once the files are zipped, the ZIP file containing all the documents will be downloaded to your local device.

We've enhanced download capacity and improved the user experience by adding contextual message strips for document downloads, even when users multitask in the redesigned Applicant Management tool.

In SAP SuccessFactors systems that are integrated with OpenText for document management, we now support the display of offer letters generated by SAP SuccessFactors Recruiting in the OpenText workspace.

Currently, only new offer letters (generated after the 2H 2024 release) can be displayed. Previously generated offer letters aren't displayed.

We added this support because customers who use the OpenText integration expect all their documents to be available in OpenText.

We've enhanced the AI-assisted skills matching feature to let you view the total number of skills in an applicant's resume that match the skills specified as primary and secondary in the job description.

The following are the details of the enhancements:

• The skills identified are now categorized as Primary skills, Secondary skills, Relevant skills, and Unmatched skills.
• Recruiters can choose any skill listed on the Skill Compatibility page to determine whether the skill was part of the job description, extracted from the applicant's resume, or manually entered by the applicant during the application process.

This enhancement helps recruiters, and hiring managers utilize the skills compatibility insights to make informed decisions during applicant screening and hiring.

The applicant list view for the Skills Compatibility section categorizes skills as Job Skills and Other Applicant Skills.

• Job Skills: Lists the primary and secondary skills. Recruiters can manage and validate the job-specific skills for a job requisition using the Manage Skills option on the Job Profile or Job Requisition Details page (based on whether Job Profile Builder is enabled in your instance).

  The job skills section further categorizes skills as:

  • Primary Skills: Skills identified as a must for the job in a job description and are available in the applicant's skill set.
  • Secondary Skills: Skills that improve an applicant's ability to perform a specific job but aren’t required. An applicant also has skills besides the required skills relevant to the job.
• Other Applicant Skills: Lists relevant skills and unmatched skills from an applicant's resume. The relevant skills are additional skills of an applicant that are relevant for the job but not identified as the required skills. The relevant skills are from the applicant's resume or manually added by the applicant on the career site.

You can associate a job profile with a job requisition by providing the externalCode property of the jobRoleEntity entity in the JobRequisition OData API. The JobRequisition entity now has a navigation entity called jobRoleEntity, with the externalCode property that determines a job profile in a job requisition.

A GET query on the JobRole XML field in the JobRequisition entity now returns jobRole and jobRoleEntity entities to represent the job role data. We recommend using the jobRoleEntity entity for the POST query to update a job role on the job requisition.

A sample GET query and response are as follows:

12
<>Sample Code
https://qacand-api.hcm.ondemand.com/odata/v2/JobRequisition(32377L) $format=json&$select=jobReqId,jobRole,jobRoleEntity&$expand=jobRoleEntity

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120
<>Sample Code
{
    "d": {
        "__metadata": {
            "uri": "https://qacand-api.hcm.ondemand.com/odata/v2/JobRequisition(32377L)",
            "type": "SFOData.JobRequisition"
        },
        "jobReqId": "32377",
        "jobRole": "402002548",
        "jobRoleEntity": {
            "__metadata": {
                "uri": "https://qacand-api.hcm.ondemand.com/odata/v2/RoleEntity('1021659')",
                "type": "SFOData.RoleEntity"
            },
            "externalCode": "1021659",
            "lastModifiedDateTime": "/Date(1726824440000+0000)/",
            "name_localized": "ABAP Developer",
            "name_cs_CZ": null,
            "name_ko_KR": null,
            "createdDateTime": "/Date(1721793114000+0000)/",
            "name_th_TH": null,
            "name_cnr_ME": null,
            "name_fi_FI": null,
            "name_lt_LT": null,
            "name_sv_SE": null,
            "name_nl_NL": null,
            "mdfSystemRecordStatus": "N",
            "name_mk_MK": null,
            "name_ar_SA": null,
            "name_de_DE": null,
            "name_zh_TW": null,
            "subModule": null,
            "name_es_ES": null,
            "name_es_MX": null,
            "status": "A",
            "name_ru_RU": null,
            "name_pt_PT": null,
            "name_he_IL": null,
            "name_it_IT": null,
            "name_fr_FR": null,
            "name_en_DEBUG": null,
            "name_ja_JP": null,
            "name_de_CH": null,
            "name_uk_UA": null,
            "name_en_US": "ABAP Developer",
            "name_fr_CA": null,
            "name_zh_CN": null,
            "name_defaultValue": "ABAP Developer",
            "lastModifiedBy": "cgrant",
            "name_en_GB": null,
            "name_iw_IL": null,
            "name_vi_VN": null,
            "createdBy": "cgrant",
            "name_hu_HU": null,
            "createdLocale": "en_US",
            "family": "1021657",
            "name_en_RTL": null,
            "nameTranslationTextNav": {
                "__deferred": {
                    "uri": "https://qacand-api.hcm.ondemand.com/odata/v2/RoleEntity('1021659')/nameTranslationTextNav"
                }
            },
            "createdByNav": {
                "__deferred": {
                    "uri": "https://qacand-api.hcm.ondemand.com/odata/v2/RoleEntity('1021659')/createdByNav"
                }
            },
            "jobCodeMappings": {
                "__deferred": {
                    "uri": "https://qacand-api.hcm.ondemand.com/odata/v2/RoleEntity('1021659')/jobCodeMappings"
                }
            },
            "roleCompetencyMappings": {
                "__deferred": {
                    "uri": "https://qacand-api.hcm.ondemand.com/odata/v2/RoleEntity('1021659')/roleCompetencyMappings"
                }
            },
            "roleSkillMappings": {
                "__deferred": {
                    "uri": "https://qacand-api.hcm.ondemand.com/odata/v2/RoleEntity('1021659')/roleSkillMappings"
                }
            },
            "statusNav": {
                "__deferred": {
                    "uri": "https://qacand-api.hcm.ondemand.com/odata/v2/RoleEntity('1021659')/statusNav"
                }
            },
            "lastModifiedByNav": {
                "__deferred": {
                    "uri": "https://qacand-api.hcm.ondemand.com/odata/v2/RoleEntity('1021659')/lastModifiedByNav"
                }
            },
            "mdfSystemRecordStatusNav": {
                "__deferred": {
                    "uri": "https://qacand-api.hcm.ondemand.com/odata/v2/RoleEntity('1021659')/mdfSystemRecordStatusNav"
                }
            },
            "familyNav": {
                "__deferred": {
                    "uri": "https://qacand-api.hcm.ondemand.com/odata/v2/RoleEntity('1021659')/familyNav"
                }
            },
            "roleTalentPoolMappings": {
                "__deferred": {
                    "uri": "https://qacand-api.hcm.ondemand.com/odata/v2/RoleEntity('1021659')/roleTalentPoolMappings"
                }
            },
            "wfRequestNav": {
                "__deferred": {
                    "uri": "https://qacand-api.hcm.ondemand.com/odata/v2/RoleEntity('1021659')/wfRequestNav"
                }
            },
            "roleCompetencyBehaviorMappings": {
                "__deferred": {
                    "uri": "https://qacand-api.hcm.ondemand.com/odata/v2/RoleEntity('1021659')/roleCompetencyBehaviorMappings"
                }
            }
        }
    }
}

A sample POST query (when you map a job code with multiple job roles by providing jobRoleEntity and externalCode property) is as follows:

1234567891011121314
<>Sample Code
{
    "__metadata": {
        "uri": "JobRequisition",
        "type": "SFOData.JobRequisition"
    },
    "templateId": "80",
    "jobRoleEntity": {
        "__metadata": {
            "uri": "RoleEntity('1000435')",
            "type": "SFOData.RoleEntity"
        }
    },
    }

The new jobRoleEntity navigation property is introduced to support the Job Profile Builder enhancement to map a job code to multiple job roles in a job requisition. We added the externalCode property to the jobRoleEntity entity to associate the correct job profile with a job requisition without providing the Internal ID value.

Fetch location information from the Job Location generic objects defined in the job requisition template based on the job posting rules configured in the field completion rules.

The Job Location Generic object provides structured location data on the job requisition to facilitate faceted search using the Google Map component and posting a job to multiple locations for candidates to find on the job boards. It supports the Job Location Long Format attribute, an address representation per country/region format standards.

The enhancement provides granularity in configuring the job locations to post on job boards.

You can now use a new property, externalCode, in the JobreqFoLocation (location_objlist) and jobLocations (sfstd_jobLocaiton_objlist) object list to update the Location Foundation object and Job Location object data of a job requisition using Integration Center.

The additional property helps you update the location data of a job requisition using Integration Center.

The approval data for job requisitions is now reportable using Story reports. A query on the Job Requisition Approval Details table in the Job Requisition table displays the Approved Date and Approved By information for job requisitions.

The enhancement helps recruiters determine approval details for job requisitions, such as the approver's name, approval date, and time required to fill the positions.

Recruiters can use AI-assisted capabilities to extract skills from a job requisition to review and define the essential skills required for the job. They can then refine the list of required skills in the job description to identify candidates whose skills match the job requirements.

Recruiters can perform the following tasks to enhance the skills listed in the job requirements:

• Add, remove, and save skills in the job requisition to control the visibility of the skills listed in the job posting on the career site.
• Categorize primary and secondary skills to find candidates who best fit the job based on their skills matching the skills specified in the job requirements.

The enhancement lets recruiters categorize a job's critical skills to identify candidates whose skills align with the job requirements.