Robson Phil DocuWare Corporation Senior Director Professional Services, Americas

Joe,
With respect, I have just clearly described how dangerous that method is on a DocuWare system  - specifically prior to DocuWare 7. Whether Product embraces the request is not my call. I simply support the product as it exists. For sure, I voice my opinion, but my opinion is no different from any user. It is taken and weighed in context. As you see in this forum thread, the Product Owner has made his comments.
My point is this, taking this approach is dangerous. What is more important? Your data or a session timeout? In most security requirements that I have read expect the computer to be locked as a priority - not timeout every session to every application.

So I don't see it as desperate times for desperate measures at all. And please don't try to bully me by suggesting that I may prefer that users dump DocuWare.

Phil Robson
Senior Director Support Americas

While I applaud your creativity, that is not a solution for a session timeout. Firstly, you do not know if the session is idle from the licensing table. Therefore you run the absolute possibility of corrupting data. Users sessions are tightly tied to the background processing - particularly in versions prior to 7. If you kill a client license in this manner, and the user has document writes active at the time it will kill those dead. The result could be anybody's guess.

I cannot stop anyone from doing this, but understand it is at your risk, not DocuWare's. I hope never to see a Support Request as a result of this cavalier approach.

Phil Robson
Senior Director Support Americas

Sorry Joe. It is not possible. The edit index entries and applying the stamp are 2 different threads and are not dependant on each other. Basically, they do not "read" each others thread data. So the user needs to save in index data entry.

Phil Robson
Senior Director Support Americas

Joe,
Let me test that for you. I have an idea.

Phil Robson
Senior Director Support Americas

Aaron,
That was removed in DocuWare 6.11. DocuWare now only supports natural casing - that is, however it is entered that is the way it is stored and shown.

Phil Robson
Senior Director Support Americas

Inbound calls are now once again possible to DocuWare Corporations' New York and Connecticut offices.
The problem was an infrastructure issue int our telephone system providers data center.
We applogize for this inconvenience.

Phil Robson
Senior Director Support Americas

DocuWare.Platform.web.dll.settings.

  <CacheExpiration CleanupPeriod="00:00:20" Session="00:10:00"

Phil

Mystery solved. From 6.5 to 6.11 there is a setting in one of the config files that defines many session parameters. In particular there is a session timeout setting. The default for this setting is 10:00 minutes, which correlates close enough to Joes experience. Now, with 6.12, this setting still existsin the file but it is clearly ignored by the platform engine. Therefore, there is really nothing that can be done from our side.

Phil Robson
Senior Director Support Americas

Joe,
The functionality was removed with DocuWare 6.5. I am looking into remnants of it remaining up until 6.11. It might be that there is a setting in a config file that is controlling your timeout. I seem to recall a value of 10 minutes which is close enough to your 12. Nevertheless, it certainly is not there in DocuWare 6.12.

Phil

The definitive answer is that Jason's behavior is exactly as I would expect from DocuWare. 6.11 or 6.12, or 7. I do not know where your 12 minutes is coming from Joe.

Phil Robson
Senior Director Support Americas