I have done this in several ways. AI has a setting for Items not matched and you can set a fixed value to a field whne nothing matches. This way you can determine the ones that have run throught the process but did not match anything.
I use one of two methods; 1. Field called STATUS and set it for Matched when it does and No Match when it does not.
2. Create a new field called AI and write the info there.
This way you can run a search against the status and see all that conform. And if you have TASK LIST you can set a list for it.
Looking for instructions/guidance on setting up the DocuWare User Synchronization with the Desktop app and Cloud Account.
Here is what I have and it does not work...won't connect.
You must be logged into a computer on the domain and have access to the LDAP and then it works. If you are not, you will get error messages that may make you belive that the DocuWare Cloud is refusing the connection.
No further action needed on this post
A support case has been opened for this issue
We have attempted to perform the upgrade 3 times and it has failed each time. 2 of the times with DW Support. Seems their is either corruption in the DB or something is too slow. Just checking my options.
What about setting up a new server with the same fields as the old, moving the document store and Restoring the documents using the associated xml info?
Current DW 6.9 is resisting the upgrade process to 6.12.
Can a new DW Server with 6.12 be set up to match the 6.9 environment with fields and then export all of the docs from the 6.9 to the 6.12 server. Is this possible?
Thank you. Checking the REQUIRED box for the Database Field has done the trick.
I have set up a field to use a select list and check the box for "The user can only use entries from the list to set field"
The select list has Yes and No as choices
When storing, this field allows for it to be left blank, Yes, No as storable entires.
How can I stop an empty entry from being allowed?
Curious now that v7 has an app to synch AD with the Cloud does single sign on work for cloud users?
This worked. Thank you.
I have upgraded a DW server to 6.12 which turned of the forcing of ALL CAPS for my index information. Unfortunately, my workflow has a decision to evaluate the next step that is being very case sensitive.
Instr(1, GV_ReqUser, GV_L2auser) =0 AND Instr(1,GV_L2auser, "NOT REQUIRED") = 0
Any new entry that comes in for the GV_L2auser that is set to "not reuquired" fails and the task goes to the MONITOR users.
My Question is how can I make the above logic not sensitive to case? Meaning if any variation of "Not Required" will work. IE: NOT REQUIRED, Not Required, not required, and noT requireD all work without putting every iteration into the logic.