It is possible customize your survey logic outside of the out of the box functionality. Advanced logic allows you to control:&nbsp;&nbsp;

This logic uses a mix of java script and server side values on the client side. Details follow in this walk through.

Surveys have a list of pre-defined survey fields. Values can be passed into the survey for tracking purposes (or to be re-display within the survey). To achieve this, append the values to the survey deployment URL. 

These fields can be passed into a survey. They will be saved with the survey response.  To pass the value, append the query string to to the survey deployment URL. 

Server side merge tags allow the placement of captured content onto a survey page. For example, to place email address on a survey page use the tag [%$email%].  The following notation identifiers a server side script tag [% %]. 

]    Survey expiry date long Saturday, 09 October 2021

[%$EndDateShort%]   Survey expiry date short 10/9/2021 11:59:00 PM

These are displayed using the following server side tag. This is would be added to the finish page and when the finish page is loaded the targeting offer logic is evaluated and the matching offers are displayed.

Embed email chart on a survey page. in order to do this the survey results need to be made public. The chart display options are as follows.

With Advanced Page Logic, scripting code can influence the navigation of the survey. It can also influence the validation.

With Advanced logic, the survey can make advanced decisions. For example, brancing based on answers to question taken on previous survey pages. This is not possible through standard page branching.

Implement this at the survey page level. There are two scripts which run:

- Page Load Script: This script runs when the page has finished loading. It can hide and show lines on the survey page.

- Page Submit Script: This script runs before the page is submitted. Use it to implement extra validation and set the next page of the survey.&nbsp;&nbsp;

This script runs as the survey page runs.

This is useful when you want to hide and show lines on the survey page based on a previous answer on another page.

In the example below the script shows how to hide lines based on the answer to a question. 

In this case Q2.0 means question 2 answer 0 has been selected. If this is the case, survey lines 1, 2 and 3 are hidden.

Note: only the highlighted items are user defined. The other script code is required as shown and is case sensitive. See appendix 1 for more samples.&nbsp;&nbsp;

This script run as the survey page is submitted after all the standard validation has run.

This is useful to do extra validation or change the next page of the survey based on the answer to a question.

In this example, if question 2 answer 1 has been selected, then the next page will be set to P4 which is page number 4.

Note only the highlighted items are user defined. The other script code is required as shown and is case sensitive.&nbsp; &nbsp;

This section explains
how to reference survey elements:

Questions are most common elements on a survey used for reference. The answer to a question is reference as follows [Q8.1.1]. All survey question elements are surrounded by []. The notation is as follows:

The value returned is either true or false depending on whether the the item is selected. 

 Survey pages are referenced in a similar way. For example [P4] returns the page id for survey page sequence 4. Use this to build custom flow and set the next or finish page ID as the survey runs. 

Survey.showSurveyLines({List of line numbers})&nbsp;&nbsp;

Shows survey lines on a survey page. Takes
one parameter which is a list of lines to show like this ‘1,2,3,4’. This
example shows how to show lines 1,2,3,4 e.g.&nbsp;


Survey.hideSurveyLines({List of line numbers})&nbsp; &nbsp;

Hides survey lines on a survey page. Takes
one parameter which is a list of lines to hide like this ‘1,2,3,4’. This
example shows how to hide lines 1,2,3,4.&nbsp;

Survey.setNextPage([P{Page seq}])&nbsp; &nbsp;

Sets next page takes page ID as a
parameter example [P4] page sequence 4.&nbsp;

Survey.getQueryStringValue('{Name}')

Survey.fieldValue('{Field name}')&nbsp; &nbsp;

Survey.hideAnswerLines('[ARow{Question seq.Answer seq}]')

Hides line of an answer. Hides answer sequence 0 and sequence 1.

Survey.showAnswerLines('[ARow{Question seq.Answer seq}]')

Shows line(s) of an answer. Hides answer sequence 0 and sequence 1.

Question.showColumn({Question seq},{Column seq})

	The first parameter is the question sequence and the second parameter is the column. Columns start with sequence 0

Question.hideColumn({Question seq},{Column seq})

	The first parameter is the question sequence and the second parameter is the column. Columns start with sequence 0.

Survey.setLanguageCode('{Lancode}',{Reload})

Set language code and trigger a page reload.

Survey.setPhantomAnswer([SelectAnswer{Question Seq.AnswerSeq}])

 Set the answer to a question which is not in the survey flow. Only applies to radio and checkbox questions. The sample code select Answer 0 for question 2. NB: Only questions on survey pages will show in results. If this question is used to create summary totals, you will need to create a dummy page. This is a page which is not in the survey flow. You must add this question to it in order for it to display in results.

Survey.removePhantomAnswer([SelectAnswer{Question Seq.AnswerSeq}])

Deselect answer.  Only applies to radio and checkbox questions. The sample code deselects Answer 0 for question 2. NB: Only questions on survey pages will show in results. If this question is used to create summary totals you will need to create a dummy page. This page is not in the survey flow. You must add this question to it in order for it to display in results 

Survey.setPipeText('{Placeholder}','{Value}')

Used to set the piped text for a place holder through code. It takes two parameters. The first parameter is the pipe text placeholder. The second parameter is the value which the place holder will become. In the example below the place holder {creditcard} will be replaced with Visa.

Note: you need to create the pipe text control question as normal.&nbsp; . 

Used to set the finish page id. Use the notation is P + the page sequence number. The example below sets the finish page to finish page with sequence 5

Used to set the next page id. Use the notation is P + the page sequence number. The example below sets the next page to next page with sequence 2.

Survey.setFinishURL('{URL}')&nbsp; &nbsp;

Sets finish page takes URL as a parameter example http://myUrl.com&nbsp;

These client side functions allow for custom validation and custom error messages.

PageError.add('{Fieldname}', '{Error message}');

Add an error to a form input field.&nbsp; In the example below there is a form field ext_User1 on the survey page. See examples below:

PageError.addQuestionError('IdQ[{Question seq}]', '{Error message}')&nbsp;&nbsp;

Add an error for a survey question. The question which is in error is referenced using the code [IdQ{Question sequence}].&nbsp;&nbsp;

PageError.removeErrorItem(IdQ[{Question seq}]')&nbsp;&nbsp;&nbsp;

Remove error item.&nbsp;The question which is in error is referenced using the code [IdQ{Question sequence}].

PageError.errorToast('{Message}')&nbsp;&nbsp;&nbsp;

Access to the state of survey response. This gives access to values which would have been on previous survey pages.&nbsp;

SurveyState.getValue('{Fieldname}');

Get the value of any form field used on the survey after you have proceeded past the page in the survey.

SurveyState.saveValue('{Fieldname}','{Value}');

Add any value to the survey state object this value can be used or any
subsequent page in the survey. It will also be saved in the survey results.

SurveyState.getQueryStringValue('{Name}');

All query string values are saved to survey state and can be retrieved using&nbsp;&nbsp;

Sensorpro supports the addition for form elements to any survey. Pre-defined fields which can be used for convivence are shown. It is recommended you use these fields where possible. They are integrated into the platform and can be used in result sets, API calls, filters and are directly part of the survey response.&nbsp;

You can use a form field with any name and it will be saved as a named pair with the survey response.&nbsp;

When adding a custom form field&nbsp; the default HTML format we would recommend is shown below, it will be automatically formatted when rendered.&nbsp;

You can of course handcraft your own html and style as you require but input fields should have the following attributes:

When you view the responses for this survey you will see a section at the endo of the instance report with the heading custom fields the values will be listed here. These fields will be tagged onto the end of&nbsp; csv &amp; excel exports.

If you want to add a custom date field prefix the field name and ID with the date format:

To write custom validation see the section "Client side functions page errors"