There is a glitch that I have run into twice now, when upgrading a version 6.9 - 6.12 system to version 7, that has to do with the file cabinet names being longer that 25 characters. God bless the poor guy from tech support who had to dig around in the database renaming all the related tables.

Is there documentation on this anywhere so that I might be able to fix this problem in advance of starting the upgrade next time?

Thanks,

I am unable to reach the partner portal.  Is it my browser or is it down for everyone?

Error.

An error occurred while processing your request.

In version 7.2, is it necessary to do anything after a change in the full text options in a file cabinet?
For example, a file cabinet was created and documents stored but the full text option was not checked until some time later.
Or, a file cabinet had full text checked but the server connection was changed in the admin tool and the file cabinet had to have the full text re-deployed.

In the version 5 and 6 series it was necessary to initiate a refresh.

It appears in v7 it is simply a matter of waiting for the full text server to catch up as full text results are not available in the client immediately after such a change.

Have I got this right?

Is there any documentation that lays out specifically what the rules are when two or more users open a document at the same time? It's a little tricky to test, but it appears there is no obvious 'document locked by user..' or read-only warning in the version 7.1 client or during a workflow activity.  

A workflow controller is reassigning tasks in bulk from the Monitor Tasks window (v7.1). The 'Send email notification' option is checked by default.

Is there a setting where this can be changed to 'off' by default? We can't count on the controller remembering to un-check it, and the emails are piling up, which provokes the end-users to ignore them.

Thanks,

Is there a way to see what is going on with a Smart Search that gives unexpected results? KBA-35072 mentions modifying a key in the DocuWare.Desktop.exe.config file in the .\Program Files(x86)\DocuWare\Desktop directory but the KBA mentions that it is valid for versions up through 6.8.
Is this info still valid, or is there a better way?

Thanks,

Me as well. Four tries, four failures.

Simon, I get it but are we sure about this part? 

"...or actually storing a new document which contains "New Document" as status, would NOT trigger the Workflow."

Storing a New Document with a Status of "New Document", and having the workflow trigger, is a requirement in my case.

Are you saying that since new documents have no previous values in any field, any BEFORE conditions would exclude new documents entirely?

Is that right? It would make the New Documents option irrelevant. That is unless I checked each before condition with EMPTY() or "Removed from Workflow". 

Simon,

Thank you for that info. I suspected that it would work this way as well.

I believe the I would only need a "Before" condition if in fact I want to limit the response to only those documents that actually had a certain value prior to the change.

For example; A BEFORE status of 'Removed from workflow' and an AFTER status of 'New Document' would trigger if I specify that BEFORE status value. Whereas changing the Status to 'New Document' from 'Processed' would not trigger as I have not specified that value as a BEFORE condition.

Is my assumption correct?

It is easy enough to start a workflow for new documents. Where I need clarification is with a workflow that should trigger for new or changed documents. 
Since a new document has no previous value in any index field, how should the 'before' section be filled out, or is that simply skipped over for new documents?
If the conditions for both are the same, it would seem that no documents would trigger, as the requirements for the 'After' section seem to imply that a change must be made.

Example, I need a document with Status "New" and a document type of "This" OR "That" and a start date of "<="Today" whether it has just now been stored or these fields have been updated (manually or by an AutoIndex process).

Clues for the clueless appreciated. Or a link to a FAQ if available.