Allow for a task to depend on more than one condition, that is, the task should be run only after all of the selected conditions are verified. This possibility was implemented in the old version of When as a plugin in the "wizard" interface.
The triggering conditions can be verified at any time, and once all of them have had a positive check, the task depending on their outcome should be run. The plugin was in fact called Confluence, but the name of the feature could be different in this version of When. It should be implemented with no modifications to the core scheduler, whenever: since whenever also has Lua capabilities, it should be relatively easy to use them in order to build lightweight private items to reach this goal.
Allow for a task to depend on more than one condition, that is, the task should be run only after all of the selected conditions are verified. This possibility was implemented in the old version of When as a plugin in the "wizard" interface.
The triggering conditions can be verified at any time, and once all of them have had a positive check, the task depending on their outcome should be run. The plugin was in fact called Confluence, but the name of the feature could be different in this version of When. It should be implemented with no modifications to the core scheduler, whenever: since whenever also has Lua capabilities, it should be relatively easy to use them in order to build lightweight private items to reach this goal.