Postponed
Project:
Rules
Version:
8.x-3.x-dev
Component:
User Interface
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
23 Mar 2012 at 09:33 UTC
Updated:
7 Mar 2019 at 06:09 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
mitchell commentedComment #2
mitchell commentedCross referencing #987410: Ability to Move an Existing Rule Under a RuleSet.
Comment #3
mitchell commentedCross-referencing: #1498834: Facilitate rule configurations made entirely of components..
Comment #4
Anonymous (not verified) commentedI just wanted to create the same issue. Glad it's already done ;)
@mitchell, the screen seems to mix conditions and actions. ("add action" option below the conditions)
Are those circles in front of each condition checkboxes? I doubt, but I think it should be possible to pick a set of conditions/actions by ticking them. This way you could slice a complex set of rows into several components, and don't have to export all into one single compontent. It furthermore should be possible to slice a component into other (sub-)components this way.
All this makes it even more important to get a proper way of commenting rules (see #1244738: Provide a description field), because converting rule-parts to components tends to raise complexity of rules.
Comment #5
mitchell commented> the screen seems to mix conditions and actions
Yea, it should be "add a component."
> Are those circles in front of each condition checkboxes?
They're meant to be. It was just a crude example, but I guess it was too crude :)
> This way you could slice a complex set of rows into several components, and don't have to export all into one single compontent. It furthermore should be possible to slice a component into other (sub-)components this way.
Yea, that's how I think it would be used.
> All this makes it even more important to get a proper way of commenting rules
I agree. Let's postponed this till that one is done.
Comment #6
mitchell commentedarrr
Comment #7
mitchell commentedComment #8
tr commentedSounds like a reasonable feature, but it's not going to be implemented in Drupal 7 this late in the D7 development cycle. Especially since there seems to be little community interest.
Moving this to a D8 feature request. If you're interested in seeing this implemented, the best way is to provide a patch so we can try it out and come to agreement on how this should work and whether it should be in core Rules or in its own module.