Content
View differences
Updated by Oliver Günther 6 months ago
**As** a project manager
**I want to** have important project documents archived at a central place
**so that** I can access them when needed
**Acceptance criteria**
Project settings:
* A project UI
* An admin can select a project storage or as attachments to be used for the project artefact archive
Creation wizard
* When a project storage has been configured to be used for the artifact
* And the user submits the project wizard / initiation request
* The work package created has a file link to the PDF created
<br>
* When attachments have been configured to be used for the artifact
* The work package created as an internal attachment to the PDF
**Technical notes**
* Upload Service / Command
* The upload command takes following arguments
* File name
* File Path
* Read-only flag
* File
* When the file path does not exist yet, the folders are created on demand
* The file is uploaded
* File names and folders are modified to work with the storage's naming restrictions.
<br>
**Workflow**
* Prerequisite
* Project artefact archive is enabled in the wizard settings
* Trigger
* Work package status change
<br>
* \-> A pdf is created based on the project initiation request
* \-> PDF is saved as "Project Folder" -> "Project artefact archive" -> "Project initiation" -> "Project initiation request.pdf"
<br>
<br>
**Technical notes**
* <br>
**Permissions and visibility considerations**
* _To whom is this feature visible?_
* _When is it not visible?_
**Translation considerations**
* _Key terms and phrases in the key languages_ languages_
**Out of scope**
* <br>
_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the changes._
**I want to** have important project documents archived at a central place
**so that** I can access them when needed
**Acceptance criteria**
Project settings:
* A project
* An
Creation wizard
* When a project storage has been configured to be used for the artifact
* And the user submits the project wizard / initiation request
* The work package created has a file link to the PDF created
<br>
* When attachments have been configured to be used for the artifact
* The work package created as an internal attachment to the PDF
**Technical notes**
* Upload Service / Command
* The upload command takes following arguments
* File name
* File Path
* Read-only flag
* File
* When the file path does not exist yet, the folders are created on demand
* The file is uploaded
* File names and folders are modified to work with the storage's naming restrictions.
**Workflow**
* Prerequisite
* Project artefact archive is enabled in the wizard settings
* Trigger
* Work package status change
<br>
* \-> A pdf is created based on the project initiation request
* \-> PDF is saved as "Project Folder" -> "Project artefact archive" -> "Project initiation" -> "Project initiation request.pdf"
<br>
<br>
**Technical notes**
* <br>
* _To whom is this feature visible?_
* _When is it not visible?_
**Translation considerations**
* _Key terms and phrases in the key languages_
**Out of scope**
* <br>
_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the changes._