Simon H. Hellmann Toshiba Tec Germany Imaging Systems GmbH IT-Consultant Document Management Solutions

Hallo Daniel Reusch, 

mit der Dokumentenverknüpfung können maximal zwei Archive verknüpft werden. Natürlich ließen sich mehrere Verknüpfungen mit den gleichen Kriterien, aber unterschiedlichen Archiven einrichten.

Im Normalfall sollten die genannten Dokumenttypen aber alle im gleichen Archiv liegen, weshalb das gar kein Problem wäre.
Ansonsten ist das hier eher ein Anwendungsfall für die Funktion "Suche über mehrere Archive" (versteckt sich im WebClient unter "Suchen").

Gruß aus Neuss,
Simon H. Hellmann
DocuWare System Consultant

Hello Miquel Sanz Vargas,

for moving or copying files between different cabinets, you should use the transfer module.
Workflow can currently not do this without putting in a lot of effort.

Greetings from Germany,
Simon H. Hellmann
DocuWare System Consultant

Hello Miquel Sanz Vargas,

every search dialog has a linked result list. In file cabinet configuration, open the file cabinet -> dialogs -> search dialog -> scroll down -> more options. There is a drop-down menu to select the result list used by this search dialog. Either the result list set here was deleted - in that case, select another one.
Or the search dialog you are looking at has a different result list linked than you think and you do not have permissions on the result list shown here.

Hope that helps.

Greetings from Germany,
Simon H. Hellmann
DocuWare System Consultant

Hallo Stephan Buch,

Der Workflow ist normalerweise die praktischste Variante.
Eine Option wäre noch, ein Indexfeld auf Archivebene auf "Eindeutig" zu stellen - dann können beispielsweise keine zwei Dokumente mit derselben Belegnummer abgelegt werden. Sobald allerdings zwei Kreditoren mit sich überschneidendem Nummernkreis existieren, wird das zu einem Problem.

Die komplexere Lösung wäre einen Validierungsservice zu programmieren und in den Ablagedialog einzubinden.
Dieser REST Webservice erhält vom Ablagedialog beim Klick auf "Ablegen" alle erfassten Indexwerte, kann beliebigen Code mit diesen Werten ausführen und liefert dem Ablagedialog dann die Information zurück ob das Dokument so abgelegt werden kann oder nicht. Falls nicht, kommt auch noch eine Fehlermeldung mit.

Gruß aus Neuss,
Simon H. Hellmann
DocuWare System Consultant

Hi Thomas,

the VC++ 2015 is a known issue in that setup.
What happens if you use the 'sa' user instead? (given it is a MSSQL Database)
Did you run the database integrity check tool from setup components, does that work?

I recently had to upgrade a 10m documents System from 6.7 to 7.9 and had to move servers as well.

You work for TBS, is that right?
If so, feel free to contact me via mail or teams - I will try my best to help you.
You should find me in your global address book - I work for TGIS.

Greetings from Germany,
Simon H. Hellmann
DocuWare System Consultant
 

Hi Jon,

I would solve this with a combination of Autoindex and Workflow.
Create a date field on the document which has the expiration date, then do an Autoindex Job which triggers for documents where expiration date is in the past and have it run daily.
This sets a status field which triggers a workflow. (Yes I know that workflow also has a timer-based trigger, but in my experience this is very unreliable.)

The workflow then sends the E-Mail notification with a link to a public form.
Why should it matter if the destination mail address is internal or external?

Greetings from Germany,
Simon H. Hellmann
DocuWare System Consultant

Hi Jesús Fernández,

is there any particular reason why you are trying to migrate with custom programming instead of using the Transfer Module?
Transfer migrates everything (except document history), including annotations as far as I know.

Greetings from Germany,
Simon H. Hellmann
DocuWare System Consultant

Hello Gabriel Vazquez Martinez,

yes, you can run DocuWare on virtual machines. Hyper-V, ESXi etc. are all supported. However, public cloud spaces like AWS or Azure are not supported (though they might work fine if you only use a single-server environment, but no guarantees).

Hope this helps.

Greetings from Germany, 
Simon H. Hellmann
DocuWare System Consultant

Hello Michal,

if you need to do this for each of your workflows, then this is just a symptom of other configuration problems in your DocuWare environment.
You should consult your ADP (or colleagues or your partner contact at DW if you are an ADP) and look at the configuration together with them.
They can help you best with analyzing your system and finding configuration issues.

Greetings from Germany,
Simon H. Hellmann
DocuWare System Consultant

Hello Michal,

you should use data assignments to make sure that the workflow is not triggered multiple times.
One possibility would be to crate a new index field "workflow active". Then insert a data assignment step at the beginning of the workflow and make it write "active" into this index field.
Before the workflow ends, do another data assignment step which clears the field "workflow active" again.
Then edit your start criteria to only trigger when this field is empty.
This is just one example of how to manage multiple workflow starts, depending on your use case there might be a better way.

Hope this helps.
Greetings from Germany,
Simon H. Hellmann
DocuWare System Consultant