1. Implementing Recruiting
  2. Configuring List Formats

Configuring List Formats

The configuration of a list format consists of the following steps.

  1. Configuring fields so they can be used as column headers in a list.

  2. Creating the list format.

  3. Displaying advanced filters in the list.

  4. Displaying quick filters in the list.

  5. Creating custom instructions for the list format context.

  6. Assigning a list format variation to configuration profiles.

Note: Be aware of the following specific field visibility behavior in candidate lists. Fields can be made visible for internal or external candidates (via the candidate security level permissions) and fields can be contextualized to appear only for certain Organizations-Locations-Job Fields or staffing types circumstances. As a result:

  • When a field was not made visible to the user for both internal and external candidates, the column will appear but data will be blank for situations where the user should not see the data.

  • When a field was made visible to the user for either internal or external candidates, the column will appear but data will be blank for situations where the user should not see the data.

  • When a field was made visible and available (active) to the user but was not used in the candidate file, data will be displayed if it exists. (This may happen if the field was supplied on another submission where the field is present).

  • When a field is not present on the file because it was not configured for display in a specific context (Organizations-Locations-Job Fields or staffing types), data will be displayed if it exists. (This may happen if the field was supplied on another submission where the field is present.)

Note: If compensation data is hidden from certain user types, it is important not to allow these fields to be available in the requisition list view context for these user types. If compensation fields are present in a list view, the data will appear to the user regardless of compensation data viewing permissions. It is possible to hide these fields from select user populations only by using the list format "variation" concept that is applied to a user's configuration profile.