Rules

Hi,
I'm currently playing around with the beta3 version of the module.
I have set up a trigger on adding a new node, with a few basic conditions and they work fine.
So I started trying to get some custom php conditions working and have hit a wall.

I have a taxonomy term on my node and want to do stuff based on its value.. What seems to be happening is the node save (rule) is kicking in before the save of the taxonomy terms because its blank when i view the node afterwards. I could be doing this completly the wrong have a look :

I'm a developer with some experience with using the Workflow module+Actions to manage the state of nodes and things that happen when nodes change state. I'm working on a new project now where I need a relatively complex workflow. Basically, we are developing a sort of Question and Answer board where the questions and answers need to be reviewed before they can post, so, for instance, all answer nodes associated with a question node have to be approved before the question node will be moved to a published state. While looking at the workflow module project page I found a link to the Workflow group, and then from there a link to the Rules group. I've installed both modules and it seems like they both fill different needs, but the way Rules is promoted it sounds like Rules is supposed to be able to handle workflows.

So, my question is, how are the two related? If Rules is supposed to be a superior replacement to Workflow, how would I go about setting up a similar workflow in Rules, where the content moves through various user-defined states (i.e. I need more than just the published/unpublished state)? Would Rules be able to help me out in my specific situation where I have interdependent node states?

Hi,

I'm attempting to develop a simple module that triggers an event when the watchdog is written to. My module also makes some configurable conditions about the watchdog message type and severity.

My event triggers okay. The conditions also work, but am completely confused about the presentation layer for Conditions. When using condition arguments with 'type' => 'value', they present themselves in the "Arguments configuration" part of the condition creation page. According to the docs (assuming i'm reading them right), type=value should be hidden fields.

This is a wiki page, so feel free to edit and improve it.

Q: I've installed the latest token module, but my tokens are still not replaced. What's wrong?
A: Don't use the actions provided by the token actions module - they don't work with rules and aren't available for use anymore in the latest module. So you can disable the token actions module when you use rules. Rules provides better integrated actions of the same kind anyway.

Attention developers, I've just committed a small API change to rules. Now you should use t() for help provided directly in your hook_rules_*_info implementation.

Example: The previous code
<?php
function node_rules_condition_info() {
$items = array();
$items['rules_condition_content_is_type'] = array(
'label' => t('Content has type'),
'arguments' => array(
'node' => array('type' => 'node', 'label' => t('Content')),
),
'module' => 'Node',
'help' => 'Evaluates to TRUE, if the given content has one of the selected content types.',
);

Check out http://more.zites.net/rules/rules-beta-1-drupalcon!

This is a list of modules, that provide rules integration. So once you install them, you have rules support as described.
It's a wiki page, so feel free to edit and improve it.

I've created a session proposal for the drupalcon :)

-> see http://szeged2008.drupalcon.org/program/sessions/rules-new-opportunities...

I'd also talk about the differences to the core actions and trigger module. Look at the session description for more infos.
Hopefully the session will be selected and I'll see you there.. :)

I've just released ALPHA1.

As you can see in the development status, there are still some important features missing. But the main UI (and the API) is already working - so check it out and give me feedback!

http://www.ubercart.org/forum/development/5555/rules_vs_conditional_acti...

Maybe we can team up and try to re-raise the support in rules...

This page will be updated, so you can track the development status here.

Improvements in comparison to workflow-ng:

Data Types:
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.
Status: implemented

I think it would be really useful to do a rules engine integration, so one can do service calls by configuring rules (per UI). It looks like one has already to specify the arguments for a service - so we would have to convert this to the format of the rules API and expose an action per service. Basically that should do it already.

Have I forgotten something? What do you think about this idea?