As the title states, we have had a standard data directive that would fire on the SysTask table. Originally, this directive would be enabled by an In-Transaction directive that looked for a task description with “Process MRP” and a status that changed to “COMPLETE”. After 2024.1.10, the directive is not firing at all specifically for Process MRP SysTask entries. It is firing for other tasks (like report generations).
Any thoughts?
[edit]Alternatively, if anyone has any suggestions of alternative ways to trigger a function after a successful MRP run, I’m all ears. This was just the way I came up with several years ago.[/edit]
Huh, interesting. I guess that explains my issue, although it is odd that I am still able to send emails from a standard directive on SysTask, but it’s just not working for Process MRP tasks (or perhaps other processes, haven’t tested). Reports seem to still trigger the directive.
My unwanted opinion about systasks and I am so glad they did restrict it, and I wish they did in On-prem also. It has to potential to hide custom functionality that really should be in a scheduled function or a BPM that is related to a scheduled process or process set.
All this serves to do is hide scheduled automation functionality from where it should be, and that’s in the System Agent Schedules.
I have been burnt too many a time by people putting well meaning BPMs on Systask “Just to get the job done” and they were too lazy to think of a more sensible and future proof method.
On Premise people, please don’t do it… There is really no need.
