Content
View differences
Updated by Dominic Bräunlein about 1 year ago
### User pain
**Example: Gap analysis**
A project manager (PM) in openDesk to a gap analysis from their 10 vendors. She creates a work package for each vendor and assigns it to the responsible person.
**Example: Software specification file** <br>
Request for changes -> Software documentation document <br>
**Example: Employment contract** <br>
First, a employment contract will be generated. Then it can be used for many employees. <br>
**Example: Attachements?** Software specification file
<br>
### Solution
The new documents
<br>
### Component Overview
<br>
Document Module
Document Object
Document Workflows
<br>
### User journeys
**Example: Gap analysis**
A project manager (PM) in openDesk to a gap analysis from their 10 vendors. PM clicks on the module document to create a template for the analysis. She chooses the document type "Vendor document" that an instance administrator (IA) configured beforehand.
\--- (Document type setup)
IA did set up a "Vendor document" in the admin settings some weeks ago. He did so because vendors need to provide openDesk with documents regularly. So he created a document type that has additional meta-data attached that can be useful for a document workflow. In this case it is a field called "Vendor", a list with all vendors to identify easily who created the document.
Additional IA added a custom workflow, by adding the statuses "Submitted" and "Approved", as all vendor documents need to be reviewed approved by openDesk.
IA choose the "Text-based" type. This allows the vendors later to directly create and edit the documents in OpenProject.
\---
After choosing the document type, which defines the meta-data and the workflow of a document, now PM can add content to the template. She would: would:
* Add the name "Gap Analysis"
* Add some informations and instructions in the description field.
* Add a structure of the gap analysis to help vendors understand the expectations and to keep the results organised.
* Save the template.
She would share the template to all vendors and ask them to please create their document
<br>
Software specification
For Admins
For Users
**Example: Gap analysis**
A project manager (PM) in openDesk to a gap analysis from their 10 vendors. She creates a work package for each vendor and assigns it to the responsible person.
**Example: Software specification file**
Request for changes -> Software documentation document
**Example: Employment contract**
First, a employment contract will be generated. Then it can be used for many employees.
**Example: Attachements?**
<br>
### Solution
The new documents
<br>
### Component Overview
<br>
Document Module
Document Object
Document Workflows
<br>
### User journeys
**Example: Gap analysis**
A project manager (PM) in openDesk to a gap analysis from their 10 vendors. PM clicks on the module document to create a template for the analysis. She chooses the document type "Vendor document" that an instance administrator (IA) configured beforehand.
\--- (Document type setup)
IA did set up a "Vendor document" in the admin settings some weeks ago. He did so because vendors need to provide openDesk with documents regularly. So he created a document type that has additional meta-data attached that can be useful for a document workflow. In this case it is a field called "Vendor", a list with all vendors to identify easily who created the document.
Additional IA added a custom workflow, by adding the statuses "Submitted" and "Approved", as all vendor documents need to be reviewed approved by openDesk.
IA choose the "Text-based" type. This allows the vendors later to directly create and edit the documents in OpenProject.
\---
After choosing the document type, which defines the meta-data and the workflow of a document, now PM can add content to the template. She would:
* Add the name "Gap Analysis"
* Add some informations and instructions in the description field.
* Add a structure of the gap analysis to help vendors understand the expectations and to keep the results organised.
* Save the template.
She would share the template to all vendors and ask them to please create their document
<br>
Software specification
For Admins
For Users