module triggers / scheduler / event manager

[habreu]

Hopefully you don't mind left field ideas...

I've been adding lots of products and rebuilding my Power Search index lately. It just dawned on me that I haven't updated our Google sitemap (with Moogle) since last year.

What I was wondering is if it would be possible to architect something so that module developers can add events that could be triggered securely by a sort of Miva task manager.

For example if Power Search exposed a 'rebuild_index_trigger', and Moggle a 'create_submit_sitemap_trigger', and perhaps an email 'notify_task_status_trigger' then using this Miva 'scheduler' I could add these in order I wanted. Then either they get triggered automatically on a schedule, or in my 'events' list I could manually run all three with a simple click of one button.

Hope this makes sense.

[lesliekirk]

Don't quote me, but I think this is in the Miva Roadmap. I'm sure Rick will chime in with more details.

[habreu]

I heard something at Mivacon but didn't realize it might fill this need. I'm looking forward to exploring Miva more fully once our new web site is complete, and the updates come along.

[Gordon - Phosphor Media]

I like the idea of modules exposing triggers. It might be implemented by a new module feature where modules register their triggers on installation.

[habreu]

That's what I was thinking. Something like IFTTT or Outlook's rules system, where you could name your custom 'rule' then select from a list of registered triggers to form a chain or group and save. I'm sure some problems could be introduced so Miva might have to have some limits built in to avoid runaway process - for example if the person doesn't think through every step and ends up firing say 'submit sitemap' or saving a new copy of a file for every page load. Also it might be useful to have some built in 'base' functions in Miva like 'send notification - to send an email, perhaps a 'set/reset flag' would be cool that allowed you to set a flag when a trigger is fired, and then run/not run the 'rule' if Flag1 is set - so you want to run the process once per day for example, then can reset the flag at end of day. Just brainstorming a bit.