# Process

A process is the link between entities in fulfillmenttools. Each order, pick job, handover job, and so on, references a process, and each process maintains the IDs of its entities. Furthermore, the process includes the statuses of the domains, modules, and entities.

{% hint style="warning" %}
The expression domain for the fields in the process class is not correct. Correct is module instead of domain. This will be fixed in the future.
{% endhint %}

Some fields of the process class:

```json
{
    "id": "111-222-333",
    // ...
    "pickJobRefs": [],
    "handoverJobRefs": [],
    // ...
    "status": "CREATED",
    "domsStatus": "CREATED",
    "returnStatus": "NOT_AVAILABLE",
    "operativeStatus": "CREATED",
    "domainStatuses": [
        "PICKING": "CREATED",
        // ...
    ],
    "lastDomainEntityStatuses": [
        {
            "domain": "PICKJOB",
            "status": "CREATED",
            "entityId": "123456789"
        },
        // ...
    ]
    // ...
}
```

## Process statuses calculation flow

The different status of the process are calculated depending on their predecessors. The start status is the `lastDomainEntityStatuses` (at the bottom in the image), with this the `domainStatuses` are calculated. `domsStatus` and `operativeStatus` are calculated from the `domainStatuses`. The final overall `status` based on `domsStatus` and `operativeStatus`.

<img src="https://4170739437-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLrrr5jgTsDuR38gNJIrm%2Fuploads%2FoYjL02sUtkz9dDggqdVR%2Ffile.excalidraw.svg?alt=media&#x26;token=0eeb56ce-81ac-4699-b217-f006360adbe8" alt="" class="gitbook-drawing">

## Description of different status

fulfillmenttools contains different domains and modules. Every domain has multiple modules, and every module includes entities like a `pickJob` in the `PICKING` module or a `routingPlan` in the `ROUTING` module.

For the different Process-Status-Calculation, only the `DOMS` and `LOCAL OPERATIONS` modules are taken into account.

<img src="https://4170739437-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLrrr5jgTsDuR38gNJIrm%2Fuploads%2Ft4x3R1fiEUs7tbTr9VUG%2Ffile.excalidraw.svg?alt=media&#x26;token=c0d97f5d-463a-4117-8372-96a192cd7756" alt="" class="gitbook-drawing">

### `lastDomainEntityStatuses`

Contains only the last status of every entity. An entity (for example, `routingPlan`, `pickJob` or `handoverJob`) status change in a module (for example, `PACKING` or `ORDER`), will update the entry of the corresponding entity in this list.

Example JSON:

```json
"lastDomainEntityStatuses": [
    {
        "domain": "ROUTING_PLAN",
        "status": "FINISHED",
        "entityId": "ROUTING-A-0000-1111"
    }, {
        "domain": "ROUTING_PLAN",
        "status": "FINISHED",
        "entityId": "ROUTING-B-0000-1111"
    }, {
        "domain": "PICKJOB",
        "status": "CREATED",
        "entityId": "PICK-A-2222-3333"
    },
    // ...
]
```

Because the noticed status in `lastDomainEntityStatuses` must work with all entities from different modules, these saved status are not the original status that's defined in the module. The original status is mapped into one, which can be used across all modules.

### `domainStatuses`

Contains module clean statuses that will be calculated from the module entities from the `lastDomainEntityStatuses`. For example, we have one status for `PICKING` or `SHIPPING`.

Example JSON:

```json
"domainStatuses": [
    "ORDER": "FINISHED",
    "ROUTING_PLAN": "FINISHED",
    "PICKING": "CREATED",
    // ...
]
```

The status enum type is the same like in `lastDomainEntityStatuses`, `DomainStatus` and can be found in our [REST API documentation](https://fulfillmenttools.github.io/fulfillmenttools-api-reference-ui/#get-/api/processes/-processId-).

### `domsStatus`, `operativeStatus`, and `inventoryStatus`

Each of these three statuses contains a clear domain status. For the calculation of these three statuses, the associated module statuses from the `domainStatuses` list are taken.

### `status`

This is the overall `status`, and it will be calculated with the three status `domsStatus`, `operativeStatus` and `inventoryStatus`.

### `returnStatus`

This status tracks the progress of returns associated with this order. As long as no returns are in progress, this status will be `NOT_AVAILABLE`. Contrary to other process status like `domsStatus` or `operativeStatus`, the `returnStatus` does not influence the overall status of the process. This is because an order is counted as complete once all its items are shipped. If a return is issued later on, the progress should not be reopened. The process will remain `CLOSED`, only its returns will be `IN_PROGRESS`.