Routing Nodes

Routing nodes direct requests to the users who can review and respond to the submitted forms. You can direct the request to one or more users, roles, and authority types, as well as the request submitter, the affected employee, and the employee’s manager. You must route the request to at least one user.

The request is shown in the inbox of each of the recipients, and the workflow pauses until a decision is made or a timeout occurs. If you direct the decision request to more than one authorized person, the first person to make a decision triggers the next step in the process. Subsequent decisions by other recipients are ignored.

When Dayforce processes a Routing node and the routing options specified return no recipients, the workflow continues to the default workflow recipient. For example, multiple levels of decisions are configured in a workflow, with a Routing node associated at each level. When a node returns no recipients, the workflow progresses to the next decision level. If no default recipient is specified, it causes an error in the workflow.

Routing objects must have only one outgoing link, which must lead to a Decision object.

Note: If your organization uses Position Management, you can use only some types of routing nodes. See Use Workflows with Position Management.

Routing Node Properties

Note: If you are routing a form that creates a new employee, such as a New Hire form or a Rehire form, and you use any of the "Affected Employee" fields described in this section, the form's submitter is considered to be the affected employee. Forms are routed relative to the submitter's hierarchy and location.

Send To User

In the drop-down list, select the users to which Dayforce sends the decision request. The request is shown in the recipient’s inbox and the workflow pauses until a decision is made or a timeout occurs.

Send To Affected Employee

Select the checkbox and Dayforce sends the request to the affected employee. Clear the checkbox and Dayforce doesn’t send the request to the affected employee.

Send To Submitter

Select the checkbox and Dayforce sends the request to the user that submitted the request. Clear the checkbox and Dayforce doesn’t send the request to the submitter.

Send To Authority Type Relative to Affected Employee

In the drop-down list, select the authority types, relative to the affected employee, to which Dayforce sends the decision request. The request is shown in the recipient’s inbox and the workflow pauses until a decision is made or a timeout occurs.

You can select one or more of the available authority types: Manager, Performance Admin, and Approve Pay Rate Change. The application checks for users who have the selected authority types assigned for the onsite department of the affected employee’s work assignment. The application moves up the organizational hierarchy until it finds users with the selected authority types to send to. It stops moving up the hierarchy after users with at least one of the selected authority types are found. If there is more than one user with the selected authority types at the same level of the organizational hierarchy (for example two users with manager authority at the employee’s location), they each receive the notification.

Note: Users can be assigned authority types for locations in the Managed Locations section of the Work > Management Assignments screen of People.

For example, Kyle works at the Plant 1 packaging department, where there is no user with an authority type assigned. At the Plant 1 site that this department falls under, Dhanesh is assigned manager authority and Shelly is assigned performance admin authority. Moreover, Amanda is assigned both manager and performance admin authority in the Manufacturing Canada region that the Plant 1 site falls under.

In the node property, Dayforce is set to look for the manager or performance admin authority type. When Kyle submits a form, the decision is routed to Dhanesh and Shelly. Because these users are found at the Plant 1 site, Dayforce stops moving up the hierarchy, and Amanda does not receive the notification.

Send to Authority Type Relative to Affected Employee's Future Location

In the drop-down list, select the authority types, relative to the affected employee's future location, to which Dayforce sends the decision request. The request shows in the recipient’s inbox and the workflow pauses until they make a decision or a timeout occurs.

Note: The selection in this field is only applicable if the form associated with this workflow adds or changes an employee's primary work assignment.

For example, Chris works at the Plant 1 packaging department as an assistant shipping clerk. He’s promoted to senior shipping clerk at the Plant 2 location. You submit a Job Assignment and Compensation Change form for this primary work assignment update. The workflow for this form features a routing node that includes selections of Approve Pay Rate Change and Manager in the Send to Authority Type Relative to Affected Employee's Future Location field. The form is routed to the appropriate people at the Plant 2 location with those authority types.

Send To Role Relative to Affected Employee

In the drop-down list, select the roles, relative to the affected employee, to which Dayforce sends the decision request. The request is shown in the recipient’s inbox and the workflow pauses until a decision is made or a timeout occurs.

Dayforce checks for users who have the selected roles, either as a primary or secondary role, in the management hierarchy or organization hierarchy, depending on how the Search for Role Within Hierarchy property of the node is configured:

