> For the complete documentation index, see [llms.txt](https://docs.hesh.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hesh.app/manuals/production/production-page/production-page-view-options.md).

# Production page view options

## Overview

The production page offers three different views: **Plane view, Product view,** and **Order view.**

The main feature of the production page is the ability to switch between different views depending on whether the production is focused on products or orders. This flexibility allows users to adapt the page to their specific needs and manage workflows more efficiently.

By reading this article, learn how to navigate the production page and use different views to optimize your production management. You will also get an idea of the standard Plane view and how to switch between views depending on your production tasks.

## Production page view

The production page can change its view among **3 options**:

* Plane view
* Product view
* Order view

Plane view - view by default, which applies to every page reloading.

<figure><img src="/files/HepZGuXH7oTc5NhhaAuZ" alt=""><figcaption></figcaption></figure>

{% tabs %}
{% tab title="Order View" %}

### Order view

***Order view*** shows all productions grouped under one order.&#x20;

<figure><img src="/files/26WVybXyKzg7dkALU4Ck" alt=""><figcaption></figcaption></figure>

There can be different or the same productions within the same order. For example, you have a customer who ordered 5 dresses. Under this order, you will immediately see all 5 productions and their progress. The progress of the order will be the total percentage of readiness of each of the productions it includes.

**To open "Order View":**

1. Click on **"Production view"** button.
2. Choose **"Order View"**.
3. Expand all productions group by order.
4. Sort the displaying of productions.
5. Open **"More actions"** menu to manage the order.

   -Change order details\
   -Change client to the order

{% @arcade/embed flowId="53BSy9xuPJhPQ1mCjZT7" url="<https://app.arcade.software/share/53BSy9xuPJhPQ1mCjZT7>" %}

In **"More action"** menu you can also change order client. Change client for all production items in this order. All changes will be applied to its components as well.

{% hint style="info" %}
Changing the details of an order or a client works as bulk actions, i.e. changings will be applied to all productions with this order.
{% endhint %}
{% endtab %}

{% tab title="Product View" %}

### Producr view

***Product view*** shows all productions grouped by one product.

<figure><img src="/files/q0QO1Ny55O0UsdHeAXrh" alt=""><figcaption></figcaption></figure>

According to this view the system shows a list of all production items in alphabetical order A→Z, where productions of similar products (have the same product ID) are grouped together in one “grouped by product item”.

**To open "Production View":**

1. Click on **"Production view"** button.
2. Choose **"Production View"**.
3. Expand all productions group by order.
4. Click **"Show more"** to see all production grouped by product item.

{% @arcade/embed flowId="ay5WglrqsJj6BDoWOr1i" url="<https://app.arcade.software/share/ay5WglrqsJj6BDoWOr1i>" %}
{% endtab %}
{% endtabs %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.hesh.app/manuals/production/production-page/production-page-view-options.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.