Joe Kaufman Bell Laboratories Inc No longer there

Bernie,

On 6.11 (so, using the DW Admin Desktop tool to create related document links), I once had an issue where it seemed like links took a while to show up. No matter how much I refreshed and applied, it took some time and then the link would appear right as I was about to call support.

How long have you been waiting? Have you tried bouncing the DW services on the server (if this is on-premise) or bouncing the whole server? Just to see if the links appear and so you know it is a caching/timing/event queue issue.

And, of course, have you checked the permissions for the result list the link generates? I do not think the links themselves have permissions (I do not see any at a glance, anyway), but I am not sure what happens if the user has access to the file cabinet but not the result list the link leads to.

When we have had things non-visible in the past, at least half the time it was because we had not granted proper permissions somewhere along the long line of things being used...

Thanks,

Joe Kaufman

Phil,

Thanks for the detailed confirmation on that -- good to know!

Thanks,

Joe Kaufman

Connie,

I just changed my DocuWare password via the DW Admin tool so that it is different from my Windows password. I was still able to log into DocuWare via Windows Authentication, and then when I used DocuWare authentication I had to use the different password I had just changed to. 

I can't be sure it works the same way when it comes to expiration and password compliance rules, though. Anyone close to expiring that you can test with? It looks to me like WIndows authentication works regardless of the DocuWare login. I have had uses that never logged in with DocuWare authentication and so have never even changed their password away from the original (we do not enforce any rules or expirations, though).

Thanks,

Joe Kaufman

Phil,

For the record, I have never seen this in our on-premise 6.11 system, and early on I did quite a bit of deleting whole pages of documents at once. I don't recall ever needing to do halves at a time.

Just a long shot, but is there a way to turn off the result list auto-refresh at some level? If one could temporarily turn that off, it could help. Alternately, do you know if viewing documetns in folders has the same issue? Folders can show up to 10,000 documents at once, all in one list, so if you can create a folder with a filter to display the documents you want, perhaps that would be an easier way to delete them? Just be sure you have the exact document you want!

Thanks,

Joe Kaufman

Tania,

This links to a similar issue of the "by half" scenario:

https://www.docuware.com/forum/english-forums/docuware-questions-about-usage-and-configuration/multiple-indexing-stops-half-way-through

Your best bet is to probably open a support ticket with DocuWare, as this might be a bug with some sort of workaround or patch.

Thanks,

Joe Kaufman

Phil,

Agreed, though a while back we figured out that if you want to return a massive (as in, unpaged) result list, it can be done with filtered Folders. A folder will return anything defined by the original query within its group-by pivot. Though, I just tested that out and tried to return over 10000 results, and I couldn't (without upping the cap). So, it looks like Folders honor the limit as well! Hopefully there is an on-prem way of changing that in lieu of the desktop Admin tool.

Thanks,

Joe Kaufman

Phil,

Very interested to know if on-prem has a workaround. Anyone who does much Platform SDK integration is going to want to have control of that result parameter (because I am pretty sure it affects returned results for SDK queries, too). This would be another reason for us to stay on 6.11 if there is not a way to increase that number. We try to use the SDK wherever we can instead of directly hitting SQL Server, so 10,000 rows could potentially be quite limiting.

ADDITIONAL NOTE: in the DWFileCabinet table, "settings" field, there is a section that looks like this:

  <Misc maxIndexSearchHits="10000">
    <SelectList timeout="15000" />
  </Misc>

for each cabinet. For cabinets where I have upped the max number of hits, "maxIndexSearchHits" is set equal to the higher number (30000, in my case). Not sure if you could just change it in settings and have it work, or if that setting is a mirror of some other table or config file. Changing the XML in the settings field is not actually all that straightforward, anyway...

Thanks,

Joe Kaufman

Cody,

As to your last question, I think you should stick with SDK libraries (like the packages in .NET) that match your DocuWare version. I would guess this is especially true when going from version 6.x to 7.0, as 7.0 is a pretty big change. We are on 6.11, and I have stuck with the 6.11 packages from NuGet even though newer versions are available.

Thanks,

Joe Kaufman

John,

What are you seeing in your Connections Overview as far as licenses in use and when they expire? I ask because we are on 6.11, and sessions automatically time out after about 12 minutes of inactivity in the web client. More details have been discussed on this thread:

https://www.docuware.com/forum/english-forums/docuware-questions-about-usage-and-configuration/forced-log-due-inactivity-premise-612

I have not figured out why some folks seem to have connections which will not release, but ours do release. It might be related to a module (e.g. Workflow) keeping connections more "alive", but that is wild speculation on my part. Check the connections in your DW Admin tool and see what happens to expiration timestamps for idle connections. They should drop from 30 minutes from start to just two minutes from the current time after ten minutes of inactivity -- that is what I see in my 6.11 on-premise system.

Thanks,

Joe Kaufman

Here is a quick link to implementing extension methods in general:

https://docs.microsoft.com/en-us/dotnet/csharp/programming-guide/classes-and-structs/extension-methods

Thanks,

Joe Kaufman