The best Idea I have come up so far has been to catch the error and send it back to the previous task. Send an email to the user with the error message. Put a wait and after X time attempt to write again. But then again it would be complicated because I would have to have a condition to only send the error in case of the lockdown specific error, and I am not sure how to do that.
What is a good standard with dealing with locked documents during a workflow? Here is the scenario:
User has a task assigned and opens the document twice (by mistake). On the second screen the user puts the task stamp and closes the document. This task does not attempt to edit the doucument. The next step will edit the index entries, but fails because the user still has the document locked from the first screen.
I am sure this is a common Workflow routine for many Docuware installations, but I am struggling to come up with a solution. There are two possible document processing paths for our purchases, of course just keeping the basics.
Invoice -> PO Approval -> PO Creation -> Receipt Creation -> Invoice Approval (once documents are ready) -> Send Notification of Invoice Approval for Payments.
Quote -> PO Approval -> PO Creation -> Send PO to Vendor -> (wait for Receipt of goods/services) -> Create Receipt -> (wait for invoice) -> Invoice Approval -> Send Notification of Invoice Approval for Payments
I have a Field on all these documents with the PO# Reference that is Unique. I use this field to create the Document relationship for easier search.
I need a way to validate that there is a matching PO, Receipt, Invoice and Optionally a Quote that matches a specific PO before sending the approval for payment processing. I have setup a Docuware Printer to automatically index the PO number as they are added. Now I need a way to validate through a workflow that they exist. I thought about using the "Wait for event" but that activity is only for New or Changed documents. If the person clicks on "PO Created" on the workflow task after he has printed the Document, the Wait activity will not have caught the event. If I just use Wait commands, the user will not have a pending task to work the PO. Any idea how to solve the issue? Thought about creating a Validate condition on the Create PO task, but the validate condition does not allow for external data.
Any help would be appreciated.
In summary: I want to have tasks for each process and I want to validate the documents created during the task have been uploaded to docuware before finishing the workflow and sending a notification.
Problem is fixed. Port 9002 must be open and I used type LDAP configuration.
Hello, I have an issue where the External User Directories connection fails with the error "There is no access on the configured external directory!". This error occurs after the DC info is configured under Docuware System -> External User Directory -> Create New External User Directory, then settings are applied and Test Configuration is pressed. I have tried writing the Domain in all possible ways, configuring different DCs by DNS or IP, trying with different usernames and nothing seems to work. I am using General -> Type: Windows.
Any idea why this message appears? I've done AD connections with other programs without issues.
Looking for a way to pinpoint what is causing our Docuware installation to constantly hang the WebClient. We are running version 7 (Build:18.104.22.16880) on Windows Server 2012 R2 with all the latest windows updates installed. This has been happening since version 6 and before upgrading to the latest windows updates. When the WebClient hangs one of two things happen:
1) Login screen is poorly formatted (missing colors and not loading regular fonts). We usually use Windows login and when it is hanged that screen presents additional fields like the page is not updating the fields based on what is selected on the dropdown. Usually a restart to IIS fixes the login screen issues.
2) The login screen works, but once you click login, the next page remains completely blank. This usually requires a restart of the complete server. Restarting IIS will not fix this issue and this might happen after fixing the previous scenario.
Sometimes to fix the login issues I have to restart both IIS and the server.
Any idea of what could be causing this issue? Is there any log I can take a look at that might give me additional information? I verified the Windows Event Log and there doesn't seem any errors correlating to the webClient issues.