POC: Click on Template file -> Create Document (Web, Backend, mobile, desktop)

[tbsbdr]

Description

User Stories

• As a user I want to create a document by clicking on a template file so that I can use the templates from a shared folder.

Acceptance Criteria

• click on a template file eg. letter.ott creates a new writable document letter.odt, new document gets opened
• Supported file formats:
  • Must:
    • DOTX
    • OTT
  • Nice to have:
    • XLTX
    • POTX
    • OTS
    • OTP
• the document gets implicity saved to the users personal space: letter.odt; [Name of template].[corresponding ext]
• filename collisions are implicitly solved: letter (1).odt
• provide the location of letter (1).odt so that clients can show a notification where the file got stored (in personal)

also see https://github.com/ONLYOFFICE/DocumentServer/issues/2839

Definition of ready

• [ ] Everybody needs to understand the value written in the user story
• [ ] Acceptance criteria have to be defined
• [ ] All dependencies of the user story need to be identified
• [ ] Feature should be seen from an end user perspective
• [ ] Story has to be estimated
• [ ] Story points need to be less than 20

Definition of done

• Functional requirements
  • [ ] Functionality described in the user story works
  • [ ] Acceptance criteria are fulfilled
• Quality
  • [ ] Code review happened
  • [ ] CI is green (that includes new and existing automated tests)
  • [ ] Critical code received unit tests by the developer
• Non-functional requirements
  • [ ] No sonar cloud issues
• Configuration changes
  • [ ] The next branch of the ocis charts is compatible

[butonic]

hm, how do other solutions like collabora and ms solve this?

[micbar]

Needed Changes in Web and oCIS

app/list/

• We will add a field target_ext=<extension> to indicate which extension should be used by the new file

app/open

• We will add the template_id to provide a way to tell the OfficeApp which template to process. The template_id will only be used if the file is empty.

Background: It is important that the template is processed by the Web App to execute the field functions and other stuff.

Web Client

• Web Client reads the target_ext field from the app/list response.
• Files with that flag will trigger a new default action, which is "open a new file from this template" (new web extension inside of external-app)
• The existing file action "Open this File in ..." will stay and can be used via right click.

New default action "open a new file from this template"

• It asks the user about the new file name in the personal space root (collision handling included, no personal space means "feature not available")
• It will create a new file via app/new using the suggested file extension
• It uses the new file to switch the current context
• It will open the new file via app/open and send the template_id

[micbar]

@kulmann backend has been merged.

[kulmann]

@kulmann backend has been merged.

nice! :heart:

[saw-jan]

API tests: https://github.com/owncloud/ocis/issues/10367 WebUI tests: https://github.com/owncloud/web/issues/11811