Principle

In the context of a collection campaign, the identity of the person returning a response has no impact on the campaign’s operation. In effect, for GTServer, the collection is not carried out at the level of the surveyed individuals levelbut at the level of the entities. Thus, when the campaign is launched, each form issued contains the information of the entity to which it is attached. The form can thus be transferred to any individual, and when the data is transmitted, it will be associated with the entity specified in the form.

Implementation

Template configuration

 

 

 

 

Suppose address validation is selected in the form template. In that case, the user must validate his email address before sending his response, even if the form is configured to send the response in HTTP. This address will then be used by GtServer as a respondent for the entity.

 

 

 

 

 

Validation of the email address by the respondents

For respondents, validation can be done in two ways:

• When setting up the email connection. When the user clicks on the “Send validation email” button, GTAnswer sends an email to the specified address.
• When attempting to transmit data for a form whose template requires validation of the email address.

Note 1: The method of transmission of the validation email may differ depending on the validation method.

• If the validation is carried out during the email connection setup, the message is sent by email.
• If the validation is carried out during a data transmission attempt and the campaign launch action that diffused the form has at least one of the HTTP publication options activated, a request to send the email is made to GTServer in http; then the email is sent by GTServer. GTAnswer, in this case, does not need to have any operational configuration to connect to the mail.

In any case, the user receives an email with a “.checkmail” attachment. By opening this attachment via double-clicking, the address is validated, resulting in a green “bullet” at the bottom left corner of GTAnswer, next to which is the validated email address:

Impact on campaign messages

By convention, we will adopt the following vocabulary:

• The correspondent: this is the address to which the questionnaire was sent. If the address has been redirected, it is the redirected address.
• The respondent: this is the address that Answer has validated. This address is only available if address validation has been activated in the template.
• The correspondents: all correspondents for an entity (including additional validation axes).
• The Respondents: all respondents for an entity (including additional validation axes)

The CC and BCC fields of the messages can be filled in automatically by correspondents, respondents, or both. In addition, it is now possible to choose the recipient: respondent or correspondent or both. These changes introduce a new sending logic, especially for reply notification messages sent by GTServer.

GTServer messages: first response, subsequent responses, rejected response

Each new response triggers the sending of an email. The recipients are selected as follows:

The To field can have one of the following values:

• to the correspondent
• to the respondent otherwise to the correspondent (i.e., if address validation is not used)
• to both

The CC and BCC fields can be set to one of the following values:

• to correspondents
• to respondents otherwise to correspondents
• to both

Notes:

• For the closed questionnaire message, the CC and BCC fields are not accessible.
• Additional CC, BCC can always be set via the input box on the right.

The default values for new messages or those updated from version 3.0 are :

• First, next :
  • To = to the correspondent
  • CC = Ø
  • BCC = to correspondent
• Rejected :
  • To = to correspondent
  • CC = Ø
  • BCC = Ø

Action messages: campaign relaunch and closure

Options for the To field :

• to each correspondent
• to each respondent otherwise to each correspondent
• To both
• Specific address

Sending to a “Specific address” available for a reminder message allows you to specify an email address directly or through a variable (e.g. [[RootAxis1]]), which will be replaced by the value of this field for each entity being relaunched.

Possible choices for ‘CC and BCC :

• to correspondents
• to respondents otherwise to correspondents
• to both

The default values for new messages are : To = to each correspondent CC = Ø BCC = Ø

Impact of validation on the behaviour of the form

The validated email address can be used in the form via the GTVALIDMAILADDRESS() function. It is thus possible to modify the behaviour of the form according to the identity of the respondent.

Note: the behaviour of the function varies according to the context. It returns :

• In GTAnswer: the address if it is validated, an empty string otherwise
• In Design: #N/A
• For the questionnaire preview (GTClient, GTWeb), this function returns #REF!

Was this article helpful?

0 out Of 5 Stars

5 Stars		0%
4 Stars		0%
3 Stars		0%
2 Stars		0%
1 Stars		0%

5 Submit

How can we improve this article?

How Can We Improve This Article?

Name

Email

Submit