Evaluation

This workflow consists of only one form.

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.

A student evaluates a specific lecturer by filling in this form. After the student saves the form, the 'Lecturer evaluation' workflow is complete.

This is a 'published task' - any student can view and complete this form, they do not have to be a logged-in user.

The 'Live Workflows' view

In order to compile the feedback in the next form task, the user would need to view the 'Live Workflows' of the 'Lecturer evaluation' workflow. By setting up the columns to display all of the feedback from the 'Evaluation' form, the user will be able to view all of the data in one convenient location, making compiling the data an easy task.

Compile feedback

This form also starts with a paragraph titled: !!! IMPORTANT CHANGES you need to make BEFORE running this workflow:

The 'Lecturer evaluation feedback' workflow starts when a logged-in Kotive user compiles the feedback received in the 'Lecturer evaluation' workflow, and fills in this form with the compiled information.

Notify head of department

The department head receives an email detailing the compiled feedback.

Kotive creates the content of the email by pulling in the details from the previous form.

Let's start by looking at how the email 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 form. If you click on the text area of the email 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 email gets sent to the department head, it won't look like it does now, it will all be normal text, because the workflow will look at the previous form and put the information from that form into this email.

A link at the bottom of the email directs them to the next form task.

Review

This form task has one condition:

Activate this task when...
'Role' IS 'Head of department'

This form can only be viewed and completed by the department head.
The department head reviews the compiled feedback, and gives further feedback to the lecturer.

Inform lecturer

The lecturer receives an email which contains the compiled feedback, along with the feedback given by the department head in the previous form task.