Enable Access to Job Requisition Forms in Recruiting

You can enable access to one or more Job Requisition forms in the Recruiting module. This allows you to create a workflow-enabled Job Requisition from the Recruiting module, rather than in the People feature.

See Submit Job Requisition Forms in Recruiting.

Important: Recruiting doesn't support the use of employee properties in Job Requisition forms.

To enable Job Requisition forms in Recruiting:

1. Enable the Job Requisition form for use in the Recruiting module:
   1. Go to the form in Workflow Administration > Form Builder and then click the Advanced tab.
   2. In the Xml Form Type field, enter JobRequisitionForm.
   3. Note: To edit the Xml Form Type field, your user role must be assigned Advanced Form Properties access in the Authorizations tab of System Admin > Roles.
   3. Click Save.
2. Add the form to a workflow:
   1. Go to Workflow Administration > Role Privileges and click Add.
   2. Do the following in each column:
      • Parent Feature: Select Job Requisition Job Requisition Forms.
      • Form: Select the form that you enabled in step 1.
      • Workflow: Select the workflow that you want to associate with the form.
   3. Note: For information about configuring Job Requisition form workflows, see Job Requisition Workflows.
   3. Click Save.
3. Assign access to the form in the Recruiting feature:
   1. Go to System Admin > Roles and click the Features tab.
   2. (Optional) Enable access to the New drop-down list in Recruiting > Job Requisitions by enabling the Job Requisition Forms subfeature under Recruiting > Recruiting > Job Requisitions.
   3. Under the Job Requisition Forms sub-feature, select the checkbox next to the Job Requisition form that you want to display.
   4. Click Save.
4. Note: When you add a new form in Role Privileges, it's automatically added as a sub-feature under Job Requisition Forms in the Features tab of System Admin > Roles. If the Job Requisition Forms feature is already enabled for users with the assigned role privileges, the checkbox for the newly added form is selected by default. You can clear the checkbox for specific roles to exclude the form for those users in Recruiting > Job Requisitions.

Job Requisition Workflows

Before You Begin: In Workflow Administration > Workflow Designer, Dayforce displays a system default Job Requisition Workflow that you can use as a template when configuring new custom workflows. This workflow is configured only for job requisition forms and shouldn't be associated with any other workflow form in Recruiting.

In Workflow Administration > Workflow Designer, you can configure custom workflows for Job Requisition forms. These workflows require the use of Process nodes to ensure that the requisition is added to the requisition list in Recruiting, and that the status is updated correctly when the form is pending, approved, or rejected.

These Process nodes use the Function Parameters field in the Node Properties to define their function in the workflow. This field is displayed as a drop-down list from which you can select Approved, None, Presave, or Rejected to define the function.

In Job Requisition workflows, the Approved, Presave, and Rejected parameters function as follows:

• Approved: If the workflow form is approved, the process node updates the job requisition record with any information that was changed during the approval process and updates the status to Open.
• Presave: The process node adds the requisition to the job requisitions list with the Pending Approval status.
• Note: The Presave function is used only in Job Requisition Workflows (that is, it shouldn't be used in workflows associated with other forms, such as the Candidate Hire form).
• Rejected: If the workflow form is rejected, the process node updates the status of the job requisition to Rejected.

Note: Process nodes with the None function aren't required in Job Requisition workflow configuration.

All workflows that were created prior to Release 54 of Dayforce are automatically copied and updated as follows when you update:

• A “Pre-Save” Process node is added after the Start node.
• An “Approved” Process node and a “Rejected” Process node are added after the Decision node.