We are happy to announce that we released the “Documents” application as part of SAP Cloud ALM for implementation! Our goal is to provide functionality to easily create, manage, track, and re-use documentation within SAP Cloud ALM as your central source of truth for all your solutions.
So, let’s discover what this application offers.
SAP Cloud ALM offers already many capabilities to manage the complete application lifecycle of your solutions. However, capabilities to manage the related documentation were limited. It was already possible to capture Notes attached to Solution Processes or document information as part of Requirements, Tasks, Features etc. But what was missing so far was a holistic approach for your documentation, during the project, as well as once the project is completed.
This will now change with the central “Document” element. Incrementally, the relations to existing SAP Cloud ALM elements will be made available. Starting with the relation to the Solution Process, followed by the possibility to relate Documentation to Requirements, User Stories, Tasks, Test Cases, and Features.
Thus, you can attach Documentation wherever needed, but still have the option to manage all Documents centrally in the new “Documents” application.
The Documents application lists all your documentation in one central place. You can filter and group them by owner, status, change date, editing status, etc. and use the known functionality to create your own views on filtered documents lists, share these views with other project members or create a tile on your launchpad for easy access.
The filtered list of documents can also be exported to a spreadsheet from here.
To create a new Document, you can start directly in the Documents app by clicking on “Create” and the new editor window will open.
Give your document a title and use the rich text editor to start documenting. You have the option to copy content from other sources, use lists, tables and links. The option to insert graphics will follow soon.
Under ‘Additional Information’ you can find the context information of the document, e.g., the Project it is created in.
You can select the document Status from the following values:
By default, the name of the creator is taken over as the ‘Owner’ of the document.
Further administrative data is captured automatically like ‘Created By/On’ as well as ‘Changed By/On’.
The general idea is that for cloud solutions documentation should be created directly in SAP Cloud ALM to prevent the storing of external documents. Therefore, we will release more and more functionality over time, to make this very convenient and easy to manage and extract. However, we understand that the management of external documents (like MS word Docs, PPTs, PDFs) is also required. For those external content, we provide the capability to link them into Documents objects using the ‘References’ option.
Here you can maintain the URL where the external document is located and name the reference. You can create, maintain, and delete references, plus download the reference list.
Soon, we will provide more capabilities to manage external documents – so stay tuned!
As mentioned above, the ‘Document’ element can be related to Solution Processes. This can be maintained under ‘Relations’, selecting one or more Solution Processes the Document belongs to. This becomes even more important when you want to track documentation completeness. As a planned capability soon, you will then be able to see the related documents in the Solution Process Traceability app.
When creating documentation online, it is crucial that we prevent any data loss. To ensure this, we use a draft versioning concept from SAP Fiori Elements.
The main purpose of drafts is to prevent data loss and to enforce an exclusive lock for draft owners. This is ensured in the following ways:
Drafts are continually saved in the background, regardless of whether all required fields have been filled. However, auto-saved drafts are not the same as actively saved documents. If you want to release an object as an active document, you must still save it explicitly so all users can see your changes. Only then an ID is given to the Document element.
In the future we also want to offer more versioning functionalities for Documents in SAP Cloud ALM.
The Notes functionality was introduced in the early beginnings of SAP Cloud ALM. By providing the new Documents capabilities, we will migrate the Notes into the Documents app. This will be done incrementally:
As you know already, we deliver new functionality to our customers frequently. And we have great plans for the Documents app to be extended. So, what to expect for this year and beyond?
First, as mentioned before, we will make documents available in the Solution Process traceability analytics application. Then, we plan to offer the assignment of Documents to the Process Hierarchy. Next to Solution Processes, we want to offer the relation to Requirements, Tasks, and Test Cases.
We are working on Document Types to distinguish between the various document purposes.
And we would like to offer the integration to SAP BTP Document Management Service to manage external documents following the SAP Harmonised Documentation Approach.
Also, APIs and export-import mechanism are on our list.
So please stay tuned and have a look into our roadmap.
So, let’s discover what this application offers.
New Document element
SAP Cloud ALM offers already many capabilities to manage the complete application lifecycle of your solutions. However, capabilities to manage the related documentation were limited. It was already possible to capture Notes attached to Solution Processes or document information as part of Requirements, Tasks, Features etc. But what was missing so far was a holistic approach for your documentation, during the project, as well as once the project is completed.
This will now change with the central “Document” element. Incrementally, the relations to existing SAP Cloud ALM elements will be made available. Starting with the relation to the Solution Process, followed by the possibility to relate Documentation to Requirements, User Stories, Tasks, Test Cases, and Features.
Thus, you can attach Documentation wherever needed, but still have the option to manage all Documents centrally in the new “Documents” application.
Documents application
The Documents application lists all your documentation in one central place. You can filter and group them by owner, status, change date, editing status, etc. and use the known functionality to create your own views on filtered documents lists, share these views with other project members or create a tile on your launchpad for easy access.
The filtered list of documents can also be exported to a spreadsheet from here.
Create Documents
To create a new Document, you can start directly in the Documents app by clicking on “Create” and the new editor window will open.
Give your document a title and use the rich text editor to start documenting. You have the option to copy content from other sources, use lists, tables and links. The option to insert graphics will follow soon.
Under ‘Additional Information’ you can find the context information of the document, e.g., the Project it is created in.
You can select the document Status from the following values:
- ‘In Progress’ (Default Value) – You are still working on the document.
- ‘In Review’ – The document is ready, but not yet released.
- ‘Released’ – The document is completed.
By default, the name of the creator is taken over as the ‘Owner’ of the document.
Further administrative data is captured automatically like ‘Created By/On’ as well as ‘Changed By/On’.
References
The general idea is that for cloud solutions documentation should be created directly in SAP Cloud ALM to prevent the storing of external documents. Therefore, we will release more and more functionality over time, to make this very convenient and easy to manage and extract. However, we understand that the management of external documents (like MS word Docs, PPTs, PDFs) is also required. For those external content, we provide the capability to link them into Documents objects using the ‘References’ option.
Here you can maintain the URL where the external document is located and name the reference. You can create, maintain, and delete references, plus download the reference list.
Soon, we will provide more capabilities to manage external documents – so stay tuned!
Relations
As mentioned above, the ‘Document’ element can be related to Solution Processes. This can be maintained under ‘Relations’, selecting one or more Solution Processes the Document belongs to. This becomes even more important when you want to track documentation completeness. As a planned capability soon, you will then be able to see the related documents in the Solution Process Traceability app.
Draft Handling
When creating documentation online, it is crucial that we prevent any data loss. To ensure this, we use a draft versioning concept from SAP Fiori Elements.
The main purpose of drafts is to prevent data loss and to enforce an exclusive lock for draft owners. This is ensured in the following ways:
- When an editing activity is interrupted, or when the app closes unexpectedly, unsaved changes are kept, so editing can be resumed later, and on a different device.
- A draft works as a locking mechanism to prevent multiple users from editing the same document simultaneously. Therefore, changes can only be made sequentially.
- The locking mechanism expires if the draft owner has been inactive for some time. This ensures that other users aren’t locked out indefinitely. When they start editing the document, they are made aware of the fact that there are unsaved changes by another user, so the changes aren’t lost accidentally.
Drafts are continually saved in the background, regardless of whether all required fields have been filled. However, auto-saved drafts are not the same as actively saved documents. If you want to release an object as an active document, you must still save it explicitly so all users can see your changes. Only then an ID is given to the Document element.
In the future we also want to offer more versioning functionalities for Documents in SAP Cloud ALM.
Notes vs. Documents
The Notes functionality was introduced in the early beginnings of SAP Cloud ALM. By providing the new Documents capabilities, we will migrate the Notes into the Documents app. This will be done incrementally:
- The new Documents app is available – Notes are still available.
- Notes will be migrated to Documents at one point in time – more information will follow.
- The Notes application will be sunset.
Outlook & Roadmap
As you know already, we deliver new functionality to our customers frequently. And we have great plans for the Documents app to be extended. So, what to expect for this year and beyond?
First, as mentioned before, we will make documents available in the Solution Process traceability analytics application. Then, we plan to offer the assignment of Documents to the Process Hierarchy. Next to Solution Processes, we want to offer the relation to Requirements, Tasks, and Test Cases.
We are working on Document Types to distinguish between the various document purposes.
And we would like to offer the integration to SAP BTP Document Management Service to manage external documents following the SAP Harmonised Documentation Approach.
Also, APIs and export-import mechanism are on our list.
So please stay tuned and have a look into our roadmap.
- SAP Managed Tags:
21 Comments
