7.1 What do contexts look like?

Context types are general “umbrella structures” and may typically be called “Sales orders”, “Vessels”, “Countries”, etc. They contain settings for a type of work.

Contexts are specific instances of contact types, e.g. work on a particular sales order, a specific vessel or a specific country. Usually a context type describes a long-term type of work while a context is an individual project with perhaps a time span of a few months.

Contexts in the Zegeba app

To the app users, contexts provide a way of sorting their work tasks into categories. Instead of scrolling through a list of available tasks in the Tasks menu option, they can now browse through the contexts to find the tasks issued for each separate category/context.

This is the context “Viking Warrior” in the app, under the context type Vessels:

On this Zegeba server the app user has 3 relevant context types: Customers, Vessels, Orders, listed in the menu to the left. In this example contexts and subcontexts will only be shown in the app if the user has tasks in them. One can also choose to have all contexts and subcontexts shown to all users in the app. We see that the user has work waiting on just one vessel right now, the “Viking Warrior”.

By clicking on “Viking Warrior” the user will continue to the subcontext Decks. There are task on Deck 1 and 2 waiting to be done:

Above are the 2 subcontexts Deck 1 and Deck 2 for the context Viking Warrior. Clicking on Deck 2 will show the subcontext Cabins:

Cabins ES-101, ES-102, ES-103 are shown here, as the user has tasks waiting to be done in each of these cabins.

We click on cabin ES-101 to see the following screen:

The above picture shows the one task waiting for this user in cabin ES-101. When we click on this task we see the familiar task screen:

To the right are the 2 forms in this task. To the left are details with information regarding the specific task (the task details) above the line separator. Below this line is the information regarding the specific context (the context details). The task and context details can be filled in automatically in the form, so the users don’t have to enter them every time they start on a new task report.

Contexts in the Dashboard’s Context Builder

Users with Admin or Tasks Admin roles can follow the progress of work on this vessel in the Context Builder. When app users have finished work on the task pictured above and set its state from New to Ongoing to Done, the task state is shown in the Context Builder like this:

Users with the role of Admin or Tasks Admin can use the Context Builder to create contexts. This is described in the remainder of this chapter.