Task types

Modified on Fri, 11 Jul at 3:14 PM

Disclaimer

All screenshots in the article were taken in the Dutch version of Yuki.


If your domain has users with roles, or you have created employees, then you can use different types of tasks with each document in Yuki. A task is an action, question or assignment for a user within Yuki. Tasks allow you to set up small work processes (simple workflow system) within your business. Create tasks for employees, for example, creating an order. 


In Yuki, you can view an overview of all created task types.


All defined settings such as task types are brought together and categorized in one place in your domain.


Open the settings of your domain by clicking on the Settings icon in the navigation bar and then click on Task types in the now-opened screen.


ATTENTION!

In a domain with the bundle Small, Medium, Large or Unlimited, the Calendar is available and the overview of all created task types can also be opened by moving your mouse over the Calendar icon in the navigation bar and then clicking on Task types.


The following screen is opened:



By default, Yuki provides two task types: Task and Release for payment. The task type ‘Release for payment’ is the only task type directly linked to the payment list.


You can create new task types yourself. Task types used by Yuki itself include:

  • Hours registration
  • Bug reports
  • Support request
  • Ordering
  • Call note.


To create a new task type, click on the New task type button.

When creating task types, the behavior of the tasks is determined.


For a detailed description of creating new task types see article Create new task type.


Example task type Ordering




Example task step 1 Approval (of order)

Below is an example of a task to be approved by the specified employee, in this example the employee Yuki Financiële administratie (Yuki Financial Administration).



Click on > in front of the task with Open status. The following screen is opened:



  1. Approve the task which transfers it to the person responsible for the step Realization
  2. Disapprove the task which transfers it back to the person who created the task
  3. Need more information which transfers the task back to the person who created the task
  4. Link this task as a subtask to another task
  5. Create a subtask for this task
  6. Create an activity (hours registration) for this task.

Example task step 2 Realization

Below is an example of a task to be realized by the specified employee, in this example the employee Yuki Inkoop (Yuki Purchase).



Click on > in front of the task with Approved status. The following screen is opened:



  1. Send the task back to the step Approval
  2. Ready which transfers the task to the step Approval of realization
  3. Link this task as a subtask to another task
  4. Create a subtask for this task
  5. Create an activity (hours registration)) for this task.

Example task step 3 Approval of realization

Below is an example of a task whose realization needs to be approved by the specified employee, in this example the employee Yuki Directie (Yuki Management).



Click on > in front of the task with Realized status. The following screen is opened:



  1. Realization of the task is approved
  2. Realization of the task is rejected which returns the task to the Realization step
  3. Link this task as a subtask to another task
  4. Create a subtask for this task
  5. Create an activity (hours registration) for this task.

Example completed task

Below is an example of a task that has gone through all the steps and is therefore completed. In this example, the employee Yuki Inkoop (Yuki Purchase) can view the completed task by selecting Completed tasks from the dropdown menu.



Click on > in front of the task with the Completed status. The following screen is opened:



Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article