SuccessFactors BizX - Recruiting Management(RCM)
As part of 1702/1705 the Offer Detail was enhanced to support GO/FO fields. This was in continuation with supporting GO/FO fields on the Job Requisition earlier.
In the Offer detail template it would be possible to define standard GO/FO fields as well as custom fields.
The 6 standard GO/FO fields are
- Legal Entity (Company) --> name of standard field
- Business Unit
- Cost Center
To Set up GO/FO fields the first change that would need to done is to the Offer detail template.
Offer Detail Template
A GO/FO field type can be defined on the Offer Detail template using the following tags
- object-type="<name of the GO/FO>"
A GO/FO field can ONLY be defined in two scenarios
- Its template-type = "job-req" --> meaning the field is derived from the Job Requisition where is was defined as a GO/FO field.
- The field is a stand alone field (defined in the Offer Detail template with the tag custom="true" - it is neither defined on the job requisition template nor the job application template).
Note: As the Job Application does not currently support GO/FO fields, it would not be possible to define a GO/FO field in the Offer Detail with template-type="job-application"
Example of how to define the standard department GO field which derives its value from the Job Requisition.
<field-definition id="department_obj" type="object" object-type="Department" required="true" custom="false" template-type="job-req" anonymize="false">
A standalone GO/FO can be defined by leaving the template-type blank similar to any other stand alone field on the Offer Detail template.
Iit would not be possible to provide write permission to the standard GO fields ( Legal Entity, Business Unit, Division, Department and Cost Center) with write permission. However the standard Location FO field can have write permission.
Custom fields derived from the Job Requisition can have write permission if they are marked as Custom Reportable Fields in provisioning from the page 'Configure Reportable Custom Fields'.
Stand alone Offer fields can however have write permission if defined in the template.
Field Criteria definition
The field criteria cannot be defined in the Offer Detail template for a field that is derived from the Job Requisition. If all the fields in the hierarchy are defined in the Offer Detail template the field criteria would be derived from the Job Requisition template. Additionally for a hierarchy of fields (more than 2 levels of hierarchy eg, legal entity --> business unit --> division) with field criteria, all the fields in the hierarchy would need to be defined in the Offer Detail template for field criteria to apply. If any intermediate fields in the hierarchy are skipped from being defined, then the field criteria would not apply.
Again as per the existing behavior the labels for all the fields are read from the Offer Detail template.
Note: Labels for 6 standard GO/FO fields are NOT read from the Succession Data Model as in the case of Job Requisition.
Offer Approval List Page
In the Offer Approval page a new column was added for the standard Location FO field. This column would be used if the standard Location FO field was defined in the Offer Detail template.
Note: A new switch was introduced in Admin to allow the customer to hide the existing Location field (non FO). The details of the switch are mentioned below
Admin --> Manage Recruiting Settings --> Offer Approval --> Disable Location On Offer Approval Summary Page
GO/FO fields in the Offer GO/FO fields , KBA , LOD-SF-RCM-CAN , General Candidate Issues (not Offers, not Profiles) , Product Enhancement