• Möglich: Ja

    Hallo Herr Eisen,

    theoretisch können Sie sehr viel mit zwei Workflows und einem WebService machen.

    Der Ablauf könnte so aussehen:

    1. Der Workflow wird so definiert, dass er täglich nach dem Auslaufdaum prüft. Für auslaufende Unterweisungen wird dann eine Instanz gestartet.
    2. Diese Instanz schickt dann bestimmte Indexdaten an einen Web Service (das kann nur eine DocID sein, oder auch gleich alle Indexeinträge, die auf dem neuen Dokument benötigt werden.
    3. Der Web Service generiert das Dokument (und holt sich eventuell noch fehlende Informationen über die übermittelte DocID) und legt das Dokument direkt wieder in DocuWare ab.
    4. Ein zweiter Workflow startet für das neue Dokument und schickt das Dokument per Mail an den Mitarbeiter.

    Ob es bereits irgendwo so einen Web Service gibt, kann ich IHnen leider nicht beantworten.

    Viele Grüße

    Tobias Getz



  • Some ideas

    There is currently no tool available from DocuWare that converts text files to PDF files. The only way would be to print them via DocuWare Printer, which is nothing automatic and probably not the way to got when having a lot of files.

    PDF conversion

    However there are a lot of applications available that can do the job and place the PDF file into a folder. For example this cheap utility: http://www.verypdf.com/app/text-to-pdf-converter/index.html.There is also a nice description how to do this from command line: http://www.verypdf.com/wordpress/201107/text-to-pdf-batch-conversion-using-wildcards-1022.html

    Index field

    After the conversion you can setup a DocuWare Import job to import the files. Depending on the structure of the EDI files you then might be able to read out the order number from the content of the PDF (maybe you need to use anchors). If this is not possible (e.g. because the order number is eventually at the end of a line and gets broken up), then you could write the full file name into an index field and then use Workflow Manager to split it into the correct field. Here is a description about this: https://www.docuware.com/forum/english-forums/docuware-questions-about-usage-and-configuration/arithmetic-expression-functions

  • Start trigger


    as file cabinets are mostly used for a lot of different types of documents, we are thinking, that the idea of starting the same workflow for all new documents is not the normal use case. This might be different in your use case but for most of our customers it is not.

    That´s why we decided to not have a generic trigger for all documents.

  • Vielen Dank

    Vielen Dank für den Hinweis. Ich habe das gerade überprüft. Mit der nächsten Version wird auch die Länge von Profilnamen geprüft wie es auch für Dialognamen oder Archivnamen bereits üblich ist.

  • Nummernkreise können nicht zurückgesetzt werden

    Hallo Herr Becher,

    eine der wichtigsten Kriterien der Nummernkreise ist, dass Nummern auf keinen Fall mehrmals vergeben werden. Deshalb können Nummernkreise leider nicht zurückgesetzt werden.

    Ich denke, dass Sie einen neuen Nummernkreis anlegen müssen.

  • Planned

    I am sorry, that you are missing this functionality so much. 
    We are adding the functionality to copy profiles to the next DocuWare release.

  • Import and Autoindex should be able to handle that

    An idea without having do write one line of code would be to use DocuWare Import to store the files in DocuWare and Autoindex to index them. You need to have a unique link between the PDF files and the data record in the CSV file.

    With DocuWare Import: The only index entry would be the file name (or maybe the directory name - depends on the exported file structure).

    Afterwards you can use Autoindex to add the index entries from your CSV file to the documents in the file cabinet.

  • Use with caution

    Hi Joe,


    please use the data in the database with caution. Never change anything in there. The database structure is just for internal DocuWare usage and might change with an update even without notice. 


  • Answers to versioning



    I understand your concern about not persisting this setting. Actually displaying the old versions in the same list as the current version was a workaround for not having this version overview mentioned in 3. This (newer) view of all versions for one document is much easier to understand and to use. In a future version we will probably only show the current version in the result list and the previous versions only in this separate view.

  • Answers to versioning

    Hi Joe,

    I tried to answer your questions below in italic.

    1. How efficient is storage for versions? As in, if I have a large document and make one small change, are the versions stored as differential layers as opposed to the whole file being saved multiple times? In other words, is it a bad idea to turn on versioning if the file cabinet is expected to house very large files with lots of changes? EDIT: Did some research on my server and all versions are the full file at the time, both in the database and in the file storage location. So versioning can definitely eat through disk space in a hurry.
      You are right, we store them as individual files.
    2. Is there any sort of "diff" utility to compare versions? Not sure how that would work since most documents are binary, but if I stored, say, text documents, is there a way to "diff" the versions without downloading them and using a diff tool?
      Currently there is no "diff" possible between different versions
    3. Is the only visible web client change related to versioning the "Hide/Show old versions" button in the result list toolbar? Is there any other way to cycle through older versions beside displaying all versions and finding the one you want in the result list (e.g. a navigation tool I am not seeing in the viewer that can cycle through)? I see that Result Lists and Search Dialogs can include the version-related fields, so that is nice.
      Additionally you have the functionality to show all versions in an additional result list. Therefore you use the context menu in the result list and use "Open document history". All versions up to the current one will then be displayed in one list. You should use this list when working with versions. 
    4. Is there a way to make the "Hide/Show old versions" setting remain persistent? I see that every time I do a search it starts in the "hidden" position. If we wanted to always see all versions, it seems like a pain to always have to toggle that button.
      There is no possibility to change the default status.