Overview

Form Logic allows you to build Vuture forms that react to your contacts’ responses, hiding or displaying later questions depending on their response to earlier questions.

You do this by adding a Condition to the next field you want your contacts to see. The Condition ensures that they will only see that field if they respond in a specified way to the previous question.

For example, when a contact responds RSVP yes, they can see further questions, or when an event capacity is reached, the next view can be “Sorry the event is full”, or if a person has dietary requirements they will see the list of options.

 

---

Contents

• Requirements
• Instructions - Showing another field when someone RSVPs Yes
• Instructions - Limiting Form Submissions with Salesforce
• Most common mistakes when writing scripts to go into the Conditional Rule box

 

---

 

Requirements:

You will need to have Forms v2 enabled in your system (your account manager can do this at "Admin.System.Versions.FormEditorVersion2") and enabled for your Vuture role, as well as having "Admin.System.Forms.Force validation script" enabled to see the extra boxes in the Form Editor.  Please contact your account manager if you're unsure about your current settings.

Your browser can be Chrome, Firefox or IE.  If you use Internet Explorer, please ensure that it is version 9.0 or higher.

---

Instructions - Showing another field when someone RSVPs Yes

Step by Step – Part 1:  Simple RSVP question and follow up answer

Please watch this video for a full overview of how this works with OnePlace:

WARNING - When you are building forms using form logic, you will decide to display fields, or not, depending on the previous answer from the contact.  You need to understand that, if you are working with a field that already has a value, and you choose not to display it, any value held in that field in OP could be deleted on Form Submit.

For example: a contact already has Monday as a session choice in an additional field in OP.  On a subsequent form for the same event, the contact RSVPs "No" to this event.  Therefore, by the logic established on the form, they will not see the session choices, even though Monday was prechecked.  When the contact submits the form, the session choice in this related field on OP will be deleted.

This behaviour only applies to fields which are brought forward onto a form from OP and then subjected to form logic.  All other OP fields are not affected, including the ability to "hide" fields on forms.

 

Start in the usual way with the first question:

1. Build a form (Prefilled or Blank)
2. Ask a question first – for example: RSVP? And create values for the responses (Yes and No)
3. Add the further fields you want to appear, depending on the answer to your first question. (In this example; if they RSVP Yes, then follow up with “Which session would you like to attend?”)
4. Add the conditional rule for when this secondary, or follow up, field should appear. In English: “If the answer to the question; “RSVP” is “Yes”, then ask; “Which Workshop would you like to attend?” (that is, make the field Workshop_Options appear)

The conditional rule for this would therefore be:    VxForm_SF_RSVP__c == 'Accepted'

Insert this into the "Add conditional rule" box for the Workshop_Options field.

 

 

Important – The Conditional Field Name is used in the syntax so you will need to use the correct field name for the conditional rule.  Each field has a "Conditional Field Name" you must use when referring to it in the secondary field.

 

You can see from the image above that the Conditional Field Name for the RSVP field in this example form is VxForm_SF_RSVP_c and the Conditional Field Name for the Workshop Options field in this example is VxForm_OP_Workshop_Options.  The field names in your forms may vary.  Click on each field to see the Conditional Field Name in each case.

 

Finding the Field Value

The conditional rule must use the database value for the field, not what you write into the label for clients to see.  For example, the question RSVP can have possible response values of Yes and No or Accept and Decline or Accepted and Declined, or even “Yes thanks, I’ll be there” and No thanks, not this time.  

For Salesforce and OnePlace the value for RSVP = Yes is actually "Accepted".   When writing your conditional rule in OnePlace you must use the word ‘Accepted’ in single, straight quote marks.  Do not use the label or value that your clients may see on the form.

Note - The Conditional field is case sensitive.  

Here is a list of commonly used terms:                              

 

Operator	Meaning
==	Equal to
!=	Not equal to
<	Less than
<=	Less than or equal to
>	Greater than
>=	Greater or equal to

 

 

Another Example

Here is an example form in different languages:

 

The field where you ask the contact "In which language would you prefer to answer?" is called Language in the Field Name (for this example).  Each language option field would therefore have a conditional rule on it like this:  

 

Each option changes the language, from English to Spanish and to German.  Your field names would be specific to your system.

---

Instructions - Limiting Form Submissions with OnePlace

Step by Step - Part 2 - controlling responses for your event.

Please watch this video for a full overview of how this works with OnePlace:

 

To control the responses for your event by limiting form submissions, you will need to use the Count variable.  You will count the Yes responses until they reach the capacity of your event.  You will then switch out the RSVP question and replace it with “Sorry this event is full” or a similar message. 

 

To limit form submissions:

1. Create the RSVP field in the usual way, and the field you are using as an alternative (e.g. a Wait List field or at text field for 'Sorry this event is now full').  
2. Open Notepad.  You will find it very helpful to build your whole line of code in Notepad first because it is quite long, and you can’t see the entire line in the Conditional Rule box.  Build the line in Notepad and then copy it into the Conditional Rule box. 
   Do not use Word.  There is a danger with Word that unwanted elements may be copied into your Rule when you copy and paste from Word.
