Contexts is a Zegeba module requested by those of our customers who use tasks. This module will be further developed in upcoming versions of Zegeba.
A context is generally a collection of work tasks to be done on a specific project but the “collection” can also be defined as a work order, a work site, etc. You can have different context types on your Zegeba server for different types of projects, such as Work Orders, Builds, Schools, Regions, etc., and then define the individual contexts as specific projects under these categories.
Why start using contexts?
For administrators, contexts provide a unique overview of the progress of a project
- In the Dashboard, administrators will in the “Context Builder” be able to track the progress of all work on a specific project, making it easy to see which tasks are finished, ongoing or not started yet
For Next app users, contexts categorize work tasks and allow for automatic prefill of form data
- Users can now browse through a context to find their tasks for this specific project instead of scrolling through a long list of unrelated tasks
- Information like project name, customer etc. can be automatically “inherited” from the context to the task, saving time for users having to fill in this information in their forms
- Such inherited information will always be correct, with no typos or misunderstandings
An example of a context
The table below illustrates the context type Vessels and two contexts defined under it: the ships “Viking Warrior” and “Lucitania”. These have as subcontexts their decks and cabins, and for each cabin listed there are tasks to be done. Each task has one or more forms to be filled in. The form fields concerning Vessel name, Deck number, Cabin number etc. are already filled out in the forms when the Next app users open them for the first time.
Users with the role of Admin or Tasks Admin can create contexts in the Contexts Builder. This is described in the remainder of this chapter.
In the Context Type editor available in the Dashboard, Admins can design new context types. This editor is described in the next chapter; Managing: 8 Managing context types.
Pages in this chapter: