In the past, that is prior to version 7, if a customer with an on premises system wanted to change the name of the organization, a new license file was generated with the new name, and installed.
Is it still just that simple in version 7 - 7.2 ?
When pushing out the Desktop Apps to many users, can the default connection also be created, or will each user need to connect to the desktop at first use, using the web client?
The customer would like to push Smart Connect out to all users and allow them to use the Smart Connect button configured for the 3rd party app without having to visit each machine for the desktop apps connection beforehand.
A customer is planning an in-place upgrade to Windows 2012R on their DocuWare server running v6.12. This version is compatible with that version of Windows but are there any other considerations or potential problems to be aware of?
Thank you for that info. The real question is this. Most of the users have been assigned to Index Profiles to provide very granular control over who can see and modify certain documents. 'Add New Entries' is not an option in an Index Profile, so insufficient rights errors occur during workflows for these users. It seems that a Custom Profile must be created, the 'Add New Entries' permission given, and then this profile assigned to the users along with the index profiles. And that this is by design. Have I got that right?
A validation in a workflow task is correct (the designer validates and does not prevent completion of configuration) but does not work in practice. The idea is to allow only a select list of users to execute the step.
The validation is: WF_LOGGED_IN_USER = "user1" OR WF_LOGGED_IN_USER = "user2" OR WF_LOGGED_IN_USER = "user3" OR WF_LOGGED_IN_USER = "user4" OR... There are 11 users in this list.
The workflow designer does not complain about this, the OK button is enabled. But in practice these users are not able to execute the task and receive the 'condition not fulfilled' error message.
Is there a limit to the length of the condition, or some other syntax error visible here?
Can anyone give the specifics, or point me to documentation that does, of the Allow New Entries permission. (Version is 7.1) It seems to exist only when using a Custom Profile. How does it differ from the right to modify an index entry? Is it needed in addition to other rights?
Workflow has thrown errors that a user without this right cannot change an index entry despite having the right to read search and modify given by an Index Profile where Add New Entries is not even an option.
Any and all clues appreciated,
After some more investigation I might want to revise this question.
I see in the Database that there is a DWSTOREDATETIME field for a document in the table of a document tray.
This same field is replicated in the table for the file cabinet and updated when the document is indexed and stored.
Is there a way I could find out the difference between these 2 dates? That way I could tell how long a document was in a tray before it was indexed and stored in the file cabinet.
In the web client viewer at the bottom left corner of the document, there is a display of a file name and a date. I believe the file name is the original name of the file on disk when it was imported into a document tray and the date is the date it was imported into a tray. As opposed to the Stored Date, when the document was indexed and stored in a file cabinet.
Is this correct?
A user wishes to know how long a document has been in a tray before it was stored. If this is the "Tray Date", is it available somewhere to be queried? It is not listed as a system entry.
For auditing purposes in an invoice processing system, we are trying to get a more accurate idea of when a document actually enters the system as opposed to the Stored On Date. That is, a document could be scanned/imported to a document tray, but not indexed and stored for a month. This makes it appear that the invoice processing workflow is taking much longer, when in truth it is a user issue.
Any clues appreciated,
In the email that went out from DW recently, we were notified that browsers that may be out of date and don't support the new TLS update will have difficulty accessing cloud systems. In order to test current browsers this was added...
“To prepare the change to TLS 1.2 we will deactivate the outdated TLS versions for a few hours on January 21st, 2020. This will enable you to check whether all DocuWare Cloud Clients have been converted correctly.”
Does anyone know when exactly these few hours will be? I have a customer that needs to test many users and in many parts of the US and some in EU.
A customer reports that many documents fail to be stored into the file cabinet which is the target of an import job. These documents show up in a document tray he has named "Failures". I believe this is just the default tray of the user running the import job. I have asked for more info but it raises some questions.
How does DocuWare determine when a document fails the import job and should not be stored? Does this only happen for jobs that have file cabinets as a target? Does it only happen if OCR is being used or if there are required fields missing?
Is there a way to direct documents that fail to import to another tray based on the individual job, if multiple jobs are running on the same machine under the same user?
Is there any specific documentation available?