Defaulting values for requisitions and job applications

A requisition must be associated with a position. A position is always associated with a job.

Job and positions have default rules set for specific fields at the organization level. These default rules determine how these job and position fields are set for requisitions. For these fields, the following rules apply:

  • If the default rule on a job or position field is set to "Default No Override" that field is set and cannot be overridden on the requisition, the job application, the job offer, or any of the hire/rehire/transfer/add work assignments actions. If the field has a value, the value is kept. If the field does not have a value, it cannot be assigned a value.

  • If the default rule on a job or position field is set to "No Default" or "Default With Override" and there is no value in the field, the field can be assigned a value on the job requisition, which will default to the job application where it can be changed on the offer and possibly on the hire, rehire transfer, or add work assignment actions (although, they would normally match the offer).

  • If the default rule on a job or position field is set to "Default With Override" and there is a value in the field, that value defaults on the job requisition, where it can be changed. The requisition value then defaults on the job application record where it can be changed on the offer and possibly on the hire, rehire transfer, or add work assignment actions (although, they would normally match the offer).

  • If the default rule on a job or position field is set to "No Default" but a value exists for the field in the organization unit's work assignment defaults, then that value is set on the job requisition, where it can be changed. The requisition value is set on the job application record where it can be changed on the offer and possibly on the hire, rehire transfer, or add work assignment actions (although, they would normally match the offer).

For fields that do not have default job or position rules:

  • If the field exists on the job requisition and has a value, then the value is set on the job application where it can be changed. Any change to the job application is shown on the hire, rehire transfer, or add work assignment action, where it can be changed.

  • If the field does not exist on the requisition, then the most recent value entered on the job application is set on the hire, rehire transfer, or add work assignment action, where it could be changed (although, it would normally match the approved offer).

  • If an employment contract is defined and approved as part of the offer process, then the employment contract data is shown on the hire, rehire, transfer, or add work assignment actions, but it cannot be changed.

Other considerations with defaults

  • For the job description that appears on the requisition, the job posting template selected for the requisition determines whether the description text is pulled from the job, from the position, or from both. Job posting templates

  • The recruiter administrator can configure an assessment vendor package, a self identification, a question set, an external consent agreement, an internal consent agreement, an external acknowledgment, or an internal acknowledgment to be shown on all new requisitions. Recruiters and hiring managers can change those values when they create a requisition.