This is a very specific use case and the first time the idea of custom upload workflows is suggested. As such there are no provisions to substitute upload workflows.
My recommendation would be to implement document attachments in a separte app adding an Attachment model with a foreign key to the main DocumentVersion and a typical Django File field. The app would also need to provide a modified clone of the Source app document upload workflow to allow specifying the attachment file during document upload, unbind the core upload process and register its own instead. The "New document" upload process is just a view so changing it would be a matter of replacing the link, but uploading new document versions directly call the Source app reusable view. A system to replace upload workflows would be needed if this is to be merged into core. On Thursday, January 21, 2016 at 10:35:22 PM UTC-4, Rachael Sewell wrote: > > Currently, there is no notion of a document attachment. This is a must > have feature for my implementation of this application. After looking at > the Document and Sources models, I'm not sure this can be done as a custom > app. The attachments would need to be uploaded during the document creation > process, rather than adding them after the document has already been > created. I would also need the attachments to be on a per version basis > rather than per document. Is there a way to add to the Document and Source > views using a custom app or can this only be done within the Document and > Source app? > > Any pointers into where to start adding this new feature would be great. > Would this be a feature that could be pulled into the core applications? > > Rachael > -- --- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
