Closed (fixed)
Project:
Rules
Version:
7.x-2.x-dev
Component:
Rules Engine
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
3 Mar 2010 at 05:06 UTC
Updated:
19 May 2010 at 11:10 UTC
I've created a rule that when post is created in our ticket system, we have a node reference CCK field were the user can be selected; an email is sent to that user notifiying. I made a rule for each tech that sends an arbitrary email to their email if their name is selected on the ticket. That part works fine as long as one tech is selected.
If we select more that one tech it does not ever send the email out. Is there a way to make the rule criteria more of a contains rule as opposed as looking for an exact match. If you select three techs then it wll not send those emails out.
Comments
Comment #1
emilyf commentedI have this same problem with multi-value fields. I have a multi-value field and I want all added values to go out in an email. Rules only takes the first value and does not include all the additional values.
Comment #2
YK85 commentedsubscribing
Comment #3
mayerwin commentedsubscribing
Comment #4
mitchell commentedThis gap has existed for a while. Rules-1 definitely can't populate multi-valued fields or read them. And I doubt it will get fixed in 6.x, but it would be likely in 7.x because fago focused on rules-2. Also, rules-2 has lists/looping support.
Let's see what fago wants to do in 7.x and then look at 6.x
Comment #5
fagoWith rules 2.x you can do so. Multiple values == List of values. So there is an action to add values, however as of now there are no tokens generated out of lists. Still you can e.g. loop over a list of recipients and send a mail to each.
Setting this issue to fixed, as it's generically possible. For more specific feature requests like multi-value-tokens open separate issues please.