David Rutt Docuware Admin

We have been using Connect to Outlook for many years.  Just found out today that the "New" Outlook is not supporting COMs and that vendors will have to rewrite code.  We have the new outlook blocked by policy.  Has anyone had any issues with the new version?

I know this can be done because I am doing this in another workflow.&#160;&#160;<br> <br> I am taking a Workflow Global Value as the destination.&#160; The entry type is a File Cabinet.&#160; I am literally making the same WHERE clause, just using different field names.&#160; I set up an e-mail trap to report back all of the fields and they all come back correctly, except the field that accesses the other file cabinet and it is blank.<br> <br> The only difference is that the one that works was created in 7.2 and we just upgraded to 7.7.&#160; I hope that this upgrade is not going to break the feature.

Our reseller has a ticket in already, Tobias.&#160; It was escalated.&#160; Still waiting.

The thread titles says it all.&#160; It is just Document Processing.&#160; Everything else is working.&#160; Attached are the very helpful errors that pop up on the screen and Edge's dev screen.<br> <br> Server side on DocuWare.DocCap.log I find this.&#160;&#160;Authentication failed with HTTP response 500 and ApiFaultCode 'Unknown'.......&#160; Well, Edge told me that.&#160; Digging further I find this.<br> &lt;event timestamp=&quot;2023-05-11T11:55:21.6136834-04:00&quot; level=&quot;Warn&quot; logger=&quot;DocuWare.Web.DocProcBase.Controllers.Util.SettingsServiceAuthenticationAttribute&quot; SequenceID=&quot;32&quot; Thread=&quot;87&quot; DomainName=&quot;XXXXXXX&quot; WindowsUserName=&quot;XXXXXXXX&quot;&gt;&lt;message&gt;Session for SettingsService 'https://XXXXXXXXXXXXXXXXXXXFQDN/DocuWare/Settings/SettingsService.svc' could not be validated due to unexpected error&lt;/message&gt;&lt;exception&gt;System.ServiceModel.Security.SecurityNegotiationException: Could not establish trust relationship for the SSL/TLS secure channel with authority 'XXXXXXXXX'. ---&amp;gt; System.Net.WebException: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. ---&amp;gt; System.Security.Authentication.AuthenticationException: <em><strong>The remote certificate is invalid according to the validation procedure.</strong></em><br> <br> The certificate is working for ever other part of Docuware so how can this be the certificate?&#160; Has anyone come across this?&#160; There was a prior thread that was close to my problem, that did not go into much detail.&#160;&#160;

Tony, I know your thread it two months old but, just a heads up.&#160; You will need to implement SSL first before your upgrade if you have not already.&#160;&#160;

I have two users in Accounts Payable that are assigning tasks in the same workflow.  I already have a substitution list that User A is first and User B is second.  

When user B enters a new task from her tray, the tasks is owned by User A and replies to that task will go to User A. Is there a way to assign ownership of the task before it hits the workflow or am I going to have to have a parallel workflow that that User A and B are separate?

 

If you are selecting users in that manner, they will all get the same task.  If any one of them take action on it the task is completed.

Do the people that are being sent the task change at all?

 

Thanks, I just wanted to see if anything has changed.

Dirk, 

How are you assigning the task to the users?  There are a few ways to do this.

 

Gregory,

Did you ever get this resolved?