Understood, thank you for the clarification.
I thought because of this line "Starting with DocuWare 6.7 the web components connect directly to the database server. Therefore it is not recommended and not supported to install DocuWare web components in a DMZ." Would we be able to install the front end (only option other than backend and intelligent indexing) option to a server on the DMZ and it still communicate to the SQL server not on the DMZ?
So all of the guides I have found regarding reverse proxies appear to only support up to version 6.11 or so. Is there anything special to do when you want to use a reverse proxy with 7.0, or is a reverse proxy even needed?
We are needing to configure a document relation between 2 doctypes and a single field. However, on one doctype (Asset) the field is set to a keyfield and on the other doctype (Invoice) it is set to a text field.
I have created a relation, where you search for an invoice, once you have an invoice I can see my relation for the Asset doctype. I click on it but do not get any results. I have attached a screen shot of my document relation
Ah, yeah we are able to do some things in 6.12 yet getting errors in 7.0. I have a ticket ongoing, I will let you know what happens. Thanks for the information.
Were you doing this in 7.0? I am seeing some odd issues in 7 whereas in 6.12 it worked fine. We have uploaded 2 PDF files, checked them out, then tried to staple them. In 7.0 we get an error that states "Document “XX” is associated with document in progress and cannot be removed". In 6.12 it works fine.
We are building a REST API that will look at a document and based off of specific criteria and if it meets it will staple the documents together so that they are pages to a full document. There is code from the Platform code examples that shows us how to do this
static partial class Examples
public static Document MergeDocuments(FileCabinet cabinet, List<int> docIds)
Document mergedDocument = cabinet.PutToContentMergeOperationRelationForDocument
Documents = docIds,
Operation = ContentMergeOperation.Staple,
Force = true
But during testing we are getting the below error, are we missing something?
"405 Method Not Allowed (File cabinets do not support StapleAsync)'"
We have a client that used this setting in Fortis, for their Fujitsu Paperstream scanner. Now in DocuWare it seems to be ignoring this setting. If I have the driver set to color detection and scan through a document that has parts highlighted it will ignore the color, scan in black and white, and either fill in the highlighted parts or draw a box around the highlighted parts. Is there a way to get the color detection to work in DocuWare?
I do have a work around, if they select the option, Show scanner device dialog, in the Scanner settings, they can then select the Auto-Color Default in the drop down of the paperstream settings, then press the scan button on there and it will scan with the highlights. This causes extra steps and we would need to see about shortening this.
We have a client that has more than 20 doctypes (about 50) for one filecabinet. They are not wanting to split them up and I remember hearing about modifyng the docuware.fortisfilecabinetmigration.exe.Config file to increase the maxtypespercabinet section to the number that would work. I just want to make sure this is still something that can be done before increasing it and performing the migration.
Awesome, hopefully I can get some time later this afternoon and test. I will let you know what I find.