Skip to main content

Mobile dispatch

Mobile dispatch lets you assign tasks to resources directly from the Progression mobile app, without going through the web.

Video - Watch the demo:

Mobile dispatch lets you assign tasks to resources directly from the Progression mobile app, without going through the web.


Overview

Mobile dispatch (the app's Mobile dispatch menu) shows the tasks waiting for a resource and lets you assign them in a few taps, from the field.

It serves two profiles:

  • The independent technician, who takes free tasks from the task pool themselves (self mode).

  • The dispatcher or foreman, who assigns tasks to any active resource, reassigns tasks already dispatched and manages helpers (dispatch mode).

Assigning a task here does the same thing as on the web: the task goes through the Assigned (100) and then Dispatched (200) states, following the workflow and the role's rights, and is sent to the chosen resource's mobile device.

The main screen: the tabs at the top, the list in the middle, the action bar at the bottom (sample data).


Access and permissions

The Mobile dispatch menu appears in the mobile app when these three conditions are met:

  1. The user is linked to a human resource (resource profile).

  2. Their role has one of the two permissions below.

  3. There are task types where Mobile dispatchable is checked (in the task type's form). Only tasks of these types appear in the lists.

Permission (role)

Mode

What it gives

Dispatch module access (mobile) - Self mode

Self

See the task pool and assign a task to yourself

Dispatch module access (mobile) - Dispatch mode

Dispatch

Everything in self mode, plus: assign to any resource, the Dispatched tab, helper management

An administrator gives each role either self mode only or full dispatch mode. Dispatch mode includes self mode, so there is no need to check both.

Other settings also apply:

  • The workflow: a task is offered only if the user's role can make the transitions to Assigned (100) and then Dispatched (200) from the task's current state.

  • The company's Helper module: without it, helper management is not offered.

  • The Disponibility module: without it (or without access for the role), the resource availability filter is not offered.


The two modes

The mode depends only on the role's permission: there is no button to switch from one mode to the other.

Self

Dispatch

Tabs

Scheduled, Unscheduled

Scheduled, Unscheduled, Dispatched

Assign to me (yourself)

Yes

Yes

Assign to… (another resource)

No

Yes, any active resource

Reassign a task already dispatched

No

Yes

Manage helpers

No

Yes, with the Helper module

Remove the appointment while assigning

No

Yes, if nothing makes it mandatory

Multiple selection

Yes

Yes

In self mode, a task already assigned to the user themselves does not appear in their pool.


The task lists

The main screen has two or three tabs, each with its task count.

Tab

Resource

Task state

Appointment

Mode

Scheduled

None

From Draft (0) up to before Assigned (100)

On the day chosen in the date strip (today when it opens)

Both

Unscheduled

None

From Draft (0) up to before Assigned (100)

No appointment, all dates

Both

Dispatched

Already has a resource, named on each card

From Assigned (100) up to before Completed (600)

With or without an appointment, all dates

Dispatch

The first two tabs make up the pool: the free tasks, which self mode can take and which dispatch mode can also assign to someone else. A task at Completed (600) or beyond appears in no tab. In dispatch mode, Assign to… works on all three tabs; on Dispatched, it is a reassignment.

In every case, only tasks of a type where mobile dispatch is allowed, and that the workflow lets the role take all the way to Dispatched, appear.

What you can do in a list:

  • Change the day (Scheduled tab) with the date strip at the top.

  • Search by task code, summary or client name.

  • Pull down to refresh the list and the tab counts.

  • Scroll: the next tasks load as you go.

  • Tap a card to select it; the bottom bar then offers Details, Assign to me and, in dispatch mode, Assign to…

The Dispatched tab: each card shows its current resource (sample data).


Search and filters

The Search... bar at the top of the list finds a task by its code, its summary or its client's name. The filter button next to it opens the Filters screen.

Filter

Choices

Tabs

Task type

One or more types

All

Project

One or more projects

All

Client

One or more clients

All

Location

One or more locations

All

Tags

One or more tags

All

Status

The states from Assigned (100) to before Completed (600), with the names from the company's workflow

Dispatched

Appointment

From / Until, and "Include tasks with no appointment"

Dispatched

  • Apply saves the filters and returns to the list. Leaving the screen any other way (Close button, back) discards the changes.

  • Reset removes all filters at once, including those already applied.

  • The search and filters also apply to the counts shown on the tabs.

  • Changing the tab, day, search or filters clears the current selection, so you never act on a task you can no longer see.

An empty list says so: "No tasks to dispatch with the active filters." when the filters are what empties it.

The Filters screen opened from Dispatched, with Appointment and Status (sample data).


Task details

Selecting a card and tapping Details opens the task's form, read-only, so you can decide whether to assign it. It shows:

  • the type, state, code and priority;

  • the appointment and duration;

  • the project, client and location;

  • the summary and description;

  • the assigned resource and the helpers ("No helpers" if there are none);

  • the task properties the role can see.

The bottom bar offers the same actions as the list: Assign to me and, in dispatch mode, Assign to…. In dispatch mode with the Helper module, a Manage helpers button appears under the helpers.

If someone else took the task in the meantime, the form says so ("This task is no longer available.") and returns to the list.

A task's form and its Assign to me / Assign to… bar (sample data).


Assign a task

Assign to me

  1. Select the task (or open its details) and tap Assign to me.

  2. The confirmation screen shows the task, the appointment and, if any, the mandatory fields to fill in.

  3. Tap Confirm. The task is assigned and dispatched to the user, and the app returns to the list with the message "Task assigned."

Assign to… (dispatch mode)

  1. Tap Assign to…: the list of active resources opens.

  2. Search for a resource by name, or filter by Resources, Availability (with the Disponibility module) or Tags.

  3. Choose the resource, then tap Next.

  4. On the confirmation, check Assign to: [name] and tap Confirm ("Task assigned to [name].").

In the resource list:

  • the task's current resource is shown separately, under Current resource: choosing it would change nothing;

  • a resource that is already a helper on the task is marked Already a helper on this task; it can be chosen, and then stops being a helper.

The confirmation also says what the assignment changes: the resource the task loses ("Resource removed: [name]") and the helper who becomes the resource ("[name] will no longer be a helper on this task.").

Reassigning a task from the Dispatched tab takes it back to Assigned (100) and then Dispatched (200): this is what moves it from the previous resource's mobile device to the new one's.

The appointment

The confirmation shows the current appointment (or "No appointment"). To change it:

  1. Turn on Change the appointment.

  2. Choose the date and time in Date and time. For a task with no appointment, the field starts empty.

  3. Confirm. The new appointment is saved after the assignment, so that the change goes to the new resource's mobile device.

If the appointment is mandatory to assign the task, Change the appointment is turned on automatically and cannot be turned off; an orange badge says so ("Appointment required to assign this task"). Confirming without a date shows "Enter the date and time of the appointment."

In dispatch mode, you can also remove a task's appointment: clear the field with the × ("The appointment will be removed"). This is only possible if the appointment is not mandatory for this role, neither at all times nor for states 100 and 200.

The confirmation for a task with no appointment, when one is mandatory: Change the appointment locked and an orange badge (sample data).

Assign to…: the current resource shown separately, and resources marked Already a helper (sample data).


Multiple selection (batch)

Multiple selection assigns several tasks at once, to yourself or (dispatch mode) to the same resource. It is available in both modes.

  1. Tap Multiple selection at the top of the list, then check the tasks, or Select all. The bottom bar shows "3 tasks selected".

  2. Tap Assign to me, or Assign to…, then choose the resource and tap Next.

  3. The confirmation screen lists the tasks (a short version of each card) with what the assignment changes for each one, and the mandatory fields to fill in, if any.

  4. Tap Confirm (3). The tasks are sent one by one ("Sending 2 / 3…"), then the app returns to the list with a summary, for example "3 of 3 tasks assigned to [name]."

Good to know:

  • 50 tasks at most per selection.

  • A task already assigned to the chosen resource is set aside under Skipped, nothing will be done.

  • Appointments do not change: each task keeps its own. If the appointment is mandatory, a single date is asked for the tasks that have none (Appointment card, "Tasks without an appointment: 2"); the others keep theirs.

  • A mandatory field is asked only once, and the value entered goes only to the tasks where it is empty.

  • Each task is processed separately: if one is refused, the others are still assigned. The summary gives the reason for each task not assigned (taken by someone else, refused by the workflow, mandatory fields empty, connection lost…).

  • Tasks not assigned stay selected in the list, ready for another try; what was entered is kept for that new try.

The list in multiple selection: three tasks checked and the bottom bar (sample data).

The batch confirmation: the tasks, the Appointment card and the mandatory fields (sample data).


Mandatory fields

Assigning a task takes it through two states: Assigned (100) and then Dispatched (200). The fields the role makes mandatory for these states are asked on the confirmation screen, under Mandatory fields, before the task is sent.

A field is asked when it meets all these conditions:

  • it is mandatory, in the role's configuration for this task type, at state 100 or 200, or on a transition along the assignment path (from the current state to 100, then from 100 to 200);

  • it is empty on the task;

  • the user can see and edit it (the role's rights on the field or the property).

The fields asked can be:

  • the summary and the description;

  • the appointment (see The appointment, above);

  • the client and the location;

  • the task's dynamic properties: text, number, date, choice list, yes/no, entity lookup (client, location, resource, product…), grouped as in their property groups.

How it works:

  1. The fields to fill in are shown with an asterisk.

  2. Tapping Confirm with a field still empty turns it red, with the message "Required"; nothing is sent.

  3. Once everything is filled in, Confirm saves the values to the task, then assigns it.

Special cases:

  • Yes/no: a mandatory yes/no property is asked with two choices, "No" and "Yes", neither checked at first. Both answers are accepted. As long as it is "No", it is asked again at each assignment, to confirm that "No" really is the intended answer.

  • Task in a project: the client is the project's and is not asked; the location is chosen from the project's locations.

  • Task with no client: if the location is asked, the client is asked just before it, since the location is chosen from the client's locations.

  • Mandatory "at all times": this setting is not asked at assignment, which only fills in what states 100 and 200 require. For the appointment, it only prevents removing it.

  • Fields to complete on the web: some mandatory fields are filled in in the web application. The screen names them in a blue box ("To complete on the web: …"); they do not block the assignment.

  • In a batch: each field is asked once, and the value goes only to the tasks where it is empty.

The server checks again at the moment of assigning. If a field has become empty in the meantime (task or configuration changed by someone else), the assignment is refused and the fields are asked again.

What was entered is kept if the app closes before confirmation, and comes back when you reopen the same confirmation on the same day.

The Mandatory fields section: summary, client and location, then a property group with a yes/no (sample data).

The same fields after Confirm, in red with "Required" (sample data).


Helpers

Everyone sees a task's helpers in its details. In dispatch mode, with the company's Helper module, you can also change them:

  1. Open the task's Details and tap Manage helpers.

  2. The current helpers are listed first, already checked, under Current helpers. Unchecking a helper removes them; checking another resource adds them. Search and filters work as for Assign to…

  3. Tap Next: the screen summarizes the change, To be removed (1) and To be added (2).

  4. Tap Confirm ("Helpers updated.").

The change goes through the same path as editing the task on the web: the helpers receive the same notifications. The task's current resource is shown separately and cannot be added as a helper.

Manage helpers: the current helpers checked at the top (sample data).


Messages and special cases

Several people can dispatch at the same time. So when you confirm, the app checks that the task is still as it was displayed.

Message

What happened

What to do

This task was just taken or is no longer available.

Someone assigned it or it left the list

Nothing: the app returns to the updated list

This task changed since it was shown (resource or state). Nothing was done

Its resource or state changed in the meantime

Check it in the list and try again

This task's workflow does not let you assign it to yourself.

The workflow refuses the transition for this role

Review the workflow or the role with an administrator

Some mandatory fields are still empty: fill them in and try again.

A mandatory field is empty at the moment of assigning

Fill in the fields asked again and confirm

The mandatory fields could not be saved. The task was not assigned.

A value was refused when saving

Correct the value and try again; nothing changed on the task

Connection lost while sending

The network dropped during the confirmation

Check in the list whether the task was assigned

Not assigned, you no longer have access to mobile dispatch

The permission was removed from the role while sending

Check with an administrator

When an assignment is refused, nothing is saved on the task: neither the mandatory fields entered nor the appointment.

Leaving a confirmation after entering something asks for confirmation ("Leave without saving?").


Frequently asked questions

Access and display

I don't see the Mobile dispatch menu.

The user must be linked to a human resource and their role must have one of the "Dispatch module access (mobile)" permissions (self mode or dispatch mode).

I don't see the Dispatched tab or the Assign to… button.

These are dispatch mode features: you need the "Dispatch module access (mobile) - Dispatch mode" permission.

A task doesn't appear in the list.

Check, in this order:

  1. the task type has "Mobile dispatchable";

  2. the task has no resource and is at a state before Assigned (or, in dispatch mode, between Assigned and before Completed for the Dispatched tab);

  3. the workflow lets the role go all the way to Dispatched;

  4. the right tab and the right day are shown;

  5. no filter or search is hiding it.

Assignment

How many tasks can I assign at once?

Up to 50 per multiple selection.

What happens if two people take the same task?

The first confirmation wins. The second person sees "This task was just taken or is no longer available." and returns to the list.

Does the chosen resource receive the task on their mobile device?

Yes: the assignment goes through Assigned and then Dispatched, as on the web, and the task is sent to their mobile device. A reassignment removes it from the previous resource's mobile device.

Who can see that a task was dispatched from mobile?

The task's event log shows that it was dispatched from mobile dispatch, by whom and to which resource.

Appointment

Can I change the appointment while assigning?

  • One task at a time: yes, turn on "Change the appointment" on the confirmation.

  • In a batch: no, each task keeps its appointment; only a common date is asked for those that have none, when it is mandatory.

Can I remove a task's appointment?

In dispatch mode, if the appointment is not mandatory for this role: clear the date with the × on the confirmation.

Mandatory fields

Why am I asked for fields before assigning?

The role makes them mandatory for the Assigned (100) or Dispatched (200) states. They are asked only if they are empty and the user can edit them.

Why am I asked again for a yes/no that is already "No"?

A mandatory yes/no property is asked again as long as it is "No", to confirm the answer. Answering "No" is enough to assign.

Did this answer your question?