Symptom
- If I use a 'derived' type for the "country" field definition and template type "job-req" in the Offer Detail template the country is not populating;
e.g.:
<field-definition id="country" type="derived" required="true" custom="false" template-type="job-req" anonymize="false"> |
- If I use an 'enum' type for the "country" field definition and template type "job-req" in the Offer Detail template the country populates with the two characted country code, but disappears when the Offer is sent for approval;
e.g.:
<field-definition id="country" type="enum" required="true" custom="false" template-type="job-req" anonymize="false"> |
Environment
SuccessFactors Recruiting Management (RCM) - All versions
Cause
The country is not supported as derived field
Resolution
In order to define country in the Offer Detail template populating information from the standard country field in the Job requisition and ensure no functionality loss, you have to define "country" with the "picklist" type in the Offer Detail template (the country in the job requisition template has to remain a "derived" field type).
An example of a correct configuration in the Offer Detail template:
<field-definition id="country" type="picklist" required="true" custom="false" template-type="job-req" anonymize="false"> |
Note: If the derived country field is being used then the ISO code will also appear in the offer letter.
See Also
2345268 - Offer Detail - Implementation Tips & Tricks from Support - Recruiting Management
Keywords
KBA , LOD-SF-RCM , Recruiting Management , Problem