Content
View differences
Updated by Dominic Bräunlein about 1 year ago
**Needs clarification:**
* **Which clarification first: Do we want to support only 2 variations, "default" and "short" (Prozesskennung) or should we support multiple different formats are needed and wanted by users.**
<br>
use a drop down right from the beginning?**
**As** an admin
**I want to** select from different display formats for hierarchies
**so that** i can adjust it based on the use case
**Acceptance criteria**
* A select with different formats is displayed
* The select has following formats
* tbd
<br>
**Technical notes**
* Some formats like "Process identification" will need to change the "short identifier" of a hierarchy item a required field. <br>
**Permissions and visibility considerations**
* Administrators _To whom is this feature visible?_
* This feature _When is part of admin settings
<br> it not visible?_
**Out of scope**
* Custom formats
* Project specific formats. Explanation: It will be not possible to have one custom field of type hierarchy and display that one custom field in different formats based on project or usage. <br>
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/331377/content">
* **Which
<br>
**I want to** select from different display formats for hierarchies
**so that** i can adjust it based on the use case
**Acceptance criteria**
* A select with different formats is displayed
* The select has following formats
* tbd
* Some formats like "Process identification" will need to change the "short identifier" of a hierarchy item a required field.
**Permissions and visibility considerations**
* Administrators
* This feature
<br>
**Out of scope**
* Custom formats
* Project specific formats. Explanation: It will be not possible to have one custom field of type hierarchy and display that one custom field in different formats based on project or usage.
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/331377/content">