Not sure if this feature is already available but, if so I can't find it.

Is it possible we have a new paramater for variables of prior, i,e, {TASK(Prior,StdOut)} where we can use "Prior" instead of "Active". This then enables generic tasks, i.e. Email tasks specifically, to be cloned between jobs where the body contents can remain the same and/or at least work after a fashion without having to enter the task Ids everytime.

When using notification the Active is fine, but when using follow-on tasks the Active doesn't apply any more.

Thank you.


Graham

Hmm, the 'Prior' keyword to see the previous output of a task. Could be a nice addition. You're working on your sql output and email jobs right? You are doing some cloning, but you have to keep changing the email body due to the task id...... 🤨

---

Yes.... but principal applies to other things. Why keep re-inventing the wheel if you can just clone tasks from one job to another and they simply work o:)


Thats why using notifications instead of email task is neat as you can have multiple task in the same job and use the Active parameter.

Thanks for the comments and the request. Hopefully it is not too hard to add this functionality.

---

You have PrevTask and LastTask now.

---