Candidate Selection Workflow Priority

The candidate selection workflow priority ensures that the most appropriate workflow is displayed to the Recruiting Center user when they create a requisition.

The system can sort candidate selection workflows (CSW) according to the level of compatibility and ensure that the most appropriate workflow is displayed when a user is creating a requisition.

The system administrator must identify one CSW as the company default workflow. However, the default workflow will be preselected only if no other workflow is found to be compatible to the requisition or if other workflows are compatible because they are linked to all Organization, Location and Job Field (all-all-all).

The system automatically preselects the most compatible workflow as follows:

The system makes the sum of the differences between the levels specified in the workflow and in the requisition.
The workflow with the least differences is the one displayed in the Candidate Selection Workflow field.
In case of a tie, the sort is performed on the code of the workflows.

A workflow with no value (Null) for a dimension (Organization, Location or Job Field) will consequently be associated to all structure elements from that dimension. However, associating a workflow to no specific value (equivalent to all) will penalize its level of compatibility. Hence, a workflow tied to all-all-all will be much less pertinent than a workflow with the slightest specificity in its categorization.

Below are examples of workflow using these OLF values:

Organization: Food Processing/Food Production
Location: United States/California/Los Angeles
Job Field: Cashier

Workflow 1: There is no difference between the Organization-Location-Job Field information of this workflow and that of the requisition.

	Code	Organization	Location	Job Field
	CSW1	Food Processing/Food Production	United States/California/Los Angeles	Cashier
Difference		(0)	(0)	(0)

Workflow 2: Because there is no job field, the sum of the difference is 20.

	Code	Organization	Location	Job Field
	CSW2	Food Processing/Food Production	United States/California/Los Angeles	All
Difference		(0)	(0)	(20)

Workflow 3: There is a difference of one level in the Organization dimension, and a difference of two levels in the Location dimension, so the sum of the differences is 3.

	Code	Organization	Location	Job Field
	CSW3	Food Processing	United States	Cashier
Difference		(1)	(2)	(0)

Workflow 4: There is no difference between the Organization-Location-Job Field information of this workflow and that of the requisition.

	Code	Organization	Location	Job Field
	CSW4	Food Processing/Food Production	United States/California/Los Angeles	Cashier
Difference		(0)	(0)	(0)

Workflow 5: Since no dimension is specified in this workflow, the sum of the differences is 60.

	Code	Organization	Location	Job Field
	CSW5	All	All	All
Difference		(20)	(20)	(20)

Workflow 6: Once again, since no dimension is specified in this workflow, the sum of the differences is 60. However, this is the default workflow.

	Code	Organization	Location	Job Field
	CSW6	All	All	All
Difference		(20)	(20)	(20)

Workflow 7: The location of this workflow is not compatible with that of the requisition. This means that this workflow is excluded. In this example, the workflow that would be displayed in the Candidate Selection Workflow field is Workflow 4 (a_csw4), because even though Workflow 1 (z_csw1) and 4 are tied and have he lowest sum of differences, Workflow 4 will be displayed first when a sort is performed on the code.

	Code	Organization	Location	Job Field
	CSW7	Food Processing/Food Production	United States/California/San Jose	Cashier
Difference