Configure Standard Fields to Collect Diversity and Disability Information

Configure Standard Diversity and Disability Fields

You need to configure which standard diversity and disability fields to display to candidates in each of the countries where hiring is done.

Activate a sandbox and page editing at the Site layer in Settings and Actions Menu > Edit Pages > Activate a sandbox.
On your Home page, go to My Client Groups > Quick Actions > HCM Experience Design Studio.
Click the Transaction Design Studio tab.
Select the action Recruiting - Candidate Application Diversity and Disability.
Click Add to create and configure a rule to display certain fields for certain countries.
In the Basic Details section, enter the name, description, and any countries for which the rule applies.
In the Available Attributes section, select a data source.
Select which fields you want to make visible and which ones are required to be filled.
- Date of Birth: use the Personal Details data source
- Ethnicity: use the Ethnicity data source (this will display two fields for requisitions in the US)
- Gender: use the Demographic Info data source
- Marital Status: use the Demographic Info data source
- Religion: use the Religion data source
- Disability Status, Category, Reason, and Reasonable Accommodation: use the Disability Info data source.
Click Save and Close.

If a job requisition is posted in any United States location and if its Diversity block is configured to display the single field Ethnicity, candidates will see two ethnicity-related questions. First a check box asks if the candidate considers themselves to be Hispanic or Latino, and then another set of five check boxes invites them to select the race or races that they identify with. This method of displaying the Ethnicity field is consistent with the employee self-service page that they will see if and when they reach the end of the recruiting process successfully. After this candidate is hired, their ethnicity responses and any other diversity values that they provided in the job application will become visible in their personal information as a worker.

Note: In the United States, it's not correct to configure the ethnicity to be required for candidates to answer. If a candidate doesn't fill in either of the two ethnicity questions, you should report the race and ethnicity for this candidate as "Not Available" or "Do not want to disclose", in whichever way you're currently reporting this value for candidates.

When collecting disability information for hiring in the United States, you should only configure a single disability-related field to be visible for that country. US regulations require that federal contractors must show candidates the form CC-305, Voluntary Self-Identification of Disability. The field Disability Status is the only field which belongs inside that form, and it can't be displayed as a required field. Furthermore, the form's format can't be changed. If you configure additional disability fields to appear for candidate applications within the US, they will all be displayed inside this form when the block is displayed in the application flow. This would disturb the form's layout, making it no longer conform to the regulations.

Review Lookup Values for Standard Diversity and Disability Fields

You can verify that the lookup values for the standard diversity and disability fields are correct for each country. This step is optional. These lookups are configured in the Setup and Maintenance work area, using the tasks Manage Common Lookups and Manage Person Lookups.

In Manage Common Lookups:

DISABILITY_CATEGORY
DISABILITY_REASON
DISABILITY_STATUS
ORA_PER_SELF_DISCLOSE_DISABILITY
ORA_PER_DISABILITY_COUNTRY

In Manage Person Lookups:

PER_ETHNICITY
PER_RELIGION
MAR_STATUS

Configure the Job Application Flow

You need to decide which blocks to add to the job application flow and where the blocks should be placed in the flow.

On the job application flow creation page, configure which blocks to display.

Diversity: This block shows any of the standard diversity fields, and any of the person legislative flexfields that are delivered by Oracle (PER_PERSON_LEGISLATIVE_DATA_LEG_DDF), and any of your customer-defined legislative flexfields (PER_PERSON_LEGISLATIVE_DFF) for job requisitions with locations in any country.
Disability: This block shows any disability-related fields for any country, and also shows the U.S. disability form CC-305 for job requisitions located in the United States.
Veteran: This block shows the US veteran status field for job requisitions located in the United States.

You can add instructions to the blocks to provide specific information to candidates. For example, you may want to indicate that answers are optional, they're confidential, and the recruiting team won't be able to view the answers. Also you may want to ensure that instructions for the Veteran block give the definition of all categories of protected veteran, because candidates aren't asked to self-identify their specific category while applying for jobs. Here in the pre-offer time frame, candidates are merely asked a single question, to disclose whether or not they fall into any category of protected veteran.

Recruiters can now use the newly-activated application flows within requisitions to start gathering this legislative and diversity information from external candidates. Anytime a job requisition is using a job application flow that contains the Disability and Diversity blocks, if that requisition is hiring for a city, state, or level within the relevant country locations, then these fields and the block instructions will appear. Anytime a job requisition is using a job application flow that contains the Veteran block, if that requisition is hiring for a city, state, or level within the US, then this field and its block instructions will appear. Candidate responses are always confidential, not visible to the Hiring Team who manages the job applications, only accessible through reporting.