FlyingDiver wrote:Am I close?
That's part of the issue (basically, it's an Action object which currently doesn't know anything about how it was configured or from where it was fired).
But the other thing is that if we are going to do this, we're going to do it the right way, which is to pass that data to all actions (not just scripts). Which means that we have to retrofit any action config UIs (where it makes sense) to use any of that data, including the script execution actions, and that's Mac Client work (which is completely different than server work). It's unlikely we'd use an environmental variable for a variety of reasons (though without completing the design I don't know for sure), but probably rather passing the actual IOM object(s) to the script somehow which will also likely be needed when we implement Python script conditions as well. Also, we really need to complete the Trigger and Schedule IOMs so that everything about them can be referenced (including other actions, delays, etc., which might be useful particularly to scripts).
So, bottom line, I don't think either of us wants to implement a solution that's not a full and well thought out solution, and there are other things that need to be done in a specific order which will make the final implementation become more obvious when we come to it.