This page will be updated, so you can track the development status here.
Improvements in comparison to workflow-ng:
Arguments had an "entity type" in workflow-ng. This has been changed to data types, so that it fits also for primitive data types like strings and numbers. So rules contains support for the usual data types like node and user, but in contrast to workflow-ng it also treats strings as data types.
Also a lot of internal code has been restructured and improved - now rules is keeping an internal array of variables.
Writing conditions / actions:
Writing conditions and actions has become even easier. Thanks to input evaluation system (see below) you don't have to care about token or php evaluation yourself. Furthermore you don't need to specify the to be saved settings like before in workflow-ng anymore, as rules will generate useful default settings for you, which can be altered if desired.
As now data types like "string" are also supported one can also add needed strings to the argument list. For such primitive data types rules will provide a form for entering the data, which can be overridden and customized by the action. You need not do this, but in some cases it can be useful, e.g. for integrating with existing systems already specifying these arguments like the services module.
Also providing new variables has been simplified and works more straight forward.
For the token integration rules will come with an input evaluation API and implementations for token and PHP input evaluation. So you can also do some simple php calculation in the input fields. Strings (and possible other data types) will be automatically evaluated so you don't have to care about this when writing actions.
Status: implemented. For token integration see this issue.
The whole API has been overhauled to also work with rule sets - this are set of rules that work independent from events. So they are like a subroutine, which can be customized or also added by the UI.
Rules supports an improved file inclusions system, which only includes the module integration files if necessary. Furthermore the internal caching system has been improved.
Status: Implemented, needs documentation.
Rules supports scheduled rule evaluation - so you'll be able to schedule everything.
Status: implemented, views integration is missing
Now label callbacks are supported for conditions, actions and new variables. So one can specify a better suiting label for configured conditions/actions, e.g. the "content is type" condition set to "page" will get the label "content is page". Of course one can still customize the labels per UI too.
Drupal 6.x Actions support
The previously just for developers logging of rule execution has been improved to look better and provide a better overview. There will be a setting for enable this logging, so this assists one during the creation of rules.
Rules comes with a small module, which comes with some simple tests - which test the API to work correctly.
Port from workflow-ng status
- Evaluation Engine [done]
- Basic UI [done]
- Port the whole module integration [done]
- States [TODO]
- CClinks [TODO]
- Per Entity Logs [TODO]
- Upgrade procedure [done]
Modules shouldn't start porting their integration not before the first BETA release is there.
Todo list before a first BETA release:
* write developer documentation [in done]
* implement scheduling [done]
Module integration status: