Nate Howland Technical Sales Analyst

Support reached out to me to discuss this. There is currently no way to alter the field data payload structure that is sent. It was suggested to add in a downstream transformation using a 3rd party tool to change the payload structure.

I'm looking for a way to control the field formatting in the web workflow designer web service task. I have an API that expects to receive the document and related fields to be formatted using the multipart form-data standard (https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Methods/POST#multipart_form_submission).

For example, if I create an API POST call in Postman using the form-data type with key/values in the body, it automatically builds out a cURL statement like this:

curl --location 'api endpoint' \
 --form 'Field1="Test1"' \
 --form 'Field2="Test2"' \
 --form 'file=@"Test.pdf"'

This is the correct format for what my API requires.

I've found, though, the DW web service task is still using the form-data POST type, but packaging all fields up as a JSON string in a single field called "requestData". Something like this in cURL:

curl --location 'api endpoint' \
 --form 'requestData="{ "Field1": "Test1", "Field2": "Test2" }"' \
 --form 'file=@"Test.pdf"'

Is there any way to control and/or modify the web service task output so it matches the first style?

Thanks!

Hello! I'm looking for instructions on upgrading from Intelligent Indexing "1.0" to "2.0" for an on-premise system.

I've looked through the online help and knowledge base and all I've found are the Intelligent Indexing 2.0 install instructions on github and it appears to only contain information about installing a new system. not doing an upgrade. Did I miss the upgrade instructions somewhere?

Thanks in advance!
 

I recall the DocuWare on-premise system requirements used to more clearly state what private cloud environments it did or didn't support. I see the latest 7.3 requirements call out only AWS as being unsupported. By way of not mentioning any others, does that imply that all other environments are supported?

For example, I thought installing in Azure required the MessageBus customization, but that isn't mentioned at all in the system requirements.

What about other large providers like Google Cloud, IBM Cloud, Rackspace, Digital Ocean? (There are 100's of other smaller private cloud hosting companies as well...)

I think it would be very helpful to more clearly state which major private cloud providers are or are not supported. It would also be helpful to list out any specific requirements needed for DocuWare to be supported in a smaller private cloud environment.

For anyone interested support did get back to me stating that Connect to SharePoint works in DocuWare on-premise 7.3. There is no new documentation available beyond the links above. SharePoint versions supported are 2007, 2010, 2013 and 2016 (no support for SharePoint 2019, Online or Office365).

Hello! I'm looking for current details on the Connect to SharePoint module.

I've found these 2 sites https://start.docuware.com/connect-to-sharepoint and https://dw-help.azurefd.net/#/home/61227/2/2 that contain marketing information.

I've also found this https://dw-help.azurefd.net/#/home/60332/2/2 which goes into more detail but doesn't appear to have been updated in the last several years (still using 6.x screenshots and even what appears to be Window XP screenshots!).

Is this documentation still valid for v7.3? What are the latest system requirements and supported SharePoint versions?

Thanks!

 

I was able to create and test a form with over 20 merge forms on it, so it appears to work for what I was looking to do!

I'm wondering if there's a limitation to the number of merge forms that a single DocuWare Form can fill out? Looking at a project that would have 20+ distinct PDF's needed to be filled out from a single Form.

Thanks in advance!

I agree with this! Please add it in.

It's confusing to not have 7.0 and 7.1 system requirements in the KB.
 

I did finally find the Version 7 requirements link in Phil's forum post here, but might I also suggest that a copy of them be added to the knowledge center (where they've always been kept for the past 10 years...).  It may save folks some time when attempting to find them.