The task is created because there is a job to do. The task will enable the manager to carry out all that is required in order to complete the job at hand. The task acts as a wrapper for everything that is required to complete the issue
These are tasks that recur at a given frequency, e.g. inspection task. This article is inked to creating a recurring task
When creating a task it helps that there is a task type to hang the task on to. Arthur provides a set of default task types. This article is linked to understanding task types
Subtasks are designed to be added to tasks in order that the manager can perform the role whilst being aided by a checklist embedded within the task. Checklists can be added manually or automatically on creation of a task.
This is linked to the article understanding subtasks
Depending on where it’s shared will determine which tenants see what:
Depending on which level a task is raised, property, unit or tenancy will determine what functions are available to you. There are two menu options available within the task:
a) Primary menu
This will give you options to update anything to do specifically with this task.
b) Secondary relationship menu
This secondary relationship menu means you can carry out many functions without leaving the task. These are to do with whatever the task is related to – e.g. the property, unit, tenancy etc.
In the example below the task is related to the tenancy and many functions related to a tenancy can be created from within the task. The example below shows tenancy information and provides the same menu as found within a tenancy
Our support staff are ready to help with any technical issues.
To get in touch please use our online chat below