By rbrownell on

Hello All;

Despite using Drupal for almost 5 years now this is my first time actually posing a question on the forms. So here is my question.

Is there a way to get Rules to prompt a user for data (of any kind of field)?

Example: You use rules link (a wonderful module I recently discovered) to create a link to a rule. You then program the rule to prompt the user for a value (of any arbitrary field type) for inclusion in the rule as part of the execution of the rule, whether it be for value modification or something as complex as a file upload to a file field.

I tried Googleing this but couldn't find anything of relevance.

Thanks for reading this!

-Ryan

⋅ Categories: Drupal 7.x

Comments

cprofessionals’s picture

cprofessionals commented

Looking for the same thing. Did you ever get a solution? Odd there have not been any responses. Perhaps some additional activity on this post may entice an answer. Waiting anxiously.

paean99’s picture

paean99 commented

One solution would be to use Rules the same way you do for programming an event driven application.

  1. Create a form (some node edit or webform) to accept the inputs of the user.
  2. Create a first rule with the first phase of what you need to be accomplished.
  3. When it is time to receive the input, create an action to redirect to the form.
  4. Create a second rule that react on the form update and continue from there.

If it is necessary to pass variables or entities to the second rule from the first. Just use the form. Pre configure it with the necessary fields to save the variables and hide them (or not) in the view mode.
You can save the activity/interaction (log) by creating and not updating the node/form.

argiepiano’s picture

argiepiano commented

Thanks for the idea! It was easy to implement (I used Entityform to receive input before the second Rule). An effective solution to a common problem.

milos.kroulik’s picture

milos.kroulik commented

Thanks for the idea. In the end, I just solved it with:

  • ECK for a form
  • The first rule could be replaced with Entityreference Prepopulate. That way, I can use that date in rule, which is executed after custom entity save