3453523 - Support for Object Type in Job Application Template - Recruiting Management

Information regarding Foundation Objects and Generic Objects fields in the Job Application template.

SAP SuccessFactors Recruiting Management

As part of this feature, effective-dated Foundation Objects and Generic Objects can now be included in the Job Application template.

User Assistance Documents

• Foundation Objects and Generic Objects for Job Applications
• Effective-Dated Foundation Objects and Generic Objects for Job Application
• Foundation Object and Generic Object Fields in Ad Hoc Reports for Job Applications
• OData Operation for Job Application

Quick Facts and Known Limitations

User Interface:

1. Objects configured on the Job Application template are only supported on the Latest Applicant Workbench.
2. Objects configured on the Job Application template are not visible to internal and external candidates.
3. Objects configured on the Job Application template only allow single value selection.
4. The system does not show Quick Card for objects on the Job Application page.

Job Application template:

1. Job Application template only accepts objects to be configured as Custom fields, even when using the system standard objects, e.g. legalEntity. As of now, there is no standard object Field ID in the Job Application template.
2. The multiselect attribute is not supported for Job Application Object fields. (Error message: Attribute "multiselect" must be declared for element type "field-definition.)

Role-Based Permissions (RBP) for MDF:

1. For Recruiting operators, the system honors RPB permissions to control the visibility of object values on the Job Application page. (See KBA 2816435 - RBP permissions for MDF Object)

Effective-dated Foundation Objects and Generic Objects:

1. Recruiting operators can view and select effective-dated object values based on Job Application startDate (or Job Requisition jobStartDate) if enabled "Allow users to select only those instances that are active as of the date in the Job Start Date field in the Job Requisition, Application and Offer Detail pages." in Manage Recruiting Settings.
   
   Order of precedence should be:
   • Job Application startDate.
   • If empty, Job Requisition jobStartDate.
   • If empty, the current date.
     
     

Synchronization between Job Requisition, Candidate Profile and Offer Detail:

1. Job Requisition: Object values in the Job Requisition will not flow into the same object in the Job Application by default. You can use business rules to auto-populate data from the Job Requisition into the Job Application object field.
   
   
2. Candidate Profile: The synchronization between Job Application and Candidate Profile is similar to other Job Application fields on the Latest Applicant Workbench.
   
   
   1. When Candidate applies, if the same object field id has been defined in both Job Application template and Candidate Profile template,
      • (1) The field value will be synced from Candidate Profile to Job Application.
      • (2) The fields are displayed within the Application Information portlet.
        
        
   2. When Recruiter updates object fields in the Application Information portlet, the field value will not be synced from Job Application to Candidate Profile since they are not snapshot fields.
      **Snapshot fields are displayed in the Profile Information portlet. Those fields are defined in Candidate Profile template only.
      
      
3. Offer Detail: Values in Job Application object flow into Offer Detail if the object field id is referenced in the Offer Detail template.
   
   

OData API:

1. Please use the 'externalCode' property (or 'code' depending on the object definition) to insert/upsert Job Application object fields.
2. Integration Center doesn't support updating Job Application object fields. It returns a successful response but fields will not be updated.
   Note: Currently it is not possible to update Job Application object fields using the 'effectiveStartDate' business key. It returns a successful response but fields will not be updated.

Sample Request:

{
"__metadata":{
"type":"SFOData.JobApplication",
"uri":"JobApplication"
},
"applicationId": "1234",
"object_field_id":  {"externalCode":"xyz"}
}

Not Supported:

        "field_id": {
          "__metadata": {
            "type": "SFOData.FODepartment",
            "uri": "FODepartment(externalCode='xyz',startDate=datetime'1900-01-01T00:00:00')"
          }
 }

Reporting:

1. Ad Hoc Report: When the option "Allow users to select only those instances that are active as of the date in the Job Start Date field in the Job Requisition, Application and Offer Detail pages." is enabled, it always displays the most future version (active or inactive) of the value. When the option is disabled, the value is as of the current system date. (See KBA 2888727 - Adhoc report is showing wrong label for object division - Recruiting Management)
   
   
2. SAC Report: Similar to Job Requisition objects, by default, all the standard MDF objects are available for reporting in Story reports. The custom MDF objects are also reportable by default, but they appear in the Available Data section of the Query Designer page, only after you associate them with one or more schemas. For more information, please see Configuring Custom MDF Objects for Reportability Using Story Reports.

RCM, Job Application, Object, MDF, start date, Foundation Object, Generic Object, UXR, Permission, Reporting, View, Edit , KBA , LOD-SF-RCM-APP , Applicants and Job Applications , How To