Management Hierarchy: Dayforce checks for a user who has the selected role and directly manages the affected employee and moves up the management hierarchy until it finds a manager with that role. It stops moving up the hierarchy after the appropriate user is found.
Note: Dayforce doesn’t route to users who manage the user by org.
For example, Alecia directly manages Alex, who directly manages Sam. Alecia has the Sales Manager role and Alex has the Assistant Manager role. In the node property, Dayforce is set to look for the Sales Manager role. When Sam submits a form, the workflow skips his direct manager, Alex, who doesn’t have the Sales Manager role, and routes the decision to his indirect manager, Alecia, who has the required role. Because a recipient is found for the selected role, Dayforce stops moving up the management hierarchy to look for more users.
This check is done separately for each role selected in the property. Continuing with the previous example, if you select both the Sales Manager and Assistant Manager role in the property, the notification is sent to both Alex and Alecia.
Organization Hierarchy: Dayforce checks for users who have the selected role and access to the onsite department of the affected employee’s work assignment. It moves up the hierarchy until it finds users with the select role who have the required location access. If more than one user has the same role at the same level of the organization hierarchy (for example two administrators at the region level), they each receive the notification.
Note: Dayforce checks location access that is configured in the Location Access tab of the Security Access section in the Security Settings screen of People. It doesn’t check whether the user manages the location, which is configured in the Managed Locations section of the Work > Management Assignments screen in People.
For example, an employee has a work assignment at the Plant 1 Packaging onsite department. A user with the Payroll Administrator role has access to Manufacturing Canada region location that Plant 1 falls under in the organizational hierarchy. Also, no other users with this role are assigned access to locations in the Manufacturing Canada region location.
In the node properties, Dayforce is set to look for the Payroll Administrator role. When the employee submits a form, the Routing node moves up the organizational hierarchy until it reaches the Manufacturing Canada region location and sends the notification to the user with the Payroll Administrator role. Because a recipient is found for the role, Dayforce stops moving up the hierarchy to find more users.
This check is done separately for each role selected in the property. Continuing with the previous example, say that you select the Payroll Administrator and HR Administrator roles in the property. Now, say that a user with the HR Administrator role is assigned access to the Plant 1 site. As a result, the payroll administrator and HR administrator users would each receive the notification.

For this property, Dayforce runs a check for each hierarchy selected in the Search for Role Within Hierarchy property of the node. For example, there are two users:

User A has a role of Manager and directly manages an employee.
User B has a role of Manager and has access to the Corporate location.

If the Search for Role Within Hierarchy property is set to check both hierarchies, each user receives the notification. User A receives it based on the manager hierarchy search while user B receives it based on the organization hierarchy search.

Send to Role Relative to Affected Employee's Future Location

In the drop-down list, select the roles, relative to the affected employee's future location, to which Dayforce sends the decision request. The request shows in the recipient’s inbox and the workflow pauses until they make a decision or a timeout occurs.

Note: The selection in this field is only applicable if the form associated with this workflow adds or changes an employee's primary work assignment.

For example, Wanda works at the Division 2 order fulfillment department as an associate quality assurance analyst. She’s promoted to manager of quality assurance at the Division 5 location. You submit a Job Assignment and Compensation Change form for this primary work assignment update. The workflow for this form features a routing node that includes selections of District Manager and HR Recruiter in the Send to Role Relative to Affected Employee's Future Location field. The form is routed to the appropriate resources at the Division 5 location with those roles.

Search for Role Within Hierarchy

When you select one or more roles in the Send To Role Relative to Affected Employee or Send To Role Relative to Submitter properties of the node, the Search For Role Within Hierarchy drop-down list lets you set which hierarchy it uses to search for those roles. The options are:

Both Management and Organization Hierarchy
Note: This option is selected by default.
Management Hierarchy
Organization Hierarchy

For more information on each hierarchy, see the description for the Send To Role Relative to Affected Employee and Send To Role Relative to Submitter properties.

Send To Affected Employee’s Manager

Select the checkbox and Dayforce sends the request to the affected employee’s manager. Clear the checkbox and Dayforce doesn’t send the request to the affected employee’s manager.

Relative Level of Affected Employee’s Manager

Type the level of management to which the form is routed, in relation to the affected employee. By default, this setting is set to 1 and the notification is sent to the affected employee’s direct manager if the Send to Affected Employee’s Manager checkbox is selected. Enter a different whole number to send the notification to that level of management. Negative numbers aren’t supported.

For example, Amanda reports to her manager, Troy, who in turn reports to his manager, Julie. Julie reports directly to the CEO, Brann. The associated workflow has the Send to Affected Employee’s Manager checkbox selected, and the Relative Level of Affected Employee’s Manager field has 2 entered. As a result, the notification is routed two levels above the affected employee, and Julie receives the notification.

