We have several ReportCaster schedules that distribute bursted output to sftp.
We want to send an email to our customers after the output has been placed in their sftp box.
However, in ReportCaster we can only choose for a single way of distribution, either sftp or email.
The email notification in the last tab is not an option as it emails the RC log which is not suitable to send to our customers, we want to send a proper email. Next to that we want to set this in general to On Error to alert us on failed jobs.

We have thought of the approach to send an email in the task/procedure with EDAMAIL, but this has the disadvantage that the sftp distribution has not yet taken place and could fail.

I searched previous topics but could not find any solution, but I assume someone else has thought of this before.

Martin.

This message has been edited. Last edited by: Martin vK,

Thinking outside of the box here, as I haven't had cause to use SFTP, what does the caster log show?

If there's any useful info as to the success or otherwise of the FTP process then perhaps use a post-process to kick off a stand alone schedule that checks the log and emails someone depending upon what the log(s) contain?

Just a thought but it might stir some thought process.

T

A post-process procedure is an interesting idea. I have never used it, so I tried.
Unfortunately it does not solve my request. The post-process procedure runs immediately after the Task it is connected to. At that time the ftp distribution in ReportCaster has not yet taken place.

Anyone else some suggestion how to solve this?

I worked out a different approach and check the RC repository after running all the schedules. A procedure checks all recently run RC schedules with (s)ftp distribution and if run correctly they it will provide an email. It will take parameters (like email settings) from the same schedules which can also be collected from the repository.