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

Hello Marek,

the Workflow designer can not handle this dynamic assignment you wish. You could either put a text field in the decision where you type the name of the next step, then after the task, you have a lot of condition steps which evaluate if the value you typed into the text field matches a step - if yes, it goes to the step, if not, it evaluates the next step.

The other option would be to have one decision per each step which could be next, and you choose the next step this way.

However, I do not think that this approach is "best-practice" and currently, I fail to see any reason to do this.
The default "General Error"-Task already gives you the options to either repeat the task which failed, continue with the next step or just exit the workflow, usually this is enough for me. In rare cases when I need special error handling, I create such an "error"-Task assigned to the administrator.

Greetings from Germany,
Simon H. Hellmann
DocuWare System Consultant

Hello Marek,
this is currently not possible with DocuWare 7.2. A user either has access to the complete table field, or not at all.
You might want to consider posting this over at the Uservoice forum.

Greetings from Germany,
Simon H. Hellmann
DocuWare System Consultant

Hello Marek,
this is a bit complicated. The easy way would be this:
Create a task called "Clip reciept" or something like that, assign that to the department and give the task only one decision, called "reciepts clipped". Teach the users how they clip documents (right click in list -> clip, or via toolbar) and tell them to only confirm this task if they have clipped something to the document.
However, this way you have no way to validate if they actually clipped something or just confirmed without doing so. You can not stop users from confirming the task without clipping something. 

If that is what you need, you probably have to take a look at the REST API over at developer.docuware.com , that way you can clip and validate it as well. As far as I know, this is not possible with just the workflow manager.

Hope this helps.

Greetings from Germany,
Simon H. Hellmann
DocuWare System Consultant

Hello Marek,

if I understand correctly, you have a table with invoice items and seperate items are to be approved by different people, e.g.:
 

subject	amount	user
Bread	10,13	admin
Butter	2,52	marek
Cheese	3,41	simon

Now you want to assign the parallel task to all users, in this case: admin, marek and simon.
you can use an "assign data" step to create a global variable of type "User from group" (use group "public" and check "list variable") which contains all users. Then, assign the parallel task to this GV.

The assign data step should look like this:
 

global variable

UserList

Document Index Data

TableField[Users]

As parallel tasks finish automatically when all users completed their tasks, you should not need any cancel conditions.

Hope this helps.

Greetings from Germany,
Simon H. Hellmann
DocuWare System Consultant

Hi Steve,

your workflow sounds like you have one task which is done by different employees each time. However, this task always gets assigned to the same user who then right clicks it and uses the "reassign" function to distribute the tasks throughout the company, is that right?

In this case, I would recommend to implement an additional task which takes place before the actual decision task. Assign this task automatically to the user who distributes tasks and give them only one decision: "assign task". In the Dialog, give one field "Next User" or something like that as a "User from group (Public)". Then, assign the document to the selected user and start the next task. this way, you can put the assignment into a stamp or index data, it appears in the workflow history and it is more comfortable to use.

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

Hello Chris,

for on-premise systems, you can change this timeout, yes. The maximum is 24 hours.
However, I do not remember where to change this - it was in some configuration file on your frontend server, I recommend asking DW Support about this.

(And kindly update this thread if you found the location)

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

Guten Morgen Sebastian,

soweit ich weiß, wird dieses Verhalten leider seit mind. Version 6.7 nicht mehr unterstützt (mit den älteren kenne ich mich nicht aus) - vielleicht kann ein Kollege von DocuWare hier noch mehr zu sagen?
Um das Problem zu umgehen, hätte ich spontan zwei Einfälle, beide aber mit Bordmitteln nicht zu machen.

1. man könnte über einen Stempel drucken - Stempel ändert Status, Workflow löst aus und spricht einen Webservice an der von dem angewählten Lieferschein und allen, von denen die Nummer in ein Benutzereingabefeld des Stempels geschrieben wurde die ersten beiden Seiten druckt.
Ist aber ziemlich umständlich einzurichten und nachher wahrscheinlich auch schwer zu warten.

2. Man könnte den Druckdatenstrom mit einem Tool abgreifen lassen und diesen so verändern, dass dieser jeweils nur die ersten beiden Seiten druckt - aber auch das müsstest du entweder zukaufen oder programmieren.

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

Hallo Herr Bittner,

das ist leider so nicht möglich.
Allerdings können Sie in der aktuellen DocuWare Version mit einer Validierung arbeiten, so dass das Formular nicht gespeichert werden kann, falls das Enddatum gleich oder früher dem Startdatum des Urlaubs ist, siehe dazu meine Beispielscreenshots.


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




 

Good morning Aaron,

yes, Phil is talking about the installed DocuWare files which reside for example in C:\Program Files (x86)\DocuWare. Not because these files are not replaceable, but because some part of the config could reside there.
However, I think he means the entire Windows System as well, so you can restore your backup as fast as possible if needed.

My usual go-to recommendation is to use VMs for the DocuWare Servers and back them up by using some tool like Veeam Backup and Restore.
Additionally, you could back up your documents and the database.

You can split your DocuWare installation to up to 3 servers, see this blog post for details: https://start.docuware.com/blog/product-news/choosing-the-ideal-docuware-server-configuration

Greetings from Germany,
Simon H. Hellmann
DocuWare System Consultant

Hello Gilles,

i think we have a small misunderstanding here. What I meant to recommend was to do the following, given the scenario that the DW customer has neither AIX nor WF available.

1. Add a new index field (int) to your file cabinet like you usually would and call it "ID" or something like that.
2. Connect to your database and create a script/trigger which copies data from the field "DocID" to the field "ID" in the same row.

From a technical standpoint, you are not messing much with the database and the only thing which might happen is that if you have the "Index Data Backup in storage location" enabled, the data from the field "ID" might not show up in these files - which does not really matter, because the DocID already shows up there.

On the other hand, yes, you are right, there are better ways to do that - namely AIX or WF.
Yes, when you update your DW System, the upgrade might break your script/trigger, you need to check this after each update.
Regarding DW support (as far as I know): DocuWare will still provide support to your system if you do not mess up the database too much - they just won't support the parts you messed with or require you to remove your customizations before working on the database (at least that's what they say, they have not done this to me yet).

However, I can only talk about the EMEA Support team and my personal expiriences.
Regarding US Support, we might want to wait for an answer by Phil.

Greetings from Germany,
Simon H. Hellmann
DocuWare System Consultant