Public Profile · DocuWare Support Portal

Joined: 3/4/2019

RE: Workflow - Approval of documents when in use by another user.

Mon, 11 Sep 2023 15:08:23 GMT – Workflow - Approval of documents when in use by another user.

Hi César,

you could enable the automatic log out feature, which will log out the user once he is inactive for a specific period of time.
You'll find these settings in Configuration > "Organization Settings" > Tab "Security" > "Session timeout" > "Automatic log out"

Viele Grüße / With best regards,

--

Gerardo Lisanti
Team Leader Product Management | DocuWare GmbH
RE: Feldinhalt aufteilen (Straße mit Hausnummer)

Mon, 11 Sep 2023 15:00:09 GMT – Feldinhalt aufteilen (Straße mit Hausnummer)
Hallo Nico, hallo Simon,

ich habe ein wenig recherchiert. Mit diesem Regex scheint es zu klappen: [0-9]{1,5}[/ \- 0-9 a-z A-Z]*

Damit sollte man ab version 7.9 im Workflow mithilfe der neuen Regex Funktionen die Hausnummer herausfiltern können.
Ich nutze dafür Regex.Match():
Regex.Match(DW_ADRESSE,"[0-9]{1,5}[/ \- 0-9 a-z A-Z]*",false,false,true)

Um die Straße zu erhalten nutze ich Regex.Replace(), um die zuvor identifizierte Hausnummer aus dem String mit "" zu ersetzen:
Regex.Replace(DW_ADRESSE,"(GV_HausNr)","",true)

Die Testergebnisse sehen vielversprechend aus:

Straße des 17. Juni 106-108
- 106-108
- Straße des 17. Juni
Straße des 17. Juni 12/c
- 12/c
- Straße des 17. Juni
Stuttgarter Strasse 22 - 24 A
- 22 - 24 A
- Stuttgarter Strasse
Hauptstraße 22-1
- 22-1
- Hauptstraße
Blümchenweg 3
- 3
- Blümchenweg
Viele Grüße / With best regards,

--

Gerardo Lisanti
Team Leader Product Management | DocuWare GmbH
RE: Workflow Design / Task

Mon, 11 Sep 2023 14:13:55 GMT – Workflow Design / Task

Hi Jagan,

you need to assign all remaining items to keyword "Checklist" again. As Simon mentioned you can use the Filter() function in an aritmetic expression, to remove specific items. In other words you get the current content of keyword "Checklist", remove the value "Payment" and write the remaining items back to the keyword field.
The syntax should look like this: Filter(DW_CHECKLIST,"Payment",false)

For the condition you can user Count() to check the remaining items in the "Checklist" and send it back to the user, if it is not 0:
The syntax should look like this: Count(DW_CHECKLIST)=0

Viele Grüße / With best regards,

--

Gerardo Lisanti
Team Leader Product Management | DocuWare GmbH
RE: Condition of my workflow

Fri, 07 Jul 2023 09:49:29 GMT – Condition of my workflow

Hi Noham,

currently the only option I see to achieve what you've described is to do logical tests using iif() and have them nested, like this:

CBOOL(IIF("CODE1"= GV_CODE_CLIENT, "1", (IIF("CODE2"= GV_CODE_CLIENT,"1", (IIF("CODE3"= GV_CODE_CLIENT, "1", (IIF("CODE4"= GV_CODE_CLIENT, "1", "0"))))))))

CBOOL at the beginning is needed to convert the outputs 0 = false or 1 = true.

With DocuWare version 7.9 (autumn 2023) you will be able to check the contents of a list variable (keyword), index field of type keyword or an index table column using a LINQ function. With this you can check if the list contains one or multiple values, or even compare 2 lists.

Example:
GV_CODES: { "1", "2", "3", "4" }
GV_CODE_CLIENT: "4"

GV_CODES.Contains(GV_CODE_CLIENT)
Returns: true

Viele Grüße / With best regards,

--
Gerardo Lisanti
Team Leader Product Management | DocuWare GmbH
RE: Create new user via REST API not working

Tue, 04 Jul 2023 14:57:59 GMT – Create new user via REST API not working

Hi Chema,

please make sure that you pass the Content-Type: application/vnd.docuware.platform.createorganizationuser+json in the HTTP header.
Only then the POST request is considered a "Create User" request.

With Content-Type: application/json the system tries to update an existing user, where the user's GUID is required.

Viele Grüße / With best regards,

--

Gerardo Lisanti
Team Leader Product Management | DocuWare GmbH
RE: How can I copy Table Fields to Index Values in Workflow

Thu, 25 May 2023 12:21:30 GMT – How can I copy Table Fields to Index Values in Workflow

Hi Filippo, to achieve this, you can use the "Arithmetic Expressions" by specifying the table column of an index table. This will return a list of the values of each row in that column. However, if the target is an index field that can hold only one value, you must specify an index (starting at 0) to return only the value of a particular row. Example: You have a table "Line Items" with 2 columns, ID and GL Code:   <table border=1 cellpadding=1 cellspacing=1 style="width:500px;"> <tbody> <tr> <td>ID</td> <td>GL Code</td> </tr> <tr> <td>1</td> <td>000-4000</td> </tr> <tr> <td>2</td> <td>000-5000</td> </tr> </tbody> </table> With the expression <code>DW_LINE_ITEMS[LINE_GL_CODE][0]</code> you get the value "000-4000", because index 0 is applied and the value of the first line is returned. Whereas with the expression <code>DW_LINE_ITEMS[LINE_GL_CODE][1]</code> index 1 is applied and the value of the second line is returned: "000-5000". --- <div>Gerardo Lisanti Team Leader Product Management  |  DocuWare GmbH</div>
RE: Week number

Fri, 24 Mar 2023 08:17:38 GMT – Week number

Hi Vorawooth, you are almost there. The DatePart() function returns a Variant (Integer). That means you can write the returned value to a field/variable of type "numeric" in DocuWare Workflows. I suppose you are trying to write to a field/variable of type "text". For this you need to convert the returned value to a string using CStr(). So the expression looks like this: <code>CStr(DatePart("ww", GV_Date1))</code> Viele Grüße / With best regards, -- Gerardo Lisanti Product Manager  |  DocuWare GmbH
RE: Hyperlink per E-Mail soll gezielt einen Dialog verwenden je nach Dokumententyp

Fri, 17 Mar 2023 10:22:10 GMT – Hyperlink per E-Mail soll gezielt einen Dialog verwenden je nach Dokumententyp

Hallo Herr Holtstiege, Dialog und Ergebnislisten müssen den einzelnen Bneutzern zugewiesen werden. Beim Teilen eines Dokuments wird der generierte Link generisch für das Archiv erzeugt. Beispiel: <code>https://.../DocuWare/Platform/WebClient/Integration?fc=ae156510-ffa8-48b1-a3ec-baec3180669c&did=641&p=V</code> Dadurch wird sichergestellt, dass das Dokument auch den über den Hyperlink geöffnet werden kann, wenn dem Benutzer die Ergebnisliste nicht zugewiesen ist. Man könnten den Parameter fc= mit dem Parameter rl= austauschen und die enstprechend Ergebnisliste mitgeben. Dann wird das Dokument auch mit der angegebenen Ergebnisliste bzw. dem hinterlegten Indexdialog geöffnet. Beispiel: <code>https://.../DocuWare/Platform/WebClient/Integration?rl=c68db269-dbda-4b32-91e0-83ab3adda61f&did=641&p=V</code> Das kann jedoch nicht als Standard eingestellt werden. Eine Alternative wäre statt dem Dokument die Ergbenisliste zu teilen. Den Menüeintrag finden Sie in der oberen rechten Ecke einer Ergebnisliste unter den drei Punkten. Viele Grüße / With best regards,   --   Gerardo Lisanti Product Manager  |  DocuWare GmbH
RE: Begrenzte Auswahl von Feldern für die Verknüpfung mit Intelligent Indexing

Fri, 17 Mar 2023 09:43:40 GMT – Begrenzte Auswahl von Feldern für die Verknüpfung mit Intelligent Indexing

Hallo Herr Holtstiege, der Grund hierfür ist möglicherweise, dass das Feld im Ablagedialog nicht sichtbar ist. Intelligent Indexing kann nur Vorschläge für eingeblendete/sichtbare Felder vorschlagen. Um die Sichtbarkeit eines Feldes im Dialog zu ändern klicken Sie in den Dialog-Einstellungen auf das "Auge" ganz rechts. <img style="width:605px;height:66px;"> Viele Grüße / With best regards, -- Gerardo Lisanti Product Manager  |  DocuWare GmbH
RE: Check out/in document to/from basket with rest API

Wed, 15 Mar 2023 14:24:34 GMT – Check out/in document to/from basket with rest API

Hi Pierre, Check-Out to document tray should be: PUT  <code>{{ServerUrl}}/{{Platform}}</code>/FileCabinets/<code>{{FileCabinetId}}</code>/Operations/ProcessDocumentAction?docId=<code>{{DocumentId}}</code>   <pre class="linenums prettyprint">{ "DocumentAction": "CheckOut", "DocumentActionParameters": { "$type": "CheckOutActionParameters", "FileCabinetId": "b_99f4b29d-a2b0-4196-a4a6-67cb74fd865c" } }</pre> Check-In from document tray should be: PUT  <code>{{ServerUrl}}/{{Platform}}</code>/FileCabinets/<code>{{DocumentTrayId}}</code>/Operations/ProcessDocumentAction?docId=<code>{{DocumentId}}</code>   <pre class="linenums prettyprint">{ "DocumentAction": "CheckIn", "DocumentActionParameters": { "$type": "CheckInActionParameters", "Comments": "", "DocumentVersion": { "Major": 2, "Minor": 0 } } }</pre> Note that the DocIDs are different for Check-Out and Check-In. Merging of sections is called "staple" (1 section) and should be: POST  <code>{{ServerUrl}}/{{Platform}}</code>/FileCabinets/<code>{{DocumentTrayId}}</code>/Operations/ContentMerge   <pre class="linenums prettyprint">{ "Documents": [ 221, 220 ], "Operation": "Staple", "Force": true }</pre> Note that stapling is only supported in document trays. This ensures that documents are not lost in the filing cabinet under any circumstances. Also, if the documents are already "clipped" (2 sections), you must first unclip and then staple. POST  <code>{{ServerUrl}}/{{Platform}}</code>/FileCabinets<code>/{{DocumentTrayId}}</code>/Operations/ContentDivide?docId=<code>{{DocumentId}}</code>   <pre class="linenums prettyprint">{ "Operation": "Unclip" }</pre> So the procedure would probably be: <ul> <li>copy the document to a document tray (Transfer)</li> <li>unclip</li> <li>staple</li> <li>store</li> <li>delete the old document in file cabinet</li> </ul> Viele Grüße / With best regards, -- Gerardo Lisanti Product Manager  |  DocuWare GmbH

‹
1
2
3
4
5
6
7
8
9
…10
›

Gerardo Lisanti Team Leader Product Management

Get Help