When the user enters the device and mobile application, the main menu is the first component they will see. The sections below explain the user interface.
1 Device Interaction
1.1 Main Menu
The main menu contains all the options the user has available to perform assignments. However, this document only explains the Tasks option, as this is the only applicable option for Taskforce Automation (TFA).
| Main Menu | ||||
|---|---|---|---|---|
|
Tasks | Set of pending tasks for the user, either from past days or the current day. It does not take scheduled future tasks into account. | ||
1.2 Tasks
The Monthly Calendar shows pending tasks with different-colored icons. It allows users to check pending tasks or create new ones.
| Monthly Task Agenda | ||||
|---|---|---|---|---|
| 1 |
|
Calendar Options |
|
Day: Displays a list of the current day's pending tasks. Week: Displays a list of the current week's pending tasks. Month: Displays a list of the current month's pending tasks. This option can also be viewed in a calendar structure. Year: Displays a list of the current year's pending tasks. |
| 2 |
|
Calendar List | The calendar view disappears, and a simple list of the current month's tasks is displayed. | |
| 3 |
|
Expand/Collapse | Clicking this button expands or hides task information. | |
| 4 |
|
Colours |
|
Opens a pop-up with the color code legend for task status, as well as the number of tasks for each color: Transferred: The device information has been synchronized with the main system. Closed: The task has been finalized and closed; synchronization is pending. Completed: All instructions have been executed, but the task has not been closed. Canceled: The task has been canceled and will not be executed. A task is cancellable if defined as such previously in the task form. Started: An instruction has been executed. Not Started (on time): The assignment is pending execution, and the assigned date is later than the current date and time. Not Started (delayed): The assignment is pending execution, and the assigned date is prior to the current date and time. Delayed tasks have the highest priority and should be executed first. |
| 5 |
|
Details | All assignment details are displayed here. This allows users to view all tasks assigned for a specific date and location. | |
| 6 |
|
See Day | A pop-up is displayed with assignment details for the day selected. | |
| 7 |
|
New Day |
A pop-up is displayed: New visit: A new visit will move all past pending assignments to the day seleceted. New customer: used to register a new customer. New event: used to create a new assignment. |
|
In any of the views described, swiping to the left will bring up future periods, while swiping to the right will bring up past periods. In addition, swiping up and down allows users to navigate through the task lists.
1.2.1 Current Day's Agenda
| Current Day's Agenda |
|---|
|
The current day view is the most common work view utilized by device users. It reflects only the tasks assigned to the selected day, and also continaully refreshes to keep tasks updated, without the need for manual synchronization.
| Current Day's Agenda | ||||
|---|---|---|---|---|
| 1 |
|
Calendar Options |
|
Day: Displays a list of the current day's pending tasks. Week: Displays a list of the current week's pending tasks. Month: Displays a list of the current month's pending tasks. This option can also be viewed in a calendar structure. Year: Displays a list of the current year's pending tasks. |
| 2 |
|
Number of Tasks | Indicates the total number of pending tasks for the day selected. | |
| 3 |
|
List Mode | Organizes the task list, classifying them into groups by their task code. | |
| 4 |
|
Options |
|
Map: Locations are represented on a map, and a route is proposed for all days' visits. Info: A pop-up is opened with the task status color code legend, and with the number of tasks per color. New: A pop-up is displayed to create a new assignment. |
| 5 |
|
Task Search | If the task has been given the tracking code attribute, users can search for it. | |
| 6 |
|
Task Information | Task information may include time of assignment, status of assignment, and the customer assigned to the task. | |
| 7 |
|
Task Process | Indicates task progress, predicted time needed to perform the task, and the task code. | |
| 8 |
|
Task Group | Classification of task groups. | |
1.3 Task Execution
When a user clicks on a task, all details of task information will appear, along with all instructions (questions) that the device user must complete.
| Task Execution | ||||
|---|---|---|---|---|
| 1 |
|
Header |
Displays customer name information. By tapping the header, the customer description field, with all relevant customer information, will be displayed. |
|
| 2 |
|
Attributes | The first block of information presented consists of the attributes previously defined in the assignment. Various types of attributes are possible. | |
| 3 |
|
Packages | Any delivery tasks will appear on this screen, revealing the code and description of the package to be delivered. | |
| 4 |
|
Task Instructions |
The questions which must be completed are presented in user-defined groupings. Various types of questions are available. |
|
| 5 |
|
Attribute Groups | Attributes are classified into different groups. | |
| 6 |
|
Collapse/Expand | Clicking the collapse/expand button hides or reveals the groups defined, with all related instruction information. | |
| 7 |
|
Special Attributes | Certain special types of attributes help the user by only presenting information about the task or customer. Others also help the user performing an action, when clicking on them (for example: performing a phone call to the customer). | |
| 8 |
|
Scanner |
To confirm a package as delivered, code can be written manually within the system, or this button can be used to enable the scanner. By scanning the barcode of a selected package, the system provides various options to differentiate:
|
|
1.4 Finalizing Tasks
After completing all task instructions (questions), the task must be closed and synchronized to send the result to the main system.
| Task Finalization | ||||
|---|---|---|---|---|
| 1 |
|
Finalize Task |
This button closes the task and prevents further modification of it. If the button does not appear in the view, this indicates that a mandatory field has not been answered. Mandatory fields which have not been filled out will appear in red. |
|
| 2 |
|
Print Task |
The print button will reveal a preview with all question responses which have been configured with the print option activated. The preview screen includes a button that allows users to send responses via email. |
|
| 3 |
|
Cancel Task | If the task configuration is set to give permission for users to cancel the task, they can do so with this button. | |
| 4 |
|
Collapse/Expand |
Clicking the collapse/expand button hides or reveals the groups defined, along with all instruction responses. |
|
| 5 |
|
Clear | This button clears all information filled out in the task. | |
Once the task has been ended, response content can be viewed but not modified.
The assignment menu allows the user to reprint the task, send it via email, or synchronize the assignment with the central system.
|
|
| Finalized Tasks Menu | |||
|---|---|---|---|
| 1 |
|
The print button will reveal a preview with all question responses which have been configured with the print option activated. The preview screen includes a button that allows users to send responses via email. |
|
| 2 |
|
Used to access the device email manager, sending the task as a file attachment. | |
| 3 |
|
Synchronize | Synchronizes the assignment with the central system. |
| 4 |
|
Collapse/Expand | Clicking the collapse/expand button hides or reveals the groups defined, along with all responses to instructions. |
| 5 |
|
Clear | This option is used to clear all task responses. However, it will NOT work in this case, as the task is closed and cannot be modified. |
2 Modification of Assignments in the Device
In any of the view options (month, week, day, etc.), if the user presses and holds an assignment, the device will bring up a menu for the user to modify the assignment date and time.
Via shell, a setting can be configured which makes it mandatory to report a reason every time an assignment is modified. With this action, the date and time, as well as the reason for modification, are updated in the central system. The reasons for modification are configured in the central system.
Configuration in the central system:
Menu path:
| Reason for Modification | |
|---|---|
|
|
Result:
Result system:
3 Manual Assignment from Device
Manual assignments are entered by users directly onto mobile devices. Users can create assignments in the device if they have the appropriate role.
Moreover, to be able to enter a manual assignment, the device must be in the daily or monthly view modes.
3.1 Manual Assignment from Monthly View
To create a manual assignment in monthly mode, simply tap a day, and a menu will appear with a "New Event" button.
The "New Event" button will reveal a manual entry form for an assignment.
Once the form is filled in and accepted, the manual assignment is registered in the calendar.
| Manual Assignment from Monthly View | |
|---|---|
|
|
3.2 Manual Assignment from Daily View
To perform a manual assignment in daily mode, simply tap the "Option" buttom in the device menu, and a menu with a "New" button will appear.
Once the form is filled in and accepted, the manual assignment is registered in the calendar.
| Manual Assignment from Daily View | |
|---|---|
|
|
3.3 Data Entry
| Data Entry | |
|---|---|
| Description | Assignment description. |
| Customer | Customer code. |
| Task | Task code. |
| Date assigned | Date and time of assignment. |
| Estimate (minutes) | Time estimated to perform the assignment (in minutes). |
| Minutes notification | Number of minutes the user will be notified in advance to perform an assignment. |
| Notes | Assignment notes. |
| Source Document | Document which generated the assignment. |
| Route | Specify the route code, if the assignment comes from a defined route. |