The about description is divided into the following sections:
A work task can be transferred to an assigned technician or to a common pool of work tasks. Previously, when a task was transferred to the pool, it was made available to all mobile users, filtered only by the resource group on the task's resource demand, or to everyone when no resource group was defined. This meant technicians often received pool tasks that were not relevant to them.
Pool Task Visibility and Filtering improves this by determining, at the time a task is transferred to the pool, exactly which mobile users should see it. Only relevant technicians receive the pool task on their devices. Which technicians are relevant is controlled by a combination of built-in eligibility rules and configurable matching options that can narrow the pool audience by Service Organization, Delivery Unit, and Region.
This reduces unnecessary noise for technicians, makes the pool task list faster to synchronize, and strengthens compliance with organizational boundaries.
When a work task is transferred to the pool (as Pool or Pool-Keep), the pool audience is evaluated once, and each eligible mobile user receives the task. A technician is eligible to see a pool task when all of the following conditions are met:
Note: The behavior of the pool itself is unchanged. The first technician who accepts a Pool task becomes its owner and the task is removed from the pool for all other users, while a Pool-Keep task can be accepted by multiple users. Pool tasks with resource demands are removed from the pool when the demand is satisfied, regardless of the transfer type (Pool or Pool-Keep).
The user must be online to view, accept, or start a Task in the pool. Once transferred, the Task will appear in the Pool Task list immediately. However, its related information will only become available after synchronization is complete.
Any changes made to a task after it has been accepted or started are synced to other users during the next batch synchronization.
While accepting a Task from the pool, the user has the possibility to set Allocated Start and Allocated Finish dates for the assignment.
The configurable visibility rules are administrated on the Mobile Configuration Parameters page, found in the Mobile for Service navigator in IFS Cloud Web. The page holds one configuration record that applies to the whole installation; the settings are switched on the record and records cannot be added or removed.
Note: These configurations are only available for Request Work Tasks.
The page contains the following settings:
| Setting | Options | Default | Description |
| Match Task Attributes to Resource | Service Organization, Delivery Unit, User Access Groups Only | User Access Groups Only | Selects which organizational attribute of the task must match the resource for the resource to receive the pool task. With the default option, no organizational matching is performed and only the access rules described above apply. |
| Match Task Region to Resource Region | On/Off | Off | When enabled, a pool task with a region is only made available to resources connected to that region. Regions for resources are defined under Scheduling Resource Regions and the region of the task location is defined under Location/Scheduling Details. |
Note: The Match Task Region to Resource Region setting is only available when the Scheduling component is installed, since both resource regions and task location regions are defined in Scheduling.
The organization matching uses the Owning Service Organization and Owning Delivery Unit defined on the resource. On the task, the Service Organization is always set, while the Delivery Unit and the Region are optional. A resource may be connected to multiple regions.
A resource receives a pool task when the resource has access to the task, the organization matching passes or is skipped, and the region matching passes or is skipped. Matching is skipped when there is nothing to compare — for example when the task has no Delivery Unit or no Region, or when the option is not enabled.
The Service Organization of the task is matched to the Owning Service Organization of the resource. The Delivery Unit is not used for matching in this mode.
| Task Service Organization | Resource Owning Service Organization | Result |
| Always set | Same as the task | Resource receives the task |
| Always set | Blank | Resource does not receive the task |
| Always set | Different from the task | Resource does not receive the task |
The Delivery Unit of the task is matched to the Owning Delivery Unit of the resource. The Owning Service Organization is not used for matching in this mode, but the access rules still apply.
| Task Delivery Unit | Resource Owning Delivery Unit | Result |
| Blank | Any | Matching is skipped — the task is available to resources that fulfill the other rules |
| Set | Same as the task | Resource receives the task |
| Set | Blank | Resource does not receive the task |
| Set | Different from the task | Resource does not receive the task |
Region matching is independent of the organization matching and can be combined with any of the three options.
| Match Task Region | Task Region | Resource Regions | Result |
| Off | Any | Any | Matching is skipped |
| On | Blank | Any | Matching is skipped |
| On | Set | Include the task region | Resource receives the task |
| On | Set | Do not include the task region | Resource does not receive the task |
| On | Set | No regions connected | Resource does not receive the task |
| Match Task Attributes to Resource | Match Task Region | What is enforced |
| User Access Groups Only | Off | Access rules only — this is the default and corresponds to the previous behavior |
| User Access Groups Only | On | Region matching only |
| Service Organization | Off | Owning Service Organization matching |
| Service Organization | On | Owning Service Organization and region matching |
| Delivery Unit | Off | Owning Delivery Unit matching |
| Delivery Unit | On | Owning Delivery Unit and region matching |
When transferring work to mobile, the Transfer to Mobile assistant supports the pool visibility filters. The Pool Work Filters section of the assistant is hidden by default and is displayed when one of the pool options (Pool or Pool-Keep) is selected.
The pool audience of a task is determined when the task is transferred to the pool. If configuration parameters or master data affecting visibility are changed afterwards — for example organization assignments, region connections, access groups, or a resource's mobile user settings — the pool tasks already in the pool can be refreshed using a database task, which re-evaluates the visibility rules and updates the pool task list available to the technicians.
| Database Task Name | Description |
| Refresh Pool Tasks | Re-evaluates the visibility and filtering rules for tasks currently in the pool and updates which mobile users the tasks are available to. Schedule this task to run after changes to default parameters or master data that affect pool task visibility. |