Unity Scheduler Outbound Email

[John_Snow1]

I am trying to build a notification into my workflow that sends an Email notification if a document has been in a queue for x amount of days. 

I have created the Rules/Tasks. 

I have created a unity scheduler task. 

But when I try to send a test notification nothing happens. I have been reading about "The Distribution Service" and am getting conflicting informationn about weather or not The Distribution Service is legacy technology that has been replaced by the Unity Scheduler. But in the Workflow MRG it states that workflow notifications need to go through the distribution service. Where can I check if this service is installed because the only information I can find in regards to installing a Distribution Service is for OnBase 14 and I am on EP1. 

[Cameron_Roberts · Accepted solution]

Hi John,

It is possible the Distribution Service is not configured properly. Can you please verify the information entered is correct specifically the email server settings.

Cameron

[John_Snow1]

I worked with my networking team to setup my mail server settings. When  I run a test notification out of Config and check it's status in Unity Management Console they all get stuck in a "Pending Send State"

[Cameron_Roberts]

OK, there are messages in the queue to route and the mail server is setup. It would appear to me that there is no Email Sending task in scheduler kicking off. Can you attempt to run the task manually via Unity Management Console? Locate the task that should be routing the mail then right click, run.  

[John_Snow1]

No Change when I right click run. Dont know if it changes anything but Those emails in the screenshot above are the ones that are generated with the generate notification button in config.

I'm a bit confused when it comes to the scheduler task. Whenever I create an email sending task in unity management console, it does not appear in studio as an option in the scheduler task tab. If I create workflow tasks they show up in studio.

[Cameron_Roberts]

The right click run should have taken everything but Distribution Service out of the equation and made an attempt to route the config generated test messages. Running Diagnostic console on the app server while attempting the right click run will give you an idea of what is wrong.