# Moving Clients

{% hint style="info" %}
Rollouter enables `Technician+` to transfer Clients between [Inventories](https://rollouter.gitbook.io/guide/rollout-managers/setup/inventories) within the same Rollout.
{% endhint %}

***

## Moving a Client

This function can be accessed via the CDV[^1] or by utilizing the dedicated [Checklist step](https://rollouter.gitbook.io/guide/rollout-managers/setup/checklists/creating-a-checklist#checklist-step-types).\
Both approaches lead to the `Move Client` modal.

### On the CDV

In the [Client Detail View](https://rollouter.gitbook.io/guide/rollout-managers/working-with-clients/client-detail-view), the `Move Client` modal can be reached via the menu in the upper-right corner.

<figure><img src="https://750384937-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIeSHc7pNZWey2rD63q9j%2Fuploads%2FtdAqdGoieA39Wdl2D6Ie%2Fimage.png?alt=media&#x26;token=1581cc16-5f11-45ef-9606-66e0103f77a8" alt=""><figcaption></figcaption></figure>

### Via Checklists

In both the CDV[^1] and the [Client Dashboard](https://rollouter.gitbook.io/guide/rollout-managers/rollout-view/client-dashboards), the `Move Client` modal can be accessed via Checklist if the dedicated Checklist step is incorporated.

<figure><img src="https://750384937-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIeSHc7pNZWey2rD63q9j%2Fuploads%2FJ5LSUc1H7kLjpmMaxqMY%2Fimage.png?alt=media&#x26;token=9b7fa651-b78e-45a1-bccc-cb42bfb8085f" alt=""><figcaption></figcaption></figure>

***

## Move Client modal

In the resulting Client Moving modal the User must first specify, into which Inventory within the same Rollout the Device should be transferred.

<figure><img src="https://750384937-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIeSHc7pNZWey2rD63q9j%2Fuploads%2FVQSoIIA28eUjk4uUYizz%2Fimage.png?alt=media&#x26;token=0e80dc4e-5e41-4fe1-9a8a-a2e1405a8a18" alt=""><figcaption></figcaption></figure>

After this, the [Workflow](https://rollouter.gitbook.io/guide/rollout-managers/setup/workflows) Status in the destination has to be determined.\
The corresponding dropdown displays every Status of the Inventory chosen above.

<figure><img src="https://750384937-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIeSHc7pNZWey2rD63q9j%2Fuploads%2FtAMFq793MBb98pw2x9P1%2Fimage.png?alt=media&#x26;token=56bf6c9f-c719-46dd-8e15-db9f12cfdaf4" alt=""><figcaption></figcaption></figure>

Lastly the User must decide, which properties of the Client should be kept during the process.\
By default, all options are activated, except for `Keep assignee`.

The default status of `Keep assignee` depends on the target Inventory's [Client Assignment](https://rollouter.gitbook.io/guide/rollout-managers/rollout-planning/client-assignment).

* With an **active** Assignment the option will be **unchecked**
* With an **inactive** Assignment the option will be **checked**

<figure><img src="https://750384937-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIeSHc7pNZWey2rD63q9j%2Fuploads%2FnOsb9OJsR1tk3AfdcQtx%2Fimage.png?alt=media&#x26;token=6881a787-93bb-4ade-94d9-9452b87a955b" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
The CDV will only display the [Custom Fields](https://rollouter.gitbook.io/guide/rollout-managers/setup/custom-fields) that are specified by the new Inventory after moving.\
\
However, the values are stored and will appear as soon as the missing fields are added to the new Inventory.
{% endhint %}

{% hint style="info" %}
The Checklist progress is stored in all cases, even if the destination Inventory has a different Workflow.

If the Clients gets moved back into its original Inventory, the previous Checklist progress will be restored.
{% endhint %}

***

## Moving with active Client Assignment

When moving into an Inventory with an active Client Assignment, several outcomes are possible, depending on the Assignment in place and the Users choices in regards to the target Workflow Status and the "Keep Assignee" option.

| Moving Modal                                                                                                                                                                                                                                              | Client Assignment      | Outcome                                      |
| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------- | -------------------------------------------- |
| <img src="https://750384937-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIeSHc7pNZWey2rD63q9j%2Fuploads%2FxqJXRFTeyCivLU0B6qYe%2Fimage.png?alt=media&#x26;token=e3bae4ac-b4d4-4817-905a-186add1133ab" alt="" data-size="original"> | Inactive               | No Assignee                                  |
| <img src="https://750384937-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIeSHc7pNZWey2rD63q9j%2Fuploads%2FXuwwekyx4eUUpwUHLlLq%2Fimage.png?alt=media&#x26;token=05100481-dff0-4921-b6bd-efc4fe293554" alt="" data-size="original"> | Active & relevant      | Assignee determined by the Client Assignment |
| <img src="https://750384937-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIeSHc7pNZWey2rD63q9j%2Fuploads%2FS0FFLGzfnx6v00W8PojB%2Fimage.png?alt=media&#x26;token=fdafa1b4-6fb9-44e6-85b8-2ddb4e02d226" alt="" data-size="original"> | Active & not relevant  | No Assignee                                  |
| <img src="https://750384937-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIeSHc7pNZWey2rD63q9j%2Fuploads%2F6gkJliKsgn4YAbu2prKg%2Fimage.png?alt=media&#x26;token=8468da6a-d970-44d6-aa7d-3c5619484ac4" alt="" data-size="original"> | Inactive               | Assignee is kept                             |
| <img src="https://750384937-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIeSHc7pNZWey2rD63q9j%2Fuploads%2FwP9E5bDafDnVFpU2aRpu%2Fimage.png?alt=media&#x26;token=77e6c56e-aea0-4a0f-932c-a3be151b0c4d" alt="" data-size="original"> | Active & relevant      | Assignee is kept                             |
| <img src="https://750384937-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIeSHc7pNZWey2rD63q9j%2Fuploads%2Fmt1tJS1ICYkXffsIsXUh%2Fimage.png?alt=media&#x26;token=d26b908e-348f-4f36-a743-972c96322ee5" alt="" data-size="original"> | Active &  not relevant | Assignee is kept                             |

{% hint style="info" %}
In the tables context `relevant` means that not only an Assignment is in place, but the Client is also actually being affected.
{% endhint %}

### Special cases

#### Client Groups & Appointments

[Client Groups](https://rollouter.gitbook.io/guide/rollout-managers/working-with-clients/client-groups) and [Appointments](https://rollouter.gitbook.io/guide/rollout-managers/rollout-planning/appointments) are not selectable in the Moving modal, their behaviour is explained below.

| Object        | Moveable             | Explanation                                                                                                                                                                                                            |
| ------------- | -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Client Groups | :white\_check\_mark: | Client Groups will always be kept, since they are defined for a Rollout and not for a single Inventory.                                                                                                                |
| Appointments  | :x:                  | <p>Appointments will always be deleted, since they are defined for a specific Inventory.<br><br>Consequently, Appointments of the destination Inventory will get added to the Client, if the requirements are met.</p> |

#### Same Workflow in source & destination

In the case that both Inventories share the same Workflow, the Checklist progress will be displayed after moving, regardless of the Status the Client gets placed in.

[^1]: Client Detail View