Send To Authority Type Relative to Submitter

In the drop-down list, select the authority types, relative to the submitter, to which Dayforce sends the decision request. The request is shown in the recipient’s inbox and the workflow pauses until a decision is made or a timeout occurs.

You can select one or more of the available authority types: Manager, Performance Admin, and Approve Pay Rate Change. The application checks for users who have the selected authority types assigned for the onsite department of the submitter’s work assignment. The application moves up the organizational hierarchy until it finds users with the selected authority types to send to. It stops moving up the hierarchy after users with at least one of the selected authority types are found. If there is more than one user with the selected authority types at the same level of the organizational hierarchy (for example two users with manager authority at the employee’s location), they each receive the notification.

Note: Users can be assigned authority types for locations in the Managed Locations section of the Work > Management Assignments screen of People.

Send To Role Relative to Submitter

In the drop-down list, select the roles, relative to the submitter, to which Dayforce sends the decision request. The request is shown in the recipient’s inbox and the workflow pauses until a decision is made or a timeout occurs.

Management Hierarchy: Dayforce checks for a user who has the selected role and directly manages the submitter. It moves up the management hierarchy until it finds a manager with the selected role and sends the form to that user for approval. It looks only at direct managers, which are assigned in the Work > Management Assignments screen of People, in forms, or through the employee-manager import. This option doesn’t include managers from Position Management. If your organization uses Position Management, you should select the Organization Hierarchy option.
For example, Alecia directly manages Alex, who directly manages Sam. Alecia has the Sales Manager role and Alex has the Assistant Manager role. In the node property, Dayforce is set to look for the Sales Manager role. When Sam submits a form, the workflow skips his direct manager, Alex, who doesn’t have the Sales Manager role. It routes the decision to his indirect manager, Alecia, who has the required role. Because a recipient is found for the selected role, Dayforce stops moving up the management hierarchy to look for more users.
This check is performed separately for each role selected in the property. Continuing with the previous example, if you select both the Sales Manager and Assistant Manager role in the property, the notification is sent to both Alex and Alecia.
Organization Hierarchy: Dayforce checks for users who have the selected role and access to the onsite department of the affected employee’s work assignment. It moves up the hierarchy until it finds users with the select role who have the required location access. If more than one user has the same role at the same level of the organization hierarchy (for example two administrators at the region level), they each receive the notification.
Note: Dayforce checks location access that is configured in the Location Access tab of the Security Access section in the Security Settings screen of People. It doesn’t check whether the user manages the location, which is configured in the Managed Locations section of the Work > Management Assignments screen in People.
For example, an employee has a work assignment at the Plant 1 Packaging onsite department. A user with the Payroll Administrator role has access to Manufacturing Canada region location that Plant 1 falls under in the organizational hierarchy. Also, no other users with this role are assigned access to locations within the Manufacturing Canada region location.
In the node properties, Dayforce is set to look for the Payroll Administrator role. When the employee submits a form, the Routing node moves up the organizational hierarchy until it reaches the Manufacturing Canada region location and sends the notification to the user with the Payroll Administrator role. Because a recipient is found for the role, Dayforce stops moving up the hierarchy to find more users.
This check is done separately for each role selected in the property. Continuing with the previous example, say that you select the Payroll Administrator and HR Administrator roles in the property. Now, say that a user with the HR Administrator role is assigned access to the Plant 1 site. As a result, the payroll administrator and HR administrator users would each receive the notification.

For this property, Dayforce performs a separate check for each hierarchy selected in the Search for Role Within Hierarchy property of the node. For example, there are two users:

User A has a role of Manager and directly manages an employee.
User B has a role of Manager and has access to the Corporate location.

Send To Submitter’s Manager

Select the checkbox and Dayforce sends the request to the submitter’s manager. Clear the checkbox and Dayforce doesn’t send the request to the submitter’s manager.

Relative Level of Submitter’s Manager

Type the level of management to which the form is routed, in relation to the submitter. By default, this setting is set to 1 and the notification is sent to the affected employee’s direct manager if the Send to Affected Employee’s Manager checkbox is selected. Enter a different whole number to send the notification to that level of management. Negative numbers aren’t supported.

Send To Future Manager

Select this checkbox to send forms to an employee’s future manager for approval. If an employee is being hired, rehired, or transferred, forms are sent to the future manager specified in the form, even though that manager isn’t approved yet.

