# March 15 - Position Library Feature

{% embed url="<https://www.loom.com/share/53974bc26f82433da5b46379f8269a1e?sid=1c98f26c-6b7d-46cb-8071-ae5ddb4757fe>" %}

**New feature:** Art Library

* Now, art team are going to have a way of re-use existing positions and use an unique identifier across the entire platform.
* A position can be added to the art library from the design view and an universal position ID is going to be assigned to it.
* A position can be removed from the art library from the design view as well
* A position can be created from the art library in the design view
* &#x20;An universal position ID can be now searched in the production queue view<br>

**Improvements and bugfixes:**

* Added product style name into the product/garment description
  * Now these output files are going to include the product style within the product name as a suffix:
    * Oder Invoices
    * Art Approvals
    * Press Instructions
    * Packing Slips
    * Distribution Manifest
    * Carton Label
* Refactored schedule board's timer behavior
  * Now, before starting another position we check if there's one already running in the press and if there is we throw an alert saying if we want to stop the other card and proceed with starting the new one
* Refactored schedule board's machine view
  * Now the the machine view is going to handle duplication and timer features
  * Scrolling within a lane was fixed
* Fixed BUG when editing API 2024 products and setting 0 total units for a specific color

\
**Time Savings:** &#x20;

* **Art Team Savings per year: 69 days**
* **AE/AM Team Savings per year: 22 days**


---

# Agent Instructions: 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:

```
GET https://docs.culturestudio.com/release-notes/decorator-platform/march-15-position-library-feature.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
