New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ability to save PDF to the database #3739

Open
ebruchez opened this Issue Sep 14, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@ebruchez
Collaborator

ebruchez commented Sep 14, 2018

Currently, you produce a PDF with a process triggered by a button, such as a "Submit" button. But Orbeon Forms doesn't support saving the resulting PDF to the database. If the PDF is required at a later time, a service call is needed, which might hit a newer version of the form definition, for example. So an option to store the PDF to the database would be good.

Thoughts:

  • Q: Do we need a new database table?
    • We cannot store this in the current orbeon_form_data, as there is only an XML column.
    • We could add a BLOB column, but…
    • It is now possible to create multiple PDF outputs with different PDF templates, as well as TIFF output, and in the future, there might be more (rendered documents).
    • So I think that we do need a separate database table, like orbeon_rendered.
  • Q: How would you get back the data?
    • It does make sense to associate it to the document id.
    • We keep versions as we do now for the data (audit trail).
    • When retrieving the document, you need the document id and the generated format type ("pdf", "pdf template with name foo", "tiff", etc.).
    • An API must be exposed.
  • A new process action is needed to create and store a rendered document.
  • With send, there should be an option to use an existing stored rendered document.
    • "Render", "store", "retrieve" and "send" should be orthogonal.

+1 from customer

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment