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 second question 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 can see the list of meal options.
Contents
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 Client Success 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 Salesforce:
Start in the usual way with the first question:
- Build a form (Prefilled or Blank)
- Ask a question first – for example: RSVP? And create values for the responses (Yes and No)
- Add the further fields you want to appear, depending on the answer to your first question. (In this example; If they RSVP Yes, then you could follow up with “Which meal choice would you like?”)
- 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 meal choice would you like?” (that is, make the field Dietary appear)
The conditional rule for this would therefore be: VxForm_SF_RSVP__c == 'Accepted'
Insert this into the "Add conditional rule" box for the Dietary field.

Important – The Conditional Field Name is used in the syntax, and you will need to use this when building 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.
The Conditional Field Name for the Dietary field in this example is VxForm_SF_Dietary__c.
The field names in your forms may vary. Click on each field to see its 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 response values that the clients will see 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, the database value for RSVP = Yes is typically "Accepted". When writing your conditional rule you must find the correct term and use it in single, straight quote marks. Do not use the label or a value that your clients may see on the form.
While the database value is typically Accepted, you can check to see the true value in a couple of different ways. You could use Inspect, or we have now added an easier method, Copy and Paste.
Finding database values of fields using Copy and Paste:
We wanted to make it easier to find the database values of fields, so we added the option to Copy and Paste the value of fields into your Conditional Rule statements.
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 two pages icon, next to each field:

Please note, it is the "hidden value" that the feature is copying. This is not necessarily the same as the words that the client will see.
Alternative Method - Finding database values of fields using Inspect:
In the form, click on the RSVP field to highlight it. Right mouse click. The resulting menu has the final item of Inspect.

Choose Inspect. The resulting page will look like this:

You can see the value= line has the value of Accepted. Use the little x at the top right to close this part of the page.
You can now write the conditional form logic line as:
VxForm_SF_RSVP__c == 'Accepted'
Note - The Conditional field is case sensitive so please ensure you are matching upper and lower case exactly.
Here is a list of commonly used terms when writing conditional rules:
|
Operator
|
Meaning
|
|
==
|
Equal to
|
|
!=
|
Not equal to
|
|
<
|
Less than
|
|
<=
|
Less than or equal to
|
|
>
|
Greater than
|
|
>=
|
Greater or equal to
|
Instructions - Limiting Form Submissions with Salesforce
Step by Step – Part 2 – controlling responses for your event.
Please watch this video for a full overview of how this works with Salesforce:
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:
- Create the RSVP field in the usual way.
- 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. (Don't use Word. Copy and paste from Word can sometimes bring across unwanted elements.)
- You will need 5 elements:
- Your instance number
- The Salesforce campaign or “list ID”
- The Field Name (not the Conditional Field Name this time)
- The Value (example Yes or Accepted)
- The number of places at your event
- 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 first.
{ 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
- Copy this second line below onto your Notepad and replace all the elements in red with your own values as you find them. Notice that this 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:
1. 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
2. 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
Instance number:
Your Instance number is the ID number of your Salesforce database, which is held in Vuture. It is typically a single number between 1 and 10 although it could be higher (it is held in Admin.External Systems) and your Client Success Manager or a Support team member can tell you what it is. It will never change, (unless you swap one CRM for another), so you should only need to obtain the number once.

In this example, your instance number would be 4.
List ID – Salesforce Campaign ID
To find the List ID or Salesforce Campaign ID from your Vuture instance, go to the Send email screen, select your Salesforce 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). You will find the List value above the name of the campaign.
For more instructions on how to find the List ID for Salesforce, please click here.
The Field Name
Each field has a field name which is displayed in the Field Name box when you click on that field. Note: a Count is not a Condition. For a simple Count such as we are building here, you are counting the field submissions. There is no condition, so you should use the Field Name not the Conditional Field Name this time.

The Response Value
The response value is the hidden value of the field, which is not necessarily the value that is displayed in the label on the form for clients to see. For example, the RSVP Yes value could say "Yes I will attend" on the form, but the underlying value of the field is actually Accepted. You need that hidden value in your line of code. We wanted to make it easier for you to find the value, so we have added a Copy Paste option to the fields on the form. Alternatively you could still use the Inspect method if you prefer.
Finding Field Values using Copy Paste
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:

Finding Field Values 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 Accepted in the same way as described above, further up in this article. For standard Salesforce RSVPs, the yes value is typically Accepted. You can also use Inspect to find the values for other fields.
Places available at your event
This will depend on you. For testing, we recommend you start by setting this number as 1 initially. This will allow you to complete the form “as a client” and see the options changing on the form.
Testing
We encourage you to test this process using 1 or 2 places available at your event initially, then resetting this number to the event capacity. Bear in mind that, if you have been testing with your internal team, maybe 5 people have accepted internally, you should add those 5 to your total event capacity to allow the full number of clients to accept.
Common mistakes when writing scripts to go into the Conditional Rule box
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 "!"#$%&'()*+,-./:;<=>?@[\]^_`{|}~"