Workflow-ng is a rule-based event driven action evaluation system.
This means, that one is able to configure various actions, that will be fired on certain events.
Workflow-ng allows you to configure actions to be fired on various events - e.g. if a user is creating a new content, the event "Content has been created" occurs. So workflow-ng allows you to react on this events, by firing actions. There are a lot of different events available and contributed modules can even introduce new events. Some more examples would be
• a user has logged in
• content has been viewed
• a comment has been created
So workflow-ng events have nothing to do with calendars.
Workflow-ng provides various actions, which let you actually do something. Some examples for actions are
• send a mail to a user
• unpublish content
• delete a comment
Workflow-ng provides some configurable actions, but again, contributed modules may provide further actions.
So let's have a look at how actions & events play together:
This is an example, that shows how workflow-ng is firing actions. It shows an action, which is configured to be fired on the event "Content has been updated".
Conditionals allow you to configure actions, that are only executed if the configured conditions are met.
Again, let's have a look at how conditions interact with actions and events:
So the action, is only fired, if the condition "Content is a Story" is evaluated to TRUE.
Workflow-ng provides some configurable conditions and contributed modules may provide further conditions.
Workflow-ng also supports negating conditions as well as the concept of condition groups, which are logical operations like OR and AND.