Collective Signature

In many cases, mobile workers have to process more than one task on the same location. OMD Mobile allows to process these tasks as a collection of tasks. The condition to process tasks collectively depends on the collectiveCriterion preference:

  • phone (default)
  • debtor
  • debtorAndAddress
  • account
  • taskGroupId
  • none

Note that the criterion is tested against the predecessors and successors of the selected task. All tasks matching the collective criterion in sequence - without interruption of a task not fulfilling the criterion - will be gathered into the collection. The mobile worker may choose to open tasks individually when selecting a collection until the task is being processed. Once a collection is started, all further steps will be executed collectively.

OMD Mobile will close all collective tasks individually once the signature is captured and the collective task is finished. The signature is automatically copied onto each task of the collection.

When itemsPlanned of participating tasks match in reference, content, subtype and processFlow, their amount will be summed up and only one entry will be shown in the Task Info view. When tapping on the entry, all aggregated itemsPlanned are displayed separately, in another view. There are different options, how entries are aggregated:

  • toDo - aggregate all items, that have not been processed yet,
  • toDoDone - aggregate items in two groups: all processed / all not yet processed,
  • all - aggregate all items to one entry,
  • none - do not aggregate at all.

The options true (default, replaced by toDo) and false (replaced by none) are deprecated.

However, this aggregation will not be available, when a taskDetailFilterTemplate is set. In that case, applying an itemsPlannedLocalExtraGroupingTemplate might be a considerable solution to visually group itemsPlanned.

collectionCriterionExclude
Type Default Value Example Android HTML 5
String none delivery,pickup + -

The flow preference collectionCriterionExclude disables grouping one or more tasks with the collection, in case their task type is mentioned in the comma-separated list found in the value of the preference.

attachmentListAggregation
Type Default Value Example Android HTML 5
Boolean toDo none + -

results matching ""

    No results matching ""