We want to start a discussion regarding future development of Notifications and appreciate the feedback from you!

The current problem is that, when we create a new Task or update a Task (for example the Email Task) we need to make appropriate adjustments in the Notification. The code is now split in two.

That leaves us with two options for future development:

1. create a new hybrid “Task Notification” which is a new form of Notification that uses code from the Task. This would mean that all Tasks that are available will be able to be used “as Notifications”.
2. remove Notifications and instead enhance flexibility and flow in Tasks in some way

Besides this we additions we want to add. Right now we only have Completed, On error, On Start. We are thinking about adding “On success” and “On timeout”.

Other requests we have received is that errors that are occurring in Notification should be transferred back to Task or Job. Currently Task do not fail if Notification fail for some reason.


Below is a list of posts which we might address in a future update. Please let us know if you find more posts:

http://www.visualcron.co....aspx?g=posts&t=2820 

---

Since we're on the subject of notifications... this kind of goes along with my same thought on 'Conditions', I would REALLY like to see the following, if possible:


Global Notifications
1. These Notifications are like they are today. Available to Every Task, Job, etc... This list can get quite long if you have a bunch of special one-off requests for notifications from different groups.
2. I'd use a Global Notification sort of as a generic e-mail of failure to our IT group (myself and my team).
3. I like to keep the list quite clean, so only truely generic notifications would be available globally.


Job Specific Notifications
1. These notifications would be unique to the JOB itself. If I create a notification for a specific Job, I don't want it to clutter up the list of Globally available notifications. I should only see these notifications if i'm looking at the job or one of the jobs tasks.
2. In our company, it is very rare, if ever, that we use notifications to the same group. Every Business Unit that has a job on our server sometimes requests that a job send a very specific message to a unique group of people on success or failure. I see no need to clutter up the huge list of globally visible notifications with these one-offs.

Obviously, I have the same thoughts on Conditions as well. I like the idea of very generic conditions. However, there are times where job-specific conditions are appropriate (such as looking for a specific file, that is unique to the task). In general, it just keeps the list nice and clean.

Brian

Hi, I can't give much feedback about architecture, but about the OnEvents.

It should be posible to define a class of return codes, that are not treated as errors. Based on this class of RCs a notification should be triggered.

Example:

Exit(101) notification to: legal@domain.com
Exit(102) notification to: it@domain.com

It could be called OnInformation notification. I know that it's possible to achieve this with triggers based on return codes, but as said in an other post it makes things more complex.