Pedro E. Gonzalez-Santini Gm

Thanks Tobias. Yes, I am using the new Knowledge Center. I can now add metadata specific to the Acrobat Sign document being processed (for example, Account Number) by inserting two steps in the Power Automate flow. First a Compose Data operation and then an Initialize Variable. The variable is then used when storing the document in DocuWare. 

The Power Automate connector available since June 2024 (only in DocuWare Cloud) creates many possibilities.   Perhaps we should discuss its use in a dedicated section.  These links provides basic information: https://learn.microsoft.com/en-us/connectors/docuware/ and https://help.docuware.com/#/home/94045/2/2.  If someone has other suggested references they will be welcome. 

As an example of a use case, we are storing in DocuWare documents that are processed in Adobe Acrobat Sign. Documents flow to DocuWare file cabinets and are indexed with a few fields. We need to capture additional metadata, however, and that is where we need help. 

Hello, Jean.  Admin IQ looks good. There is also this solution presented at DocuWorld Americas 2024: https://weareintuitive.com/process-management/intuitive-for-docuware/

The contact person in USA is jodi.lindner@ecoprintq.com 

Regards.
 

Hello, Tobias. Thank you for the detailed response. We suspected the OAuth 2.0 authentication might be a problem but I hoped perhaps the user would be forced to log into the on-premise system each time a document was to be stored or once per session. Since that is not the case, I guess the dwcontrol route is appropriate. To you knowledge, is adding OAuth 2.0 to the API in the pipeline?<br> <br> We might also add a Cloud 4 DocuWare account and have the incoming documents go there and then synchronize with the local system. For search and retrieval from within Power Apps to the local system do you think URL Integration will work?<br> <br> Finally, when you indicate &quot;Also you could use Webhooks to send information from DocuWare to a webhook on the Power Platform and process it there&quot; are you referring to search and retrieval or also to storing documents?<br> <br> Regards.

This page explains how to build a custom connector that user the REST API. It seems the way to go.&#160;https://learn.microsoft.com/en-us/connectors/custom-connectors/<br> &#160;

The Power Apps system is developed using the Model-driven, not the Canvas approach.&#160;

An existing on-premise client (a government regulatory agency) has developed various applications for internal processes using Microsoft Power Apps. They also use DocuWare as the system of record to store their documents.&#160;<br> <br> One of their Power Apps is simply used to register incoming correspondence, many still on paper, others by email and usually printed. Items are given a control number, assigned a few fields (sender, date, subject) and then distributed to the pertinent area for handling.&#160;<br> <br> From then on, each area has its own processes. Several manage cases on paper and eventually the completed files are scanned into DocuWare. Automating these processes is desired over time nd may or may not involve DocuWare Workflow Manager. It is not licensed at this site.&#160;<br> <br> The immediate objective is to be able to store incoming mail in DocuWare from the incoming correspondence system and later to be able to retrieve documents stored in DocuWare from the correspondence system and subsequent systems.<br> <br> Storing documents will require copying a document to DocuWare with metadata pulled from the item being recorded in the correspondence system.&#160;<br> <br> Regarding communications and authentication, sInce Power Apps is a Microsoft 365 Cloud application and DocuWare is on-premise, will web services need to be developed and will webhooks be available? Maybe Power Apps provides OAuth 2 as used in email authentication with Microsoft 365.<br> <br> I think URL integration will work in this case as well as the REST API.&#160;<br> <br> Any guidance and comments will be welcome.&#160;

Hello. I have the same need. Does the Workflow Manager now in version 7.7 allow this without a web service?  If not, can you provide a bit more detail on how the web service would work? This is for a Cloud installation. Best regards.

A couple of clients experienced this as well and with different KB updates. Deleting recent updates resolved this temporarily but in some cases the updates were automatically reinstalled and then it appears not all workstations experienced the error.  So far it is inconclusive. 

DocuWare version 7.7 replaced the Solr 4 full text engine that included Tomcat with the improved Solr 8 engine. For security, it is recommended that the default files be removed. Can this be done without affecting the DocuWare system?

References:

Synopsis

The remote web server contains default files.

Description

The default error page, default index page, example JSPs and/or example servlets are installed on the remote Apache Tomcat server. These files should be removed as they may help an attacker uncover information about the remote Tomcat install or host itself.

Solution

Delete the default index page and remove the example JSP and servlets. Follow the Tomcat or OWASP instructions to replace or modify the default error page.

https://www.owasp.org/index.php/Securing_tomcat

https://www.rapid7.com/db/vulnerabilities/http-tomcat-default-install-page/