Content
View differences
Updated by Andrej Sandorf 1 day ago
**Acceptance criteria**
* Within a WorkPackage, the existing PDF export is extended to create artefacts of the PMflex process
* A new template entry "PMflex Artefact" in the export dialog
* PDF styling is the same as the PIA PDF
* Contents:
1\. Cover
2\. TOC
3\. Project attributes with sections (from the new tab)
4\. Work package attributes/custom fields with sections (from the work package configuration)
for sections, including embedded `related work package table` queries, list the work packages
* work package name
* work package fields (as defined in the table query)
* work package description (if any)
* all non-empty long text custom fields for that work package
tables
**Technical notes**
* PIA and the new PMflex export will share the same stylesheet file
**Out of scope (Follow ups)**
* Add specific export settings to the export dialog and/or type (e.g. treeview)
* Automatically upload to Nextcloud on status change
* Export of Activity/Change history
* Within a WorkPackage, the existing PDF export is extended to create artefacts of the PMflex process
* A new template entry "PMflex Artefact" in the export dialog
* PDF styling is the same as the PIA PDF
* Contents:
1\. Cover
2\. TOC
3\. Project attributes with sections (from the new tab)
4\. Work package attributes/custom fields with sections (from the work package configuration)
for
* work package name
* work package fields (as defined in the table query)
* work package description (if any)
* all non-empty long text custom fields for that work package
* PIA and the new PMflex export will share the same stylesheet file
**Out of scope (Follow ups)**
* Add specific export settings to the export dialog and/or type (e.g. treeview)
* Automatically upload to Nextcloud on status change
* Export of Activity/Change history