Steve Shriver Application Specialist

Can anyone say if KBA-35463 is still valid in version 7.1? Is it still necessary to schedult fulltext operations on large cabinets? Will turning off fulltext in file cabinet configuration force a reset of the fulltext tables?

Thanks,

In this small screen snippet of the bottom left corner of the viewer in the client, after the original file name there is a date. I assume this is the file date on disk (Date modified column in Windows Explorer), before it was imported into a document tray. Is that correct? 

Since it is displayed in the viewer I also assume it is stored in the DW database. Can anyone tell me where?

I would like to be able to report on the number of days between when a document actually came into the system and when it was finally processed, as opposed to when it was stored (DWStoreDate) and processed.

Many thanks,

In this small screen snippet of the bottom left corner of the viewer in the client, after the original file name there is a date. I assume this is the file date on disk (Date modified column in Windows Explorer), before it was imported into a document tray. Is that correct? 

Since it is displayed in the viewer I also assume it is stored in the DW database. Can anyone tell me where?

I would like to be able to report on the number of days between when a document actually came into the system and when it was finally processed, as opposed to when it was stored (DWStoreDate) and processed.

Many thanks,

A user has uncovered that if you have a result list configured to 'Open first document of the result list automatically in the Viewer', 3 'Open' entries are created in that document's history log after doing a search.

In addition, opening the document history itself creates another 'Open' entry in the log.

Those that examine document history closely may see 6 or 7 'Open" entries after viewing the document only once.

I'm not sure I would refer to this as a bug as I have know idea what mechanism is used to track document activity, but it does appear somewhat confusing in an environment where this is used and examined closely.

Any clues appreciated.
 

When configuring a List in File Cabinet Configuration (Cloud System), the SQL Statement radio button is disabled and only the Rules Editor is available.

In previous versions there was a check box in the Admin Tool that allowed us to enable the use of SQL Statements, but it is nowhere to be found in the current version of the Admin Tool.

Is that still something that needs to be done, and where can it be done?

Or is SQL simply disabled for Lists and the option still displayed? (and why would you do that?)

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.

Thanks,

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?

Thanks,

Tobias,

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?

Thanks again,

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?