Go to Rules > Components (admin/config/workflow/rules/components).However, if you have a choice between using a Views filter and an extra Rules Condition, I recommend to go for the Views filter, because that will reduce the number of your iterations in your Rules loop (performance!).You need to create a rules component first: Typically the things you cannot, or have not yet, expressed as a Views filter. Optionally, you may also want to add whatever extra Rules Condition(s), also up to your own imagination.So at that point it's a piece of cake to adapt the value of that list widget for the node you're processing in that loop. At that point you'll have all data from each column of your Views results available as so called Rules Parameters. For each iteration step in your Rules loop, perform a Rules Action to " do your thing" (= to set a list widget from active to ended).Remove that "add condition" (in the custom rule you started) and, instead, use the Views Rules module to iterate over each of these Views results in a Rules action, using the Rules technique known as a "Rules Loop".Important: use a Views display type of "Rules". You'll need these View fields later on as values to be processed by your rule, "to set a list widget from active to ended*" (as in your question). Whereas that view has fields (columns) for whatever is needed in subsequent steps, e.g the node ID, the date field, and possibly other fields as well.
#Drupal rules loop build variable send mail how to
Therefor some more details about how to move forward using these modules: The previous quote may seem a bit cryptic (it may make you think like "so what, how can this help me?"). Provides Views directly as Rules actions and loops to seamlessly use view result data. Some details about this module (from its project page): Yes you should be able to get this to work using the Rules module to implement what you're looking for, but I recommend you to also combine that with the Views Rules module. Sorry for my english, I hope you understand everything :) I state: I do not know if it works but at least it should direct you towards the right path Add an action in the loop (click on the link to the right of loop row) and select the component created in the point 2 and pass the variable provided by loop.Now add a loop in parameter list use the variable provided by 'Fetch entity by property'.Data selector: the variable created at the point 8.Now add another action 'Fetch entity by property'.Then write the value of this variable just like the machine name of content type that you want to cycle on (if you want you can change the name and machine name of this variable in the section below).Jump the conditions section and in the actions:.Now go to Rules (admin/config/workflow/rules) and create the rule with action on cron maintenance (as you have already done).In the component add the condition 'Data comparison' and select node:type.Machine name: Use the same name of the label but set here only lower case and underscore.Set a name for this component and in the table below select:.Then create a new component and select 'Rule' from select list.You need to create a rules component first:
0 kommentar(er)
