Benoit Vassart ASC

Dear Phil,

You're right, but in our case, the design was done by a Docuware consultant. :(   (maybe an issue with the previous engine can explain the way of working ?)

Our main issue is with the active documents when upgrading. It's almost impossible for us to know if our workflow will still working after an upgraded workflow engine. If not, the documents will go into an error state and the workflow will stop. 

This will also be the case for further versions. 

I've found a similar issue when upgrading and some components were not supported anymore:

https://www.docuware.com/forum/english-forums/docuware-help-technical-pr...

(Thanks for the webinar yesterday, very interesting, specially for upgrades)

Benoît, 

Dear,

Has anyone had issue with the upgrade of workflow from 6.9-6.12 for assigning external data and variables? 

Our issue is using 'quotes' within the SQL queries. 

Version 6.9, we had the following:

Assign data (arithmetics): GVmyVariable = "'" + GVmyVariable + "'"  --> Result should be GVmyVariable with quotes

Assign from external source: 

the select clause was like:  Select MyColumnName from DatabaseName where myField = GVmyVariable (without quotes, because they are set in the previous step)

Version 6.12: This was not working anymore. (in fact, the workflow engine seems to add on his own quotes)

 Workaround: Removing the first arithmetic operation GVmyVariable = "'" + GVmyVariable + "'" and set the quotes within the SQL query: 

Select MyColumnName from DatabaseName where myField = 'GVmyVariable' 

Very annoying issue, specially for active documents within the workflow.

Kind Regards

Dear Tobias,

Joe is right, in my case, is mostly a licensing issue. 

The license price has doubled with DW 6.12.

In the past: 2 named licenses : 1  concurrent license 

Now: 4 named licenses : 1 concurrent license. 

Our customers are using a lot of concurrent licenses, and we often need to log out users. 

Kind Regards

Security issues, licensing? 

Top of ideas:

https://docuware.uservoice.com/forums/230570-client-english/suggestions/...

https://docuware.uservoice.com/forums/230572-configuration-english/sugge...

And no actions from Docuware.

Too bad

Dear Erick,

Please select the option: All Tasks: You should see the workflow task ID.

Connect to the Workflow designer and stop the workflow task ID. 

Kind Regards

Dear Erick,

Please select the option: All Tasks: You should see the workflow task ID.

Connect to the Workflow designer and stop the workflow task ID. 

Kind Regards

I need within an approval workflow to wait for an index change done by an external application (Erp). 

I was wondering if using a loop on a "condition" object was a good practice, specially on performance. (see printscreen)

I will have permanently hundreds of documents waiting on the Index change and I was wondering how Docuware will handle this. 

An another way is to create a new workflow based on index change, but in our case, I prefer to have only one workflow. (for technical and business reasons)

Kind Regards,

https://www.docuware.com/sites/default/files/forums-images/WorkflowEngine%20-%20Conditions.jpg

Dear Stephane, 

you can use a post like this (tested with postman):

First Login: http://docuware/DocuWare/Platform/Account/Logon?UserName=xxx&Password=xx...

Then a POST command (with curl - postman or other tools)

http://docuware/DocuWare/Platform/FileCabinets/c664c5fd-6ae4-48f6-bd2e-9ac81628089a/Documents/57/Fields/

With xml (or Json) as body, which contains index fields:

<?xml version="1.0" encoding="utf-8"?>

<?xml-stylesheet type="text/xsl" href="/DocuWare/Platform/Content/standard.xslt"?>

<DocumentIndexFields xmlns:s="http://dev.docuware.com/schema/public/services" xmlns="http://dev.docuware.com/schema/public/services/platform">

    <Field FieldName="NR_STATUT" FieldLabel="Nr statut">

        <String>02</String>

    </Field>

</DocumentIndexFields>

Kind Regards

Dear, 

I'm also struggling with Postman and the lack of documentation for the sdk. What I'm doing is using 'Fiddler'. Try to do a check in from the webclient and you can see the Xml used by Docuware within Fiddler.

I've done this for updating fields using Postman & Curl. It's take some times, but you will have a good idea what Docuware platform is waiting as xml.

Kind Regards

Dear Josef,

Do you have more technical details on your solution? If I understand, we set a trigger on a sql field, then, the SQL trigger is updating a field with the Docuware api? 

Kind Regards