The GP Monitoring workflow is a system workflow that tracks the life cycle of guided processes that employees complete in Dayforce during events such as onboarding or offboarding. It allows you to keep track of the status of each form in an employee’s guided process from one workflow, instead of from the individual workflows of each form.
When users submit one of the forms of a guided process, Dayforce launches the GP Monitoring system workflow. This workflow runs in the background and its activity is visible only in Workflow Administration > Workflow Management. It’s separate from the workflows of the individual forms in a guided process.
In Workflow Management, the History section of the GP Monitoring workflow indicates when forms in the associated guided process are successfully processed or not. After all of the forms of the guided process are processed, the GP Monitoring workflow ends with no action.
For example, say that a new employee needs to complete a guided process containing several workflow-enabled forms. The employee first submits the Direct Deposit form of the guided process. This triggers the workflow for the Direct Deposit form, plus the GP Monitoring workflow. The following screenshot shows how the records for each workflow would be displayed in Workflow Management:
When the Direct Deposit form is processed, an entry is added to the history of the GP Monitoring workflow to indicate that the form was processed.
The workflow for the Direct Deposit form is updated to the Completed status, and the GP Monitoring workflow remains in the Open status until all of the forms of the employee’s guided process have been processed.
The GP Monitoring workflow is shown in the list of system workflows in Workflow Administration > Workflow Designer. No configuration is supported for this workflow:
This workflow goes through the following process that can be tracked in Workflow Administration > Workflow Management:
- When a user submits a form that is part of a guided process, the workflow moves from the Start node to the Routing node, and an entry is added to the history to indicate that a decision message was sent.
- The workflow moves from the Routing node to the Guided Process Decision node. This is a system decision node that tracks whether the form is processed.
- The workflow cycles between the Guided Process Decision node and Routing node until all of the forms in the guided process are processed successfully.
- After all of the forms in the guided process are processed, the workflow moves from the Guided Process Decision node through the following path: All Forms Submitted connector > Routing node > End node.
The following is an example of the history of a GP Monitoring workflow when the associated guided process has two forms:
You can click the icon next to one of the entries in the history to view more information about the guided process in the GP Monitoring Summary dialog box:
The dialog box shows details about the guided process including its name, date submitted, and the number of forms it contains. Information about forms that were skipped is shown in the following fields:
- Number of Forms Skipped: Shows the total number of forms in the guided process that were skipped.
- Number of Forms Skipped and Completed: Shows the number of forms that were processed, including submitted and skipped forms.