Closed (won't fix)
Project:
Rules
Version:
7.x-2.x-dev
Component:
User Interface
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
6 Feb 2011 at 18:06 UTC
Updated:
31 Jan 2019 at 01:43 UTC
Jump to comment: Most recent
Comments
Comment #1
fagoIt's by design. However, I think we should improve this a bit by:
- Adjust render() of a condition/action so the 'label' describes what cannot be changed any more.
In case of the condition, we could improve it to say "Compare node:property", for entity_create we could say "Create node". Having that scheme applied consistent to all conditions/actions helps I think.
Comment #2
burlap commentedI can understand this, however it makes cloning (or changing rules) a bit useless through the UI. OTOH it might be just me relying too much on workflow-ng ways, while the new Rules seem to follow different use patterns...
Comment #3
fagoadding tag
Comment #5
mitchell commentedI need to figure out how this relates to #1244738: Provide a description field to organize this.
@burlap: What were workflow-ng's ways?
Comment #6
fagoRelated: #1244738: Provide a description field
Comment #7
tr commentedI don't see anything left to do here. The "Data to compare" is fixed when the condition is created and added to the Rule - this has nothing to do with cloning. The data conditions seem to be the only ones where a parameter gets fixed. Regardless, there has been no participation from the community in almost 6 years and there doesn't seem to be any interest in adding this to D7 Rules this late in the D7 development cycle.
If you have a specific proposal and can contribute a patch, please open a new issue.