Robson Phil DocuWare Corporation Senior Director Professional Services, Americas

Martin,
Actually, yes. They could execute a "Lost password" reset.

Phil

Joe,
Correct. When using SSO DocuWare does not use the DocuWare password. In fact, if you perform an AD synch to bring in users, and specify that DocuWare creates a password for each user, then a 32 characters abitrary password is created. No one, not even the administrator knows what it is because it is machine generated and encrypted. Only an administrator with rights to create users can change that password.

Phil Robson
Senior Director Support Americas

Generally the login selected should be kept in a cookie locally, so that the last login type used becomes the default. I you want to use Windows SSO then do not implement DocuWare secure login.
What we can do to stop the users from being able to login using the DocuWare login is to select one user and set the password for that user to something very secure. Once set we can copy the encrypted password to all users in the system. Only the administrator who set the password would know what it is. That way, the unknown password would never expire, the correct password control is implemented through windows and no user except the administrator can login using the DocuWare login.

Phil Robson
Senior Director Support Americas

Jason,
I found the reason. An Internal (default) select list allows the use of the leading asterisk. It must ignore it during processing. However! If you use the leading asterisk against an external list, it fails immediately. The solution is not to use the asterisk at all when searching a select list. Also, remember to turn off filtering on the field that has the external list.

Also, bear in mind that select lists filter as you type. After 3 characters the list will get more precise the more characters you type in. It is read ahead tech. So, no asterisks to muddy the process.

Phil Robson
Senior Director Support Americas

Jason,
I believe that the description in the support request was misunderstood. I read it as "I want my select list to be case sensitive" meaning when I type in "Brooklyn" it returns all records "Brooklyn" but no records "brooklyn". Generally speaking DocuWare is case INSENSITIVE. However, depending on the backend database (Oracle for example is case sensitive), or MySQL on Unix (a case sensitive OS), results can be different.

What is the source of your new select list? What database? Fixed entries? Flat file?
Also, why type in the asterisk first? You would only use the wild card at the start if the word you wanted was further in the string such as "Mrs Brooklyn".
I tested this myself in 6.12 after your request came in and it works fine. Please try the search without the leading wildcard and let me know the results.

Phil Robson
Senior Director Support Americas

That will work unless the following condition does not exist:
There are no DocuWare 5 legacy internal index field numbers in the file cabinets. If there is, theses index fields will not be carried over to the new file cabinet when creating based on the exported cabinet XML.
Meaning the cabinet would have to have been created in 6.8 or later.

Please email me with the Support Request number. I am not aware of an upgrade that has been abandoned. There is always a solution.

Phil Robson
Senior Director Support Americas

phil.robson@docuware.com

Craig,

No. It will fail. They need to be on the same release to export. What does resisting the upgrade really mean?

Phil Robson
Senior Director Support Americas

In  the Import screen of DocuWare Desktop you can view the history of the import process. This history is kept for 7 days by default.

Phil Robson
Senior Director Support Americas

https://www.docuware.com/sites/default/files/forums-images/ImportHist2.png

Streve,

Send me an email. I'll reply with them for you.

Phil Robson
Senior Director Support Americas

Michael,
This question seems to be related to the current support request. I am not aware of any size limit (but that is not to say that there may be a value that requires changing). However, the log file clearly indicates a bad gateway error, which would indicated a network coms problem during the transfer. Since the log only refers to a single document it is hard to say. It is possible that the transfer errors co-incided with some recent  DocuWare 7 Cloud infrastructure issues.

Phil Robson
Senior Director Support Americas