Answers.Body: <p>Webform validation module can run a number of checks on specific fields on your webform - <a href="https://www.drupal.org/project/webform_validation" rel="nofollow">https://www.drupal.org/project/webform_validation</a></p>
  
  <p>If you're worried about SPAM submissions install Mollom: <a href="https://www.drupal.org/project/mollom" rel="nofollow">https://www.drupal.org/project/mollom</a> - and configure it to monitor your webform submissions.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-05-12T15:59:01.340Z
Answers.Text: Sounds great,thank you; we are more in need of "human validation" tool though.
Answers.UserDisplayName: yurg
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-05-12T16:08:31.927Z
Answers.Text: As in, you're trying to make sure the webform submission was made by a human (and not a bot), or you need a human to check the data before Civi is updated?
Answers.UserDisplayName: Allen Hutchison
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-05-12T18:40:45.713Z
Answers.Text: Hey yurg - please be more/very specific as to what you meant when you wrote "check data" - or we're just throwing darts in the dark :-)
Answers.UserDisplayName: KarinG - Semper IT
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-05-13T16:14:44.090Z
Answers.Text: @Allen Hutchison The latter I guess: default data consistency checks are fine, it's more about content check group of "moderators" performs on "decent users" submission.
Answers.UserDisplayName: yurg
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-05-13T16:26:30.523Z
Answers.Text: @ KarinG You're absolutely right, sorry; have just thought about this for a while, so it is clear for me only.. It's a content checks, hence, "human touch" is needed.
Answers.UserDisplayName: yurg
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-05-13T16:36:16.897Z
Answers.Text: ah - if you're worried about spam - have you tried Mollom module? I'll amend my answer.
Answers.UserDisplayName: KarinG - Semper IT
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-05-13T22:05:46.627Z
Answers.Text: A lot of spam can be removed by setting a Validation rule that First name must not equal Last name ;-)
Answers.UserDisplayName: petednz - fuzion
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-05-12T15:48:47.487Z
Answers.LastActivityDate: 2016-05-13T16:39:08.530Z
Answers.LastEditDate: 2016-05-13T16:39:08.530Z
Answers.UserDisplayName: KarinG - Semper IT
Answers.Body: <p>Suggest you look at giving users only the option to create Draft webform submissions (maybe just hide 'submit' via js) - then you take over and do the actual Submission</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-05-13T22:04:23.063Z
Answers.LastActivityDate: 2016-05-13T22:04:23.063Z
Answers.UserDisplayName: petednz - fuzion
Body: <p>We've a Webform which picks and updates existing contact's data. Is it possible to add a "check data" step somehow after webform submission has been made but before actual contact record change? There seems to be no corresponded event-condition-action chain in Rules/Webform Rules/CiviRules. </p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-05-12T21:23:31.237Z
Comments.Text: here is another dart in the dark (nice phrase). look at giving users only the option to create Draft webform submissions (maybe just hide 'submit' via js) - then you take over and do the actual Submission.
Comments.UserDisplayName: petednz - fuzion
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-05-13T17:19:55.400Z
Comments.Text: Pete I was just trying to think of something similar to this and you nailed it.  You should post this as an answer.
Comments.UserDisplayName: Allen Hutchison
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-05-13T23:28:28.793Z
Comments.Text: Perhaps amend to say that this only works for authenticated users.
Comments.UserDisplayName: KarinG - Semper IT
Tags: <webform-civicrm><workflow>
Title: Premoderation for webform submission before contact record change
ThreadText: # Premoderation for webform submission before contact record change
  
  (Asked by: username_0 on 2016-05-12)
  
  We've a Webform which picks and updates existing contact's data. Is it possible to add a "check data" step somehow after webform submission has been made but before actual contact record change? There seems to be no corresponded event-condition-action chain in Rules/Webform Rules/CiviRules.
  
  **Tags:** webform-civicrm, workflow
  
  > **Comments:**
  > **username_1**: here is another dart in the dark (nice phrase). look at giving users only the option to create Draft webform submissions (maybe just hide 'submit' via js) - then you take over and do the actual Submission.  
  > **username_2**: Pete I was just trying to think of something similar to this and you nailed it.  You should post this as an answer.  
  > **username_3**: Perhaps amend to say that this only works for authenticated users.  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_1 on 2016-05-13. Score: 3 | Accepted answer
  
  Suggest you look at giving users only the option to create Draft webform submissions (maybe just hide 'submit' via js) - then you take over and do the actual Submission
  
  
  ---
  
  ### Answer by username_3 on 2016-05-12. Score: 2
  
  Webform validation module can run a number of checks on specific fields on your webform - <https://www.drupal.org/project/webform_validation>
  
  If you're worried about SPAM submissions install Mollom: <https://www.drupal.org/project/mollom> - and configure it to monitor your webform submissions.
  
  > **Comments:**
  > **username_0**: Sounds great,thank you; we are more in need of "human validation" tool though.  
  > **username_2**: As in, you're trying to make sure the webform submission was made by a human (and not a bot), or you need a human to check the data before Civi is updated?  
  > **username_3**: Hey username_0 - please be more/very specific as to what you meant when you wrote "check data" - or we're just throwing darts in the dark :-)  
  > **username_0**: @username_2 The latter I guess: default data consistency checks are fine, it's more about content check group of "moderators" performs on "decent users" submission.  
  > **username_0**: @ username_3 You're absolutely right, sorry; have just thought about this for a while, so it is clear for me only.. It's a content checks, hence, "human touch" is needed.  
  > **username_3**: ah - if you're worried about spam - have you tried Mollom module? I'll amend my answer.  
  > **username_1**: A lot of spam can be removed by setting a Validation rule that First name must not equal Last name ;-)  
  
  ---
  
  