Launching a process on a record create is great but it would be significantly more useful if we can also launch on a generic Update rather than only on update of a specific record.
For example, we want to hook in some API events where a notification occurs on every Add, Update or Delete. Currently we can do the Add but to do the update we have to set a conditional Update process on EVERY record meaning thousands of processes.
Yes it has been mentioned in the forums that good design would mean you have just one update function and you can add to that but using that theory the launch on Add is unnecessary so why have one without the other?
The Launch On actions of processes are really good for extending functionality of an “entity” espace without having to continually touch the original code every time so I think adding an Update launch is a valid condition.
A launch On Delete would also be useful for some people but no important for us as we do a soft delete which would be caught by the update
I can't see it being too hard to achieve, should just be an on update trigger on the database side