It would be nice to have a new 'Action: Stop evaluting other rules' to avoid other rules to be fired after the current.
For example take two rules, first has condition New user registration and redirects to a specific path, the second has condition User logged in and redirects to another path.
After user registration user is also logged, but i do not want to fire both rules. So I think this new action would solve this problem. Sure there are also other situations where a stop condition would be userful.

Comments

mitchell’s picture

Version: 6.x-1.4 » 7.x-2.x-dev
Component: Rules Engine » Rules Core

New features go to 7.x first, then can be backported.

Perhaps there's another workflow that can achieve the same desired behavior without adding a new action.

jay-dee-ess’s picture

Issue summary: View changes

+1

This would be great (though I have a feeling that the reason why I need it is because I'm not effectively using components).

tr’s picture

Status: Active » Closed (won't fix)

Won't do this in D7 at this point in time. If there's interest in doing this in D8/D9 please open a new issue and provide a patch.