Client Assignment
Last updated
Last updated
The Client Assignment can be configured under Rollout -> Client Assignment, by Users who are at least Rollout Manager.
This feature is only available in Enterprise Rollout projects.
On the Client Assignment page, all Inventories within the Rollout are listed with an indicator, whether or not an Client Assignment is active.
By selecting an Inventory, the corresponding Client Assignment configuration page opens up. For a new Project, the Assignment is disabled, i.e. empty.
Its possible to further refine the Configuration by adding Client Groups per Workflow Status by using the + Client Group button.
In the resulting modal, Client Groups can be selected.
After confirming the Client Groups with the Add button, the Client Assignment Configuration displays every Group as a seperate box within a Status.
To remove Client Groups from a status, simply press the x button.
The boxes within the Configuration can be filled by simply utilizing drag & drop, choosing the responsible Users from the right-hand side Technicians table.
Each User can be responsible for several Groups within one Status.
After finishing the Client Assignment Configuration it must be saved using the Update Assignment button.
In the resulting modal, the User has the choice between simply saving the Configuration or choosing between the two additional options:
Update assignees immediately after saving
All Clients without Assignee will immediately get assigned according to the Configuration.
Override already assigned clients
Without any of the additional options, the Configuration will take effect upon all future Status changes.
The Reset button will return the Configuration to its empty state.
The Clients get distributed according to the Configuration evenly between all responsible Technicians. For 3 Technicians responsible this would mean on Status change:
Client A -> Technician 1
Client B -> Technician 2
Client C -> Technician 3
Client D -> Technician 4
and so on...
In the exemplary Configuration above, the following Assignees result:
Management
Technician_1
Management, Finance & Controlling
Technician_1
Finance & Controlling
Technician_3
Human Resources, Finance & Controlling
Technician_2
Management, Human Resources, Finance & Controlling
Technician_1
Assignee mapped
Assignee as in the source
Assignee not mapped
Assignee as in the Configuration
Assignee mapped but no value in the source
No Assignee (Assignee as in the source)
Assignee mapped but invalid value in the source
Import fails
If Keep assignee is checked, the Assignee won't change upon moving, regardless of the selected Status
If Keep assignee is unchecked, the Assignee will be decided based on the Configuration in place and according to the selected Status
For all changes through the Client Assignment, both the old and the new Assignee receive corresponding Notifications. These Notifications display the System as responsible for the change:
The Client Assignment Configuration reflects the Inventory's and all Users who are at least Technician and assigned to the Rollout.
All Clients - with or without Assignee - will immediately get (re-)assigned according to the Configuration. This can be conveniently used to remove all Assignees by first resetting the Configuration and then executing this option.
It is possible that one Client is part of several Client Groups, that are also part of our Client Assignment Configuration. In this case, the Assignment is determined by the highest in order.
The also determines the graphical arrangement in the Client Assignment Configuration's Workflow status columns.
are always set to the first Status, and will get assigned to a Technician according to the Configuration in place.
For , several outcomes are possible, depending on data-source and mapping.
When into an Inventory with an active Assignment, the User must decide whether or not to keep the previous Assignee.
The same applies to the various :
