Matthew Trembly Software Support Manager

I revised my previous reply.  I just checked the two most recent releases for 7.3 on-prem and cloud, and both show the Document Name value in my viewer in version 7.3.0.55868.

Steve, what's the build?  I checked two of my systems:

DocuWare Cloud 7.3.0.55868 shows the value of the Document Name field in the File Cabinet Viewer.

DocuWare on-premise 7.3.0.55868 shows the value of the Document Name field in the File Cabinet Viewer.


 

What about if you delete the tray entirely and create a new one in its place?

Yes, Workflow Manager includes an email workflow activity.

The Workflow Manager module is required in order to send an email with a DocuWare File Cabinet record (with or without annotations) as an attachment.  Task Manager is not required in addition to Workflow Manager.

I've never been able to make this work with Xerox either.

I tested this again in DocuWare 7.3, and it doesn't look like it's any more helpful - at least not with default logging.  I configured an AIX job that updates a file cabinet date field from a file connection.  After configuring the file connection appropriately, I went back and fudged some of the date entries so they weren't acceptable date formats.  The AIX job just skipped these without any meaningful mention as to which ones or why (see screenshot).

The AIX log isn't very helpful either: "Multiple file parse errors"

 

I just tested this, and there is more than one fault behavior.  I created two users: Designer and Controller. I created a workflow that gets an explicit user assignment and then sends an email using the value of a global workflow variable as the recipient email address.

1. If the workflow user exists, is active, and the email address is valid, then the workflow task is assigned to the workflow user and the email recipient receives the email.

2. When I deactivate the workflow user, the workflow task faults and is assigned to Controller and is visible to Controller as a workflow task awaiting the next known good activity.  It's also viewable in the workflow task monitor.  The task is not accessible by Designer in any view.

3. When I enter a bogus email for the global workflow variable, then the workflow faults and is assigned to Designer and is visible to Designer as a workflow task in error activity "General error" with prompts to Retry, Continue, or Stop.  Additionally, it is not viewable by Controller in the workflow task monitor.
 

Will you share?

In my experience, I feel like the workflow controller gets this task.  What did support say?

Very coherent and organized!  This is correct.