Daybook and activity planning

Find out how to plan mobile activities with TDox

WEB DAYBOOK

On the web-side TDox agenda you can schedule/plan an event linked to a module. For example, supposing you have created a module for the maintenance management, you can schedule these activities by assigning them to your specific operator. Click on the scheduled maintenance day, select the form and enter any notes: you have created the event in “draft” status on the calendar. This event is not associated with any user and serves only as a reminder.

Once the draft action has been created, you must confirm it to make it visible to your operator: select the event created in the web daybook again, assigning it to the user and fill in the detail fields if available process.

The confirmed event will be visible to the mobile operator to whom you assigned it once the synchronization has been performed.

EVENTS STATUS

Possible states of an event on the daybook are:

  1. Draft
    It is highlighted in orange on the webapp; it is not visible from the mobile app.
    Clicking on the event opens the page where you can set the operator and the details of the fields to be planned.

    Operations on an event in “draft” state

    • Save draft: save the event again; for example, assign the user or complete some of the fields that can be planned, leaving the planner the task of completing or validating what has been entered. While specifying the user, this event will not be visible on the mobile app.
    • Clone event: clone the event keeping what has already been entered but specifying a different date.
    • Confirmation: confirm the event making it visible to the operator to whom it has been assigned on the mobile app. The confirmation of the event logically requires that a user is specified.
    • Delete: deleting an event in “draft” state.
  2. Confirmed
    It is highlighted in green on the WebApp; it is visible on the mobile App of the user to whom it has been assigned.

    Operations on an event in “confirmed” status

    • Warn operator: if enabled it allows to send a push notification on the device of the user to whom the event has been assigned.
    • Save: save the event again; for example, change the values of some previously planned fields.
    • Clone event: clone the event keeping what has already been inserted but specifying a different date and returning it to the draft state (therefore to be confirmed).
    • Delete: an event in a confirmed state can be deleted.
  3. In progress
    It is highlighted in blue on the WebApp; it is visible on the mobile App of the user to which it has been assigned in the Archive section among the compiled instances.

    Operations on an event in “in progress” status

    • Clone event: clone the event keeping what has already been entered but specifying a different date. The event is reported in draft status.
    • Delete: an event in a confirmed state can be deleted.
  4. Completed
    It is highlighted in gray on the WebApp.

    Operations on an event in “completed” state
    The only possible operation is the visualization of the data compiled (by clicking on the completed event) and, if necessary, the printing in PDF of the same.

  5. Canceled
    It is highlighted in purple on the WebApp; the canceled status is determined by canceling the event on the mobile app.

    Operations on an event in “canceled” status

    • Clone event: clone the event keeping what has already been entered but specifying a different date. The event is reported in draft status.
    • Delete: an event in a canceled state can be deleted.

OTHER FUNCTIONS

Events research

It is possible to filter the events contained in the daybook for a single form (point 1 of the image below) or for a single user (point 2 of the image below).

Push notifications

Through button it is possible to send push notifications to the selected operators in the appropriate panel. This can be useful in case of communications that massively involve the operators in the field.

Import events

It is possible to massively import events by clicking on the import/export button and then on the button through which the selection panel of the file to be imported will open. The import is limited to “flat” processes therefore without repeated steps.

To obtain the template in xlsx format, which is necessary for importing, it is sufficient to use the “import/export” button and then the “Export” button: you will get an empty file in which some fixed fields/columns will be reported (such as Event code, Event start date, Event end date, etc.) and other configurable variables.

DAYBOOK PARAMETERS CONFIGURATION

SHOW EVENTS CLOSED

  • ALWAYS

    It allows you to always view completed events (closed) in the mobile daybook.

  • NEVER

    It does not display completed events in the mobile daybook. It can be used if, once the event is completed, users do not have to be able to edit the compilation again.

  • ON DEMAND

    Shows completed events only if the user selects the “show completed events” check.

Event grouping mode

  • NO GROUP

    The events are shown in the mobile daybook in the form of a simple list (the title of the form shows “Planned events”).

  • BY DATE

    Events are shown in the mobile daybook grouped by day. Selecting this grouping mode, an additional selection will be shown and will allow you to define the phase displacement time before and after the date of the event. These values allow you to view the event. Referring to the image on the right, the events will be visible from 23/02/2019 to 05/03/2019.

  • BY OBJECT VALUE

    Events are shown in the mobile daybook grouped by a variable (object) defined within the process. Example: subdivision of interventions by area of competence. In this case the “zone” variable will be populated taking the province of the client on which the event was planned.

    You can also define:
    -a description, which will be the label under which the events will be displayed (for example “Zones / Areas of intervention”);
    -a event execution constraint, which can take three values: no constraint, increasing, decreasing.

    The option “Include groupings with all events executed” allows you to view groupings, even if all events have already been executed (closed).

Sorting events

  • BY DATE AND TIME (Ascending/descending)

    Sort events by ascending/descending date and time. The functionality is only available if a grouping is selected.

  • BY OBJECT VALUE crescente/decrescente)

    Sorts events for the value of the ascending/descending object. For example: alphabetical sort by province. The functionality is only available if a grouping is selected.

Show event date and time

Adjust the date/time display of events (looking at the image on the right you can see that no time has been set on events so only the date is displayed).

Expand the daybook events view

The extended view allows you to view events with different formatting showing more information about them. In the example shown on the right, in addition to the model name and the customer that would still be displayed in normal mode (not extended), the customer’s address, telephone number and e-mail are also shown.

Function “navigate to a point” (present in the case where the address set in client graphics is valid) allows you to activate Google Maps.
The extended mode allows you to view the play key needed for the event to run.

The values that can take the extended mode are:

  • NEVER: the events are always shown in compressed mode
  • ALWAYS: events are always shown in extended mode
  • ON DEMAND: the events are shown by default in compressed mode, but clicking on them are “enlarged” assuming the extended view.

MOBILE DAYBOOK

On the mobile daybook the users will find the scheduled events and will only have to select the play to execute them. Depending on whether or not the “Enable event deletion from agenda” flag is selected in the form settings (see image below) the mobile operator can cancel the event proposed by the planner. It is possible to allow the execution of a form only from the agenda, setting the visibility on the user.


Learn more about all our successful cases

Check our Case History