Craig Heintz SE

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.

I have always used the below requirements from Article ID# 2638 for setting up a MS-SQL Database.  Someone challenged me yesterday on #5 in the list as they want to basically give me a SQL account with DBO rights to all the DW DB's only.  Is that SQL right in #5 an ongoing need or is it for the initial setup of the DB only?

Microsoft SQL (MSSQL)  for DocuWare Installation

1. Make sure MSSQL server is up to date with their service packs (SP), especially if you are using old version of Micorsoft SQL Server.
2. Microsoft SQL Server has to be configured with a static port number for installation. Dynamic porting is not support by DocuWare during the installation. The default port for MSSQL is 1433. Also MSSQL Express Edition is not supported by DocuWare.
   1. To see if SQL server instance has been configured with static or dynamic port you can use the tool called "SQL Server 20xx Configuration Manager"
   2. Also take a look at the "System Requirements" for each version of DocuWare. 
3. Micorosft SQL server has to be configured to accept SQL Authentication and Windows Authentication. During DocuWare installation SQL authentication will be utilized. This is typically done in SQL Server Management Studio (for SQL 05/08/12/14/16).
4. By opening “SQL Server Management Studio” login into the SQL Server and create a SQL user with:
   1. Securityadmin role rights
   2. Sysadmin role rights
      1. This SQL user must be able to create databases and objects with the database (tables, triggers, indexes, etc). 
5. This SQL user should also be mapped as securityadmin role for tempdb databases.
6. If your SQL server has multiple instances running then you have to connect from DocuWare using the full instance name (E.g.: ServerName\InstanceName) during the installation.

NOTE: Once the database has been prepared, DocuWare Authentication server installation will onnect to that database and create all necessaries components required for DocuWare software. If you are installing DocuWare in a different server, then you could test the connection by creating a test ODBC connection from that DocuWare server to the Micrososft SQL Database server (as test only).