Feature Wiki
Tabs
WOPI: Create empty Documents
Page Overview
[Hide]- 1 Initial Problem
- 2 Conceptual Summary
- 3 User Interface Modifications
- 4 Additional Information
- 4.1 Involved Authorities
- 4.2 Technical Aspects
- 4.3 Privacy
- 4.4 Security
- 4.5 Contact
- 4.6 Funding
- 5 Discussion
- 6 Implementation
- 6.1 Description and Screenshots
- 6.2 Test Cases
- 6.3 Privacy
- 6.4 Approval
1 Initial Problem
If an online editor is configured, existing files can be opened and edited with it. This feature should make it possible to edit new, empty documents together.
2 Conceptual Summary
The options for creating a new file object have been extended to include a new option: Create empty document.

All options supported by the connected WOPI editor are offered.
3 User Interface Modifications
3.1 List of Affected Views
- Creation Dialog for new Files in Repository
3.2 User Interface Details
The existing file input is moved to a switchable group and displayed by default. In a second group (radio option), it is possible to create a blank document.
3.3 New User Interface Concepts
The feature is implemented with existing UI components and does not introduce any new UI concepts.
3.4 Accessibility Implications
The use of existing UI components does not introduce any new implications for accessibility.
4 Additional Information
4.1 Involved Authorities
- Authority to Sign off on Conceptual Changes: Schmid, Fabian [fschmid]
- Authority to Sign off Code Changes: Schmid, Fabian [fschmid]
If this request is related to multiple components, please list both authorities for all related components.
4.2 Technical Aspects
To create new documents, WOPI uses the `editnew
` actions. These must also be taken into account by the crawler and then provide the information for which file types the editor supports the creation of new files.
Furthermore, the WOPI endpoint must now support the 'PutFile' operation: https://learn.microsoft.com/en-us/microsoft-365/cloud-storage-partner-program/rest/files/putfile
4.3 Privacy
No new personal data is collected or processed as a result of the implementation of the feature.
4.4 Security
The implementation of the feature does not introduce any new attack vectors. there are no further special security-related considerations to be made.
4.5 Contact
Person to be contacted in case of questions about the feature or for funding offers: Lorenz, Katharina [klorenz]
4.6 Funding
Funding status and funding parties are listed in the block 'Status of Feature' in the right column of this page.
If you are interested to give funding for this feature, please get into contact with the person mentioned above as 'Contact'.
5 Discussion
6 Implementation
Feature has been implemented by {Please add related profile link of this person}
6.1 Description and Screenshots
{ Description of the final implementation and screenshots if possible. }
6.2 Test Cases
Test cases completed at {date} by {user}
- {Test case number linked to Testrail} : {test case title}
6.3 Privacy
Information in privacy.md of component: updated at {date} by {user} | no change required
6.4 Approval
Approved at {date} by {user}.
Last edited: 14. Feb 2025, 15:55, Schmid, Fabian [fschmid]