3. You will need 5 elements:
   • Your instance number
   • The OnePlace list ID
   • The Conditional Field Name
   • The Response/Field Value
   • The number of places at your event.
4. Copy the line below onto your Notepad and replace all the elements in red with your own values as you find them. Instructions for how to find each element is further down in this article. You will need this line for the conditional rule for the RSVP question.
   { Count : 'all', Instance : '4', ListId : 'F-a0V41000006pEueEAE', Field: 'SF_RSVP__c', Value : 'Accepted' } < 30
   
   To make it easier for you to copy, you could copy the text in the below code block.
   

   { Count : 'all', Instance : '4', ListId : 'F-a0V41000006pEueEAE', Field: 'SF_RSVP__c', Value : 'Accepted' } < 30

    

5. Copy this second line of code and replace all the elements in red with your own values as you find them. Notice that this second line of code switches the <30 to be >=30
   { Count : 'all', Instance : '4', ListId : 'F-a0V41000006pEueEAE', Field: 'SF_RSVP__c', Value : 'Accepted' } >= 30
   
   To make it easier for you to copy, you could copy the text in the below code block.
   

   { Count : 'all', Instance : '4', ListId : 'F-a0V41000006pEueEAE', Field: 'SF_RSVP__c', Value : 'Accepted' } >= 30

 

What do these two lines of code mean in English?

For an event limited to 30 attendees:

Count the RSVP acceptances and keep the RSVP question visible as long as the number of accepts is less than 30. (<30).  

You will put this count Command into the RSVP conditional rule field.

{ Count : 'all', Instance : '4', ListId : 'F-a0V41000006pEueEAE', Field: 'SF_RSVP__c', Value : 'Accepted' } < 30

Count the RSVP acceptances and make the Sorry message appear once the number of Accepts is equal to or greater than 30.(>=30) 

You will put this Count command into the Sorry message conditional rule field.

{ Count : 'all', Instance : '4', ListId : 'F-a0V41000006pEueEAE', Field: 'SF_RSVP__c', Value : 'Accepted' } >= 30

 

To find the five elements for a Count command

1.  Instance number

Your Instance number is the number of your OnePlace database, which is held in Vuture.  It is typically a single number between 1 and 15 (held in Admin.External Systems) and your Client Success Manager or a Support team member can tell you what it is.  It will not change, unless you swap one crm for another, so you should only need to obtain the number once.

 

In the above example, the ID number you would need is 13.

 

2.  List ID

For detailed instructions on finding the List ID, please click here.

To find the List ID from your Vuture instance, go to the Send email screen, select your OnePlace instance as your list source, hover over the list picker, right click on your mouse and click "inspect".

 

Once the inspect window is open, expand the list section (by clicking on a downward facing arrow head) and then either the Function or Publication section.  You will find the List Id next to each List name.

 

 

3.  The Field Name

Each field has a conditional field name which is displayed in the Conditional Field Name box when you click on that field.  

 

4.  The Response Value

Update:  You can use Inspect to find the response value, but we now offer an alternative which should be easier.  There is an option to Copy and Paste the value of fields into the Conditional Rule statement.

When you use the Copy option, Vuture will find and copy the hidden Value of the field to the clipboard. From there, you can paste it into your Conditional Rule.  The Copy option is under the little i in a circle, next to each field:

Note that the copy option will copy the actual, hidden, value of the field - which is not necessarily the text that the users of the form will see.

Alternatively - to find the value using Inspect:

In the form, first select the correct question and then right click your mouse.  The last option in the drop-down menu is Inspect.  Click on Inspect.  Find the value for Yes or Accepted in the same way as in point 2. above.  Note:  For OnePlace RSVPs only, the yes value is always Accepted, but you can use Inspect to find the values for other fields.

 

5.  Places available at your event

This will depend on you.  For testing, we recommend you start by setting this number to 1 initially.  This will allow you to complete the form “as a client” and see the options changing on the form for subsequent “clients”.  You will need to email a test send to yourself to see this working.  Just using View Page will not work.

 

---

Common mistakes when writing condition scripts

If your conditions are not being met in the form (for example, the secondary field is not hidden when it should be), you could have made one of the following common mistakes:

• Case Sensitivity:  Variables and function names are case sensitive.  Please make sure you have added the correct name and/or field IDs and used the correct upper or lower case
• Mismatching quotes, parenthesis and curly brackets:  Make sure any statement which opens with a parenthesis, ends with a closing parenthesis
• Use the correct assignment operator.  For example: '= >' is not the same as '> ='   The first of these two examples is incorrect and will break the condition and consequently the form.  See the table of commonly used terms above for guidance
• Extra commas, semicolons or other punctuation characters:  Every character has an interpretation in JavaScript; any unnecessary additions will modify your condition
• Do not use inverted commas ( ’ ).  Use single quotation marks ( ' ) in your condition.  Make sure the mark is straight and isn't tilted or curvy in any way.
• Do not use special characters in crm field names. Special characters are  "!"#$%&'()*+,-./:;<=>?@[\]^_`{|}~"

There is a Word version of this article available for you to download (below) if you would find that useful.