End Nodes

The End node is the end of the workflow process. A workflow should have only one End node, which should have at least one incoming link from one or more Decision, Notification, Condition, or Process nodes. End nodes can’t have any outgoing links leading to other nodes.

While a workflow can include more than one End node, it’s a best practice for the workflow to include only one.

End nodes mark the completion of the workflow process. They can be configured to send an error message to the appropriate users if the workflow isn’t successfully run to completion.

End Node Properties

Message Subject

Click Create Expression and enter the subject line of the message Dayforce sends when an error prevents the normal completion of the workflow. Enter any text that you want to include in the subject line of the message. To include variables from the tree on the left, find the appropriate token and double-click it. See the Workflow Tokens Guide.

Send Error To User

In the drop-down list, select the users to whom Dayforce sends the error message if the workflow is unable to run to completion.

Send Error To Affected Employee

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

Send Error To Submitter

Select the checkbox and Dayforce sends the error message to the user that submitted the form. Clear the checkbox and Dayforce doesn’t send the error message to the user that submitted the form.

Send Error 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 error message if the workflow is unable to run to completion.

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 Error To Role Relative to Affected Employee

In the drop-down list, select the roles, relative to the affected employee, to which Dayforce sends the error message if the workflow is unable to run to completion.

The application checks for users who have the selected roles, either as a primary or secondary role, within the following hierarchies:

Management Hierarchy: The application 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: The application 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 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: The application 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 there is more than one user with 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: The application 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. Moreover, there are no other users with this role who 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 performed 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 per hierarchy, and you cannot set it to only check one hierarchy. 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.

In this case, both users would receive the notification. User A receives it based on the manager hierarchy search while user B receives it based on the organization hierarchy search.

Send Error To Affected Employee’s Manager

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

Relative Level of Affected Employee’s Manager

Enter the numeric level of management to which the notification is sent, 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 allowed.

For example, Amanda reports to her manager, Troy, who in turn reports to his manager, Brent. Brent 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 Brent receives the notification.

Send Error To Authority Type Relative to Submitter

In the drop-down list, select the authority types, relative to the submitter, to which Dayforce sends the error message if the workflow is unable to run to completion.

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 Error To Role Relative to Submitter

Sets which users receive an error message if the workflow is unable to run to completion.

The application checks for users who have the selected roles, either as a primary or secondary role, within the following hierarchies:

Management Hierarchy: The application checks for a user who has the selected role and directly manages the submitter 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: The application 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 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: The application checks for users who have the selected role and access to the onsite department of the submitter’s work assignment. It moves up the hierarchy until it finds users with the select role who have the required location access. If there is more than one user with 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: The application 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. Moreover, there are no other users with this role who 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 performed 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 per hierarchy, and you cannot set it to only check one hierarchy. 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.

In this case, both users would receive the notification. User A receives it based on the manager hierarchy search while user B receives it based on the organization hierarchy search.

Send Error To Submitter’s Manager

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

Relative Level of Submitter’s Manager

Enter the level of management to which the error message 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.

Use Form Effective Date For Routing

When this checkbox is selected, Dayforce determines the users to whom the notification is routed based on the effective date of the form.

For example, a workflow is configured so that the notification is sent to the affected employee’s manager. The employee is working under Danny, and there is a future-dated manager record so that they will be working under Andy starting on December 15. If a form is submitted on November 11 with an effective date of December 16, and the Use Form Effective Date for Routing checkbox is selected, Dayforce sends the notification to Andy rather than Danny.