For example, you select this checkbox in a Routing node for a workflow that is used with the New Hire form. Sonia submits this form with Manjit selected as the new employee’s manager. Because the employee isn’t yet hired, Manjit isn’t yet the employee’s manager. However, because this checkbox is selected, the workflow sends the form to Manjit for approval.

The Send To Future Manager checkbox is applicable only if the form associated with the workflow adds or updates the employee’s primary work assignment. For example, it’s always applicable for new hire and rehire forms because these forms always create a new primary work assignment. As another example, it’s applicable when the Job Assignment and Compensation Change form is used to update an employee’s job assignment or location.

If the Employee reporting to multiple managers client property is enabled in System Admin > Client Properties in the Properties tab, and there is more than one org-level manager at the location of a new work assignment, all of the future org managers receive workflow decision notifications.

When a workflow reaches the Routing node, Dayforce looks for the future manager in the following priority:

The direct manager selected in the form.
If there is no direct manager selected in the form, Dayforce looks for a manager derived by org, based on the location selected in the form. The process for finding the org manager is similar to other node properties, as follows:
- If there is no org manager for the location selected in the form, Dayforce moves up the org hierarchy until it finds an org manager to send to.
- If your instance of Dayforce is configured to allow employees to have more than one manager, and a location has multiple org managers assigned, each of these managers receives the form.
- Dayforce looks for the org manager at the time that the Routing node is reached. As such, if the org manager changes after the form is submitted, Dayforce sends the form to the current org manager.

Note: The Send To Future Manager checkbox works independently of other Routing node properties. For example, the Relative Level of Affected Employee’s Manager field doesn’t affect it.

Relative Level of Affected Employee’s Future Manager

This setting is used together with the Send to Affected Employee’s Future Manager checkbox. It applies only to forms that update the employee’s primary work assignment.

Use this setting to send forms for approval to people in the management hierarchy of the employee’s future manager. For example, enter 2 in this field to send the form to the employee’s future manager’s manager.

By default, this option is set to 1 and the notification is sent to the affected employee’s future manager when you select the Send to Affected Employee’s Future Manager checkbox. Enter a different whole number to send the notification to another level of management. Negative numbers aren’t supported.

For example, you’re configuring a workflow for use with the Job Assignment and Compensation Change form. The form has two levels of approval: first, the employee’s future manager approves it, and then that person’s manager does so. The workflow needs to be configured with two Routing nodes with the Send to Affected Employee’s Future Manager checkbox selected. The first Routing node has 1 in the Relative Level of Affected Employee’s Future Manager field so that the form goes to the employee’s future manager for approval. The second node has 2 in the field to send the form to the manager’s manager for the second level of approval.

This setting works together with other Routing node settings. If this setting is configured along with Send To Submitter’s Manager, then both managers receive the form.

You can use this setting to send to only one type of manager. For example, if there’s a new direct manager selected in the form and you select 2 in this field, the form is sent to the direct manager’s manager. If there’s no new direct manager selected in the form and the employee’s manager is derived from the org, if you select 2 in the field, the form is sent to the org manager’s manager.

Use Form Effective Date For Routing

Select the checkbox and Dayforce routes the request to the manager that has authority as of the date of the change made on the form.

For example, Amanda reports to Troy, but will report to Julie after January 15. When you submit a Compensation Change form that increases her salary as of January 21 to be approved by her manager, the request is sent to Julie, and not to Troy.

Note: For Dayforce to route the request to a manager that has authority in the future, you must already have created the future-dated employee-manager assignment. You can’t create the future-dated manager record on the same request with a form that should be routed to that manager.

Send to Position’s Manager

Note: This property is used in workflows for Position Management.

Use this property for routing approval requests for changes in Organization Designer. Select the checkbox and Dayforce sends the request to the affected position’s manager. Clear the checkbox and Dayforce doesn’t send the request to the affected position’s manager.

Relative Level of Position’s Manager

Note: This property is used in workflows for Position Management.

Enter the level of management to which the approval request is routed, in relation to the affected position. By default, this setting is set to 1 and the notification is sent to the affected position’s managing position if the Send to Affected Position’s Manager checkbox is also selected. Enter a different whole number to send the notification to that level of management. Negative numbers aren’t supported.

For example, you want to a new Sales Associate position that reports to the Assistant Manager, who in turn reports to the Store Manager. The associated workflow has the Send to Affected Position’s Manager checkbox selected, and the Relative Level of Affected Position’s Manager field has 2 entered. As a result, the request is routed two levels above the affected position, and the employee who occupies the Store Manager position receives the notification.