#1 Revise the Success/Failure Emails...

[adymlincoln]

Revise the batch job emails. Currently they are built and sent from the AbstractBatch class. We should setup two simple tasks, one for successful batch jobs, one for a failure. These can then be added to the <jbjf-tasks> element as individual tasks.</jbjf-tasks>

Implementation Options:
1.) Add pre-built XML elements into the <jbjf-tasks>.
2.) Design two ITask classes and then use these directly from the AbstractBatch class.</jbjf-tasks>

[adymlincoln]

Logged In: YES
user_id=1741681
Originator: YES

This should allow individual batch jobs to decide whether to receive email at all. For instance, some batch jobs may only want to receive email during a failure. Others may want to receive both success and failure. Still others may not want any email at all.

[adymlincoln]

Perhaps we should use a generic Batch Job notification that determines whether to send a successful or failure email. A simple Task that accepts a parameter that indicates success/failure/warning, etc...

[adymlincoln]

Also need a way to separate success and failures. A request has been made to have the success emails be an "optional" thing while exceptions are always sent. There should also be a way to send Successful notifications to one mailbox and failures to another.

[adymlincoln]

Two new XML elements:
<email-success mailbox="email-success@address.com" attachments="a002">Batch Job Finished successfully...</email-success>
<email-failure mailbox="email-failure@address.com" attachments="a002">Batch job failed for the following reason(s)...</email-failure>

• To make the successful email optional, we can simply make the element optional. Thus, the framework detects the missing XML element and sends no Success email.

[adymlincoln]

Actually need a way to shut off success emails. Only send email when something fails seems to be a big need.