Answers.Body: <p>We could create an option to disable the unregistering from events as this also solves the problem that if multivalue widgets are enabled for multiple sets of event fieldset, they do not work together well. This way we can get a better control towards the behaviour, also makes the solution possible for any widget.</p>
  
  <p>Regarding the loading event form URL, I think it will also be good to become a checkbox under "Event Registration Options" as people might not want to allow users to change some event setups through URL freely. </p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-06-04T14:48:02.083Z
Answers.Text: Patch implemented and merged as per suggestion above.
Answers.UserDisplayName: Guanhuan
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-02-14T22:37:59.930Z
Answers.Text: and the patch is ..... now in webform_civicrm? link? or does this now just work ie the event id can be used in the url? as what? eid=??
Answers.UserDisplayName: petednz - fuzion
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-05-18T17:15:09.477Z
Answers.LastActivityDate: 2015-05-19T21:21:10.247Z
Answers.LastEditDate: 2015-05-19T21:21:10.247Z
Answers.UserDisplayName: Guanhuan
Answers.Body: <p>I think the way you'd want to set this up would be with a hidden, exposed field for the event. This would allow the value to be selected, but not by the user. It seems that to get this fully functional, the webform-civicrm module will need 2 improvements:</p>
  
  <ul>
  <li>Allow event id to be specified in the url (note this may already be possible with the use of url tokens in the webform).</li>
  <li>Don't un-register participants if event selector is a hidden field. This seems like a good compromise solution to get the feature you want without removing the un-register behavior for non-hidden fields.</li>
  </ul>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-10-27T02:58:34.960Z
Answers.Text: I believe some of the above has been implemented now so that there is a setting on the Event section of the webform's civicrm tab so that you can 'allow events to be autoloaded from URL'
Answers.UserDisplayName: petednz - fuzion
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-05-15T22:22:18.850Z
Answers.LastActivityDate: 2015-05-15T22:22:18.850Z
Answers.UserDisplayName: Coleman
Body: <p>What we are looking to do is find a neat way to create a process for sending out an automated email from Civi with a link to a form of some type for a feedback or evaluation on the event that a person has booked on. We would ideally like this feedback or survey to be attached to the participant record in Civi (i.e. so its easy to see which event they are feeding back on and to find the feedback easily in Civi). I'm not sure if I can see any simple way to do this at the moment.</p>
  
  <p>So I guess the idea would be to send the email as a scheduled reminder with a checksum token to a webform, and also have in the url the event ID. The event id would then allow the user to update their participant record for that event with some custom fields which are the feedback fields (or we could copy a link to the webform submission into a text field).</p>
  
  <p>But to use 1 webform for all events and to pass the event ID to a field of event ID on the form, there is an issue that this will unsubscribe the contact from any other events that they were previously registered for.</p>
  
  <p>Any one got any thoughts on a solution?</p>
  
Tags: <civievent><webform-civicrm>
Title: Is there a way to automate event feedback using Civi and Drupal webform?
ThreadText: # Is there a way to automate event feedback using Civi and Drupal webform?
  
  (Asked by: username_0 on 2015-05-15)
  
  What we are looking to do is find a neat way to create a process for sending out an automated email from Civi with a link to a form of some type for a feedback or evaluation on the event that a person has booked on. We would ideally like this feedback or survey to be attached to the participant record in Civi (i.e. so its easy to see which event they are feeding back on and to find the feedback easily in Civi). I'm not sure if I can see any simple way to do this at the moment.
  
  So I guess the idea would be to send the email as a scheduled reminder with a checksum token to a webform, and also have in the url the event ID. The event id would then allow the user to update their participant record for that event with some custom fields which are the feedback fields (or we could copy a link to the webform submission into a text field).
  
  But to use 1 webform for all events and to pass the event ID to a field of event ID on the form, there is an issue that this will unsubscribe the contact from any other events that they were previously registered for.
  
  Any one got any thoughts on a solution?
  
  **Tags:** civievent, webform-civicrm
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_1 on 2015-05-18. Score: 3
  
  We could create an option to disable the unregistering from events as this also solves the problem that if multivalue widgets are enabled for multiple sets of event fieldset, they do not work together well. This way we can get a better control towards the behaviour, also makes the solution possible for any widget.
  
  Regarding the loading event form URL, I think it will also be good to become a checkbox under "Event Registration Options" as people might not want to allow users to change some event setups through URL freely.
  
  > **Comments:**
  > **username_1**: Patch implemented and merged as per suggestion above.  
  > **username_2**: and the patch is ..... now in webform_civicrm? link? or does this now just work ie the event id can be used in the url? as what? eid=??  
  
  ---
  
  ### Answer by username_3 on 2015-05-15. Score: 2
  
  I think the way you'd want to set this up would be with a hidden, exposed field for the event. This would allow the value to be selected, but not by the user. It seems that to get this fully functional, the webform-civicrm module will need 2 improvements:
  
  * Allow event id to be specified in the url (note this may already be possible with the use of url tokens in the webform).
  * Don't un-register participants if event selector is a hidden field. This seems like a good compromise solution to get the feature you want without removing the un-register behavior for non-hidden fields.
  
  > **Comments:**
  > **username_2**: I believe some of the above has been implemented now so that there is a setting on the Event section of the webform's civicrm tab so that you can 'allow events to be autoloaded from URL'  
  
  ---
  
  