Creative CiviCRM Workflow Solution to Get Around Webform Bug?

[PrincessAng417]

I have several large Webforms that we intend to use for our application process.  The Civi-Webform integration works beautifully.

As I said, though, these Webforms are very large, and there are a lot of conditional statements driving the logic which shows an applicant (who is a registered user, invited to fill out the form) the appropriate questions.

We ran into this known issue (https://www.drupal.org/node/2088249), which is limiting how many conditions we can load into each of our forms.   

Now we are trying to figure out a work-around.  Any ideas how to leverage Civi to make something work? 

We are thinking we will need to split each application in half or so-- there are some logical breakpoints that would work.  But with two Webforms that update Custom Data on the same Case... how can I make this a seamless experience for our applicant user?  I don't want to have to send two separate hash links for them to fill out... I would imagine we would end up with people who have filled out one, but not the other.  Is there a way to chain the two Webforms together that would be seamless to the user?

Anybody have a creative idea to help make this work?

[petednz]

we have used a checksum so that the user gets moved on from one webform direct to anothr - can't put my finger on it right now but don't recall anything tricky other than getting the right user id token in to the 'custom url' option for where they get moved to after submission.

in the civi tab on webform, there is a vertical tab that will give you the checksum link for form 2 that you can then use in form 1 - (talking from memory but it might be enough to nudge you down the right route)

[Coleman Watts]

It looks like there are multiple patches and solutions proposed in that issue thread, have you tried any of them?

[PrincessAng417]

Thank you so much for the responses.

Coleman: No, we did not apply any of the patches in the Drupal thread because we were topping out at significantly more conditional statements than the other posters topped out at.  Because they acknowledged it didn't fully fix the problem, and that there is something still amiss, we haven't yet gone that route.

Pete: Did you use the checksum to show a Profile, or a Webform?  I'm confused, but feel like you're onto something that may solve this issue for us.

[petednz]

it pushed people through to another webform - not a profile

[Coleman Watts]

To further Pete's point: any webform can be set to redirect the user wherever you want upon submission. So it's simple enough to redirect to a second webform. If the user is logged in then you already know who the contact is so you've got no problem - just set the redirect and you're done.

If the user is anonymous then you need some way for the 2nd webform to know the contact ID from the first webform - and that's where checksums come into play - on the first webform use the hidden cid and checksum fields which will provide you with the tokens you need to add to the redirect url which will identify the contact for the sake of the 2nd webform (you can get the precise format for this link by clicking "edit" on the webform tab on the checksum field once you have added it to your form).

I'd also recommend an additional convenience for your users - in addition to redirecting them after the 1st webform you can also send them an email containing the checksum link to the 2nd form - this would allow them to pick up where they left off at a later time rather than having to do both forms in one sitting.

[PrincessAng417]

This is really excellent advice-- thank you so much!

[Coleman Watts]

You're welcome, you'll find more documentation on the wiki.
Let me know how it goes!

[JohnFF]

Bear in mind: the unsupervised dedupe rule means that if someone enters their name & email address that the form may prepopulate with their previous values - a definite security risk.

To circumvent this: set your unsupervised dedupe rule to be the contact id only.

[Coleman Watts]

(or a less drastic solution, ensure the second webform is not set to display any sensitive data)

[JohnFF]

Won't it prepopulate it automatically? Is there any easy way to prevent this?