Casey Miller Director of Technical Services

Phil, I believe you have gotten it! Thanks for the help.

I think I can get around the notification part by creating a new parallel task after the first check then turn notification off on that one. I understand the concept you are saying but wouldn't know how to get around the user already approved not getting the task again.. May just be we can't do it that way..

So, it is an application that is submitted into docuware from DocuWare forms to a Committee for approval. But, if majority approve then it passes. Right now, it is just 4 users, so 3 would be majority. 

So it would need to leave the Parallel task to do this then get fed back in? Would the users who have already approved it get an approval again?

Great information. Thanks, Phil!

had a question today about parallel tasks and I wasn't 100% on the answer, but here it was. They have a TASK sent to 4 users for approval of a document. It goes in as a parallel task. Is there a way that we can set an exit condition so that if 3 out of 4 approve, it will exit?

I have a workflow setup that when the application is approved it autofills an Approved Date field with current date. is there a way in the workflow manager that we can also fill in the Expiration Date? I can't figure out how to calculate this? It is 3 years after approval date.

ok, thank you. I would suggest loading them in the KB like every other version is. Not sure why things are being  put in different spots.

Pretty new to 7 and you will want to double check but you should just be able to create the domain user in MSSQL and make sure mixed Auth is turned on. The user will need the DB.creator role at least. Then sign into docuware admin tool and change the login to the new login for each database. I am not sure if there is still a settings file for each service like before that has this in it too..

I think this would be different depending on what version of DocuWare you are on.