Employee details

The first part of this form is a paragraph that's titled: !!! IMPORTANT CHANGES you need to make BEFORE running this workflow: This paragraph contains instructions on how to personalize the workflow for you and your company. If you intend to run the workflow, these changes can not be ignored.

Next you'll notice two faded out fields. These are called 'hidden fields'. These fields capture information without displaying it to the user and make the information available to other tasks in the workflow.

The workflow starts when a logged-in user (e.g. a manager or member of Human Resources) fills in this form with the details of the employee who is leaving the company.

Notify employee of exit survey

The employee receives an email asking them to complete the exit survey by following a link in the email.

Notify employee of exit survey

The employee receives a Slack notification asking them to complete the exit survey by following a link in the notification.

Exit survey

This form task has one condition:

Activate this task when...
'Email' IS '{user.email:{field.value:24288}}'

This form can only be viewed and completed by the employee selected in the 'Employee details' form task.
The employee completes the exit survey and saves the form. The next form is displayed immediately for them to complete.

Knowledge transfer questions

This form task has the same condition as the previous form task:

Activate this task when...
'Email' IS '{user.email:{field.value:24288}}'

This form can only be viewed and completed by the employee selected in the 'Employee details' form task.
The employee answers the knowledge transfer questions and saves the form.

Exit survey

DocRaptor generates a PDF of the exit survey.

Kotive creates the content of the PDF by pulling in the details from the previous forms.

Let's start by looking at how the PDF is typed up. There are lots of normal looking text words, but there are also lots of rectangular, shaded in, blocks of text. What's the difference?

Well, the normal text is just that: normal text. There's nothing special about it. But the blocks of text are actually information that is being pulled in from the previous forms. If you click on the text area of the PDF while in the webapp, you'll see that it changes and suddenly looks like a lot of code with lots of curly brackets { } and numbers. This code (also called dynamic field tags) is what tells these fields of text what they're going to end up saying. When this PDF is generated, it won't look like it does now, it will all be normal text, because the workflow will look at the previous forms and put the information from those forms into this PDF.

Notify HR survey completed

Human Resources receives an email informing them that the exit survey has been completed. The survey is detailed in the email, and a link to the PDF is included as well. HR is instructed to review the survey in the next form task.

Notify HR survey completed

Human Resources receives a Slack notification informing them that the exit survey has been completed. HR is instructed to review the survey in the next form task.

HR review exit survey

This form task has one condition:

Activate this task when...
'Role' IS 'HR'

This form can only be viewed and completed by a member of Human Resources.
Human Resources reviews the exit survey, and indicates if there are any issues that the manager needs to be made aware of.

If HR indicates that there are issues that need to be resolved, then the 'Issues with exit survey' sub-workflow is activated next. However, if HR indicates that there are no issues, then the sub-workflow is skipped, and the 'Final day checklist' form task is activated immediately, instead.

Issues with exit survey

This sub-workflow has one condition:

Activate this task when...
'Are there any issues that the manager needs to be aware of?' IS 'Yes'

This sub-workflow will only be activated if HR indicated that the manager should be made aware of issues in the previous form task.

Notify manager of issues

The manager receives an email informing them that there are issues with the exit survey. The email details the exit survey, and includes the comments from HR from the 'HR review exit survey' form task. The manager is instructed to review the issues in the next form task.

Notify manager of issues

The manager receives a Slack notification informing them that there are issues with the exit survey. The manager is instructed to review the issues in the next form task.

Manager resolve issues

This form task has one condition:

Activate this task when...
'Role' IS 'Manager'

This form can only be viewed and completed by a manager.
The manager reviews the exit survey, and views the comments left by HR. They indicate that the issues have been resolved, and leave comments for HR if necessary, before saving the form.

Notify HR - issues resolved

Human Resources receive an email notifying them that the manager has resolved the issues with the exit survey. Any comments left by the manager are included in the email, and HR is instructed to continue with the next task.

Notify HR - issues resolved

Human Resources receive a Slack notification notifying them that the manager has resolved the issues with the exit survey. Any comments left by the manager are included in the notification, and HR is instructed to continue with the next task.

Final day checklist

This form task has four conditions:

Activate this task when...
'Role' IS 'HR'
AND
'Are there any issues that the manager needs to be aware of?' IS 'No'
OR
'Role' IS 'HR'
AND
'Have you resolved the issues listed above with the employee leaving?' IS 'Yes'

This form can only be viewed and completed by a member of Human Resources, IF they indicated that there were no issues with the exit survey in the 'HR review exit survey' form task, OR if the manager indicated that the issues were resolved in the 'Manager resolve issues' form task.
Human Resources completes the checklist and saves the form.