This is an interesting concept. Since Mayan was originally made to be used in government and legal setting, one of the philosophies was to keep the uploaded document intact. This is to preserve the chain of evidence.
In this case the possible solution we've come up with is to add new workflow actions to create a new document (PDF) based on a previously uploaded document (LaTex one) and then delete the previous document. This way there is a log of how the PDF was created and the upload process doesn't need to be customized. For this three workflow actions need to be created: A document delete action, one to call an external binary and another to the upload a new file as a document. More discussion is needed but just letting you know how far we are in the brainstorm. On Thursday, July 26, 2018 at 6:14:41 AM UTC-4, Dexter wrote: > > Hi All, > > Is it possible to perform a preprocess on uploaded document ? > > The idea is that we would like the sources of the documents to be uploaded > ( for example LaTeX files and projects), and make Mayan run the compiler > and generate a PDF. This PDF will be what is shown in the preview. > > Without this we must upload the PDF version, and find another system to > store the sources. We don't like the idea of using two tools to store > documents > > Thanks > -- --- You received this message because you are subscribed to the Google Groups "Mayan EDMS" group. To unsubscribe from this group and stop receiving emails from it, send an email to mayan-edms+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
