Craig Heintz SE

We have attempted to perform the upgrade 3 times and it has failed each time.  2 of the times with DW Support.  Seems their is either corruption in the DB or something is too slow.  Just checking my options.

What about setting up a new server with the same fields as the old, moving the document store and Restoring the documents using the associated xml info?

Current DW 6.9 is resisting the upgrade process to 6.12.

Can a new DW Server with 6.12 be set up to match the 6.9 environment with fields and then export all of the docs from the 6.9 to the 6.12 server.  Is this possible?

Thank you.  Checking the REQUIRED box for the Database Field has done the trick. 

I have set up a field to use a select list and check the box for "The user can only use entries from the list to set field"

The select list has Yes and No as choices

When storing, this field allows for it to be left blank, Yes, No as storable entires.

How can I stop an empty entry from being allowed?

Curious now that v7 has an app to synch AD with the Cloud does single sign on work for cloud users?

This worked.  Thank you.

I have upgraded a DW server to 6.12 which turned of the forcing of ALL CAPS for my index information.  Unfortunately, my workflow has a decision to evaluate the next step that is being very case sensitive.

Instr(1, GV_ReqUser, GV_L2auser) =0 AND Instr(1,GV_L2auser, "NOT REQUIRED")  = 0

Any new entry that comes in for the GV_L2auser that is set to "not reuquired" fails and the task goes to the MONITOR users.

My Question is how can I make the above logic not sensitive to case?  Meaning if any variation of "Not Required" will work.  IE:  NOT REQUIRED, Not Required, not required, and noT requireD all work without putting every iteration into the logic.

Thanks Phil and that makes sense.  Unfortunately we are installing into a hospital infrastructure and they want to give our SQL account for DocuWare minimum rights and will not give us DBO for the Instance.  So that being said, if I can give them an explanation of that the " securityadmin to the tempdb " right is used for, they can decide if and how they want to proceed. 

Is there any way to find out what this right is for and what it allows to happen?

I have a demo server where the DocuWare.BackgroundProcessService.exe is opening many PID connections to the CPU and eating up the CPU %.  Currently there are 5 PID running for this service.  And the close and new ones open.

I am not doing anything to the server when this is happening.  It is just sitting with no document being stored, imported, printed...nothing.

Suggestions as I am trying free up resources.

Current Environment:  VM, 2 cpu, 4GB mem, SSD Drive

I may have found my answer on the FAQ site:

https://www.docuware.com/support_faq/index.php?action=artikel&cat=191&id...

I also stopped most of my AutoIndex Workflows since they are demo specific.  Anything else to suggest that may be helpful?

Keep in mind that if you are doing any changes to the DW Database directly and not through a DW process that the Task Lists will not update.  It is a requirement that changes run throught the Content and Workflow Server processes to allow the Task List triggers to happen.