In Recruitment Marketing (RM), you can create custom candidate fields mapped to your ATS Integration, CSV Import, or Apply questions that can be used for custom filters. Custom fields can be configured to be shown within the Other Fields tab on the candidate profile. If you are using the Internal Mobility app in Source can set up your custom fields to be used specifically for Internal Mobility reporting.
Audience
Company Administrators
Create Custom Field
Navigate to your user menu, then click Applications.
Select Source > Fields & Filters > Custom Fields.
The Custom Fields page is displayed.
Click New Field.
Select the field type that best suits the field you need to create.
The following examples show the different field types:
- Text Field - Field type will be a free-form string.
- List Field - The list field type can be set up as a Single-value or Multi-value field. This setup will allow the correct configuration of the field in edit mode. Existing Apply Questions/Answers fields will preserve the corresponding setup for that question in Apply. New fields, both ATS and Apply Questions/Answers, are created as Single-value by default. The setting can be changed on the field setup. NOTE: If your ATS integrator sends multiple instances of the same custom field (with the same or different values), the best practice is to make this field multi-value in RM. Otherwise, only the first value will be saved for the candidate. See Configure Values for List Type Fields for additional information.
Date Field - Field type will be a specific date or a date range.
- Numeric Field - Field type will allow numeric strings >=0.
- Consent Field - Field type for working with data related to the candidate's consent.
- Boolean Field - Field type allows easy mapping to yes/no questions.
Fill out the following information (where applicable) for the custom field type you selected:
-
Show on Profile - All custom field types have this toggle. When enabled, the custom field will be displayed under the Other Fields tab on the candidate profile. NOTE: If Show on Profile is turned off for Apply Custom Fields, they will not appear on the Other Fields tab, but will still be shown on the Profiles and Overview tabs (this view is controlled by the setting on that Question in Apply).
Allow Edit on Profile - If Show on Profile is enabled, the Allow Edit on Profile toggle becomes clickable. Enabling this allows the custom field to be editable from the Other Fields tab on the candidate profile.
Display Name - The name will be used to show this field on the profile, and to configure the corresponding filter.
HRXML Node of CSV Header - If you need to map this field to your ATS Integration, enter the HRXML node where you are mapping this field. The same label will be used as a column header in the Candidate CSV that can be imported into RM. NOTE: RM supports "one-to-one" and "one-to-many" ATS to RM consent fields mapping (you can map one ATS Consent field to several consent types in RM). Leave this field blank if you need to map your field to an Apply Question.
Workflow Question ID - If your new field has to be mapped to an Apply Question, enter the Question ID. Leave this field blank if you are mapping the new fields to your ATS Integration. NOTE: This field is case sensitive as it was defined in the Apply Workflow Questions. Failure to match the case will mean that the field will not be populated.
Numeric Mask (only on Numeric Type field) - When you create a numeric type field, you need to specify the format of the numbers used in your new field. The default numeric mask is 6.2 (six digits before the decimal point and two digits after it). You can edit the mask depending on your needs.
HRXML Node of Consent Date (only on Consent Type fields) - If your ATS provides the date of the consent change, enter the HRXML node of the consent date field where you want to map this field. The date field is optional. If no date is provided, consent is saved with the date when the candidate was created.
-
Consent Type (only on Consent Type fields) - This is one of several ways to collect candidates' consent. Other ways include Apply Workflow, Candidate Portal, or direct SMS subscription. The candidate's master consent value is using the latest consent value obtained through any of these ways. For example, if a candidate with an existing email consent custom field value "no" applies for a job and provides consent to receive emails (the most recent consent), their master email consent will be set to "yes", but the value of the email consent custom field will remain as "no". Select one of the available consent types:
SMS - Consent to be contacted via SMS.
Email - Consent to be contacted via email.
Applied Jobs - Consent to be contacted with relation to the jobs the candidate applied to.
Other Jobs - Consent to be contacted with relation to any other jobs.
Processing - Consent on processing the candidate's data.
Consent Given (true) (only on Consent Type fields) - Enter the value that stands for "consent given" in your ATS or Apply question.
Consent Not Given (false) (only on Consent Type fields) - Enter the value that stands for "consent rejected" in your ATS or Apply question.
NOTE: The Unconfirmed consent status cannot be removed with the manual update on the profile. For example, even if "Yes" is saved manually on the profile, the Consent will still be Unconfirmed until the candidate confirms it properly through MyPortal, SMS, or Apply.
Once you have finished configuring your custom field, click Save to create the field. NOTE: To discard your changes and return to the list of Custom fields, click Cancel.
The new field is now displayed on the list of custom fields and is available to be selected for a new custom filter. See Custom Filters for more information.
Edit Custom Field
Once your custom field has been created, you can edit any defined setting on it; however, you CANNOT change the field mapping from HRXML to Apply Question.
On the Custom Fields page, locate the field you want to modify and click Edit.
Edit the field as needed.
Click Update.
Delete Custom Field
You can only delete custom fields that are not used in custom filters. Once the custom filter is created, the Delete option is removed for the related custom field.
On the Custom Fields page, locate the field you want to delete and click Delete.
On the confirmation pop-up, click Yes.
Configure Values for List Type Fields
The values for your list type field can be added via API or manually on the Custom Fields page.
On the Custom Fields page, locate the field you need to configure and click List Values.
On the List Values page, fill out the following fields:
Name - Enter the name that will be shown for this value on candidates and in the filter.
Code - Enter the code that will be passed on Candidate XML for that value. The code is case sensitive, and commas are not allowed. The recommended formats are "word1word2" or "word1_word2".
Click ADD to add your value to the list.
NOTE: When you create a list type field based on an Apply Workflow question, make sure to use the Answer ID from the question setup as the code for your list item. For example:
Edit List Value Display Name
To change the display name, from the Custom Fields page, click List Values.
Click Rename.
Update the display name and click Save.
Archive List Values
You can archive the values they no longer need. Once archived, the value will not appear on the filter, on the candidate profile, or in the action menus.
To change the display name, from the Custom Fields page, click List Values.
Click Archive.
The list value is archived.
Special Case
Two fields are created by default for each account: DispositionStatusCode and DispositionReasonSearch. They are ATS fields with a default location under RelatedPositionPostings node in Candidate XML. A common way to set up these fields is to sync values from ATS, though they can also be added via UI. If the ATS integration has such a sync implemented, it will use the default field name and overwrite any manual updates made to the values of this field. If you want to maintain the list of values for these two fields manually should change the field name; otherwise, it would be overwritten by the ATS integration.
Internal Mobility Customers
If you are using the Internal Mobility app in Source, you will see an additional toggle when creating or editing your custom fields: Use for Internal Mobility.
Users without Internal Mobility privileges will not see custom fields that have Use for Internal Mobility enabled in the following areas:
Other Fields tab on the candidate profile
Downloaded candidates CSV