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
• Instructions - Showing another field when someone RSVPs Yes
• Instructions - Limiting Form Submissions
• Most common mistakes when writing scripts to go into the Conditional Rule box

 

---

Requirements:

This article applies to users of the "connector crms" which are the ones listed in the title of the article.

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

1. Build a form (Prefilled or Blank) Include all the usual contact fields (Name, Company Name, etcetera)
2. Ask a question first – for example: RSVP? And create values for the responses (Accepted and Declined)
3. Add the further field 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?”)
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 “Accepted”, then ask; “Which meal choice would you like?” (that is, make the field Dietary appear)

 

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

Insert this into the "Add conditional rule" box for the Dietary field, or whichever secondary field you wish to appear, if the delegate responds with Accepted.

 

 

Important – Each field has a Field Name and a "Conditional Field Name" which you must use when referring to it in the secondary field. The Conditional Field Name is the name used in the syntax, and you will need to use this when building the conditional rule. 

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 could 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”.  

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 the true value by using Copy and Paste like this:

Finding database values of fields using Copy and 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 two pages icon, next to each field:

Important: it is the "hidden value" that the feature is copying. This is not necessarily the same as the words that the client will see.

 

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 

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

 

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 "you like to join the Wait List?" or a similar message. 

 

To limit form submissions:

1. Create the form and the RSVP field in the usual way. 
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.  Copy and paste from Word can sometimes bring across unwanted elements.)
3. You will need 5 elements:
   • Your instance number - for the CRMs listed in the title of this article, the instance number is always 0
   • The campaign ID 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
4. Copy the line below onto your Notepad and replace all five elements in bold 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: (This line is an example only - replace each element in bold with your own values):
   { Count : 'all', Instance : '0', 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 below onto your Notepad and replace all the elements in bold with your own values as you find them. Notice that this code switches the <30 to be >=30
   { Count : 'all', Instance : '0', 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

    

Q. What do these two lines of code mean in English?

A. 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 : '0', ListId : 'F-a0V41000006pEueEAE', Field: 'SF_RSVP__c', Value : 'Accepted' } <30

Then:

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 or Wait List message conditional rule field.

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

 

To find the five elements for a Count command

1. Instance number:

Your Instance is the ID of your database, which is held in Vuture.  For the CRMs listed in the title of this article it is always 0 and will not change (unless you change CRMs).

 

 

2. List ID 

To find the List ID from your Vuture instance, in your campaign, go to the Send email screen, select

1. your CRM as your External System, and select

2. the list you are planning to send to. 

You do not need to complete any other fields.  You are not sending anything at this point, only establishing the List ID.

Click on Check List, highlighted in red above.  

A new screen will open, listing the names on your mailing list and showing their engagement.  You need to take note of the URL along the top of the screen.  It will look something like this:

https://xxx.vuture.net/mvc/admin/emailengagementchecklist?strListSource=Prod%20Upper%20Sigma&externalSystemId=11&status=0&emailListId=4533&intSitePageId=113983&isConnector=true

Find the ListId by scrolling along the URL until you get to the ListId= section.  In the example above it is 4533.  Make a note of your number.

You can now close the checklist window, return to the Send Email screen and select Cancel in the top right of the window.  You will not be sending anything at this point.

 

3. 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.

 

 

4. 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 for the clients to see, 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 easy for you to find the value, so we have added a Copy Paste option to the fields on the form.  

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 page icon, next to each field:

Click to copy the hidden value, and then paste into your Notepad.

 

5. 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.

 

Once you have assembled the five elements you need, replace the items in the line of sample code with your own values in Notepad and then copy each line into the correct Conditional Rule boxes in your forms, as instructed above. 

 

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 "!"#$%&'()*+,-./:;<=>?@[\]^_`{|}~"