Universal Custom Actions and Custom Action Triggers

It just occurred to me that ideas of Barry and Pat work really well together.

I’m imagining and interface where we can create the custom action sequences that Barry described, which would be available across the entire org (or module).
In another section of the interface, we would be able to identify universal ‘triggers’ the way Pat described, which would run in the background anytime their conditions were met.

Both get to a more pervasive use of the skuid ux, particularly the action framework, to perform global actions without apex or even javascript.

Love it.