Decision nodes are points in the workflow at which a decision is required. The outcome of the decision determines the next step in the workflow process. Users are sent a message and prompted to respond, usually by accepting or rejecting the changes contained in a submitted form.
Decision nodes can have only one incoming link, which must be from a Routing object. They can have outgoing links to two or more nodes. Each outgoing response leads to a different node that determines the consequence of the response. For example, a Rejected response sends a rejection message to the affected employee. The response option is configured in the properties of the arrow link leading to the subsequent node. See Input or Output Links.
Decision Node Properties
Message Subject
Click Create Expression and enter the subject line of the message Dayforce sends prompting users for a decision. 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 Compose Workflow Messages.
Message Body
Click Create Expression and enter the body of the message Dayforce sends when a decision is requested. Enter any text that you want to include in the body of the message. To include variables from the tree on the left, find the appropriate token and double-click it. You can click Cut, Copy, and Paste to update existing text, or edit the font face, size, color, and style using the text editing controls.
See Compose Workflow Messages.
Associated Form
In this drop-down list, select the form that Dayforce sends with the approval request. This property is used only if a different form should be sent with the message. Leave this property cleared and Dayforce sends the form that’s associated with the workflow in Workflow Administration > Role Privileges.
Note: Selecting a value overrides the selection in the Role Privileges screen. The form associated with the workflow is ignored for this node if you select a value for the property.
When you configure a workflow that needs a single level of approval, and contains only one Decision node, you would usually associate a form only with the Decision node that has fields in common with the form that initiated the workflow. Dayforce automatically populates the common fields with the information submitted on the form that initiated the workflow.
For example, a manager submits a request to update an employee’s job assignment in the Job Assignment Change form, but the manager doesn’t have the Job Assignment and Compensation Change form assigned to their user role, because they don’t have the authority to approve compensation changes. Associate the Job Assignment and Compensation Change form with the Decision node, followed by a Routing node that sends the form to a payroll administrator. When the payroll administrator receives the Job Assignment and Compensation Change Form, any data fields that are common to both forms are already populated and the user updates the additional fields before approving the form and completing the workflow process.
If you select a form that has no common fields with the form that initiated the workflow to a workflow with a single level of approval, the user that receives the decision notification won’t see the information that was submitted with the original form. However, if the user approves the associated form, the information on the original form will also be approved.
When you configure a workflow that needs multiple levels of approval, and contains more than one Decision node, you can associate a different form with one or more of the decision levels.
Note: Ensure that at least one user views and responds to the submitted form.
Can See Self
Select the checkbox and the recipient of the message can view their own employee data contained on the form included with the message when they receive the associated form. Clear the checkbox and Dayforce hides the information about the employee contained on the form. For example, with this checkbox cleared, when a copy of the Job Assignment and Compensation form is sent to an employee, their salary information is hidden on the form.
Timeout Value
Enter the time period, in minutes, that elapses before Dayforce triggers a timeout response. This allows the workflow process to progress to an automated response, such as rerouting, approving, or rejecting the submitted request, after a specific amount of time. For example, enter 1440 and, if no decision has been made after 1440 minutes, or 24 hours, the workflow process continues and the form is forwarded to another user.
This property is used only if an outgoing link with a response value of Timeout is attached to the Decision node. The workflow node that follows the link becomes active when the timeout value has elapsed.
Maximum Timeout Retries
Enter any value from 0 to 10. This field defaults to 3 if you enter a value in the Timeout Value field. If a workflow times out, Dayforce attempts to retry the process the specified number of times before the workflow ends with a state of Timeout. A message is shown in the workflow's End node history indicating the timeout state, and identifying the Decision node where the number of retries was exceeded.