Page tree
Skip to end of metadata
Go to start of metadata
Plugins listed in this category allow to perform Workflow operations like passing data between Forms/Surveys, sending data to a third party system, etc.

Copy Responses

 Click here for more details:

The Copy Responses plugin copies the responses provided for original form/survey and passes them to the indicated fields in another form/survey. It allows to set up an advanced workflow with options for synchronized responses updating and deletion in connected surveys.

Set up the following parameters to apply the plugin:

  • *Logical Condition - Specify the logical condition, based on which the plugin should be triggered. If this field is empty, the plugin would be executed on every submit. You can use Qx.Ay.Cz references in here, ANDORNOT operators and regular expressions.
  • * Target Form or Survey Id - Enter the unique ID of the survey or form the data should be copied into.
  • *Merge responses - This dropdown has three options: Do not merge, Respondent ID and External ID. Select "Do not merge" if you want the plugin to create a new response in the target form each time a response in the original form is submitted or resubmitted. If Respondent ID is selected, copied responses in the target form or survey will be updated automatically when respondents come back to edit and resubmit their original responses. Choose External ID if you would like to merge responses with the same External ID from multiple source forms into one response of the target form.
  • *Respondent ID or External ID - If you choose to merge responses by Respondent ID, reference a question in the original form or survey where the parameter Respondent ID will be recorded by the system. If you would like to merge responses by the External ID, reference a question with the unique custom value which the system will use as an External ID. Use Qx.Ay format or Question/Answer identifiers to specify the question reference.

  • We highly recommend hiding a question where the Respondent ID is stored to prevent the ID value editing by respondent.
  • If the Copy Respondent ID parameter is not specified, and the original response is edited and resubmitted in RBR mode, the plugin will fire and create a new response in the Target form each time response is resubmitted.
  • If the Copy responses plugin is applied to a form/survey along with the Respondent ID Saver plugin, the Respondent ID Field and Copy Respondent Id parameters must reference different questions in order for these plugins to work properly.
  • Overwrite with empty values - This option allows the system to overwrite existing values in target responses with empty values.
    "Yes" means the plugin will overwrite target fields with new empty response values.
    "No" means the plugin will skip empty form fields, and data that was recorded previously for those fields will be preserved.
  • Auto-Map Questions - This option works only if identical question identifiers are set for questions in both source and target forms. Select 'Yes' if you would like to map questions with the same question identifiers in both source and target forms automatically. If 'No' is selected, the system will process mappings defined in Question references section.
  • Question References - Enter paired references in Qx=Qy format to specify questions to pass the data from and to. For instance, Q1=Q5 means that response from question 1 of the original survey will be placed into the question 5 of the destination survey. The source and target forms questions must have the same type and structure.
  • The references specified in Questions References section will overwrite questions mapping generated automatically.
  • The options Merge responses and Overwrite with empty values were added to this plugin on February, 5th, 2019. They will be present in all Copy Response plugins configured after this date.

Copying responses across different accounts

If you would like to copy responses across different accounts (meaning source and target forms/surveys are located in different accounts), please additionally set up the following:

  1. Create as much AllowCopyFrom metadata as necessary in the account where the target form/survey is located. For instance, if it is necessary to copy responses from 3 sources, you should add three AllowCopyFrom metadata in the target account:
  2. Go to the target form/survey settings, set metadata and specify IDs of forms/surveys-sources in the following format: AllowCopyFrom=SID
  3. In the forms/surveys-source set up the "Copy Responses" plugin and in the second parameter specify the unique ID of a target form/survey.
  • Parameters marked with * are required.
  • Autocomplete function allows you faster and easier insert questions references. After entering Q or Qx.A system will show you the list of available questions or answer options. Picked element will be substituted by its sequence number within the survey.
  • Question references can be edited in Quick Edit box.
  • It is possible to pass files uploaded by respondents from one form to another. To do this, simply reference to a "File upload" question type and the file uploaded in original survey will be available for downloading in destination survey.

Please note that this plugin also works with the Question and Answer Identifiers, so you can use them instead of question and answer numbers in the plugin parameters.

Expired Link Blocker

 Click here for more details:

This plugin allows setting an expiration date for unique links or passwords in forms and surveys that were distributed via Email or Password Protection methods. After the unique links or passwords expire, respondents can either be redirected to a certain website or see an info message.

To apply this plugin specify the following parameters:

  1. *Days to Live - Specify the number of days the unique links and passwords should be active.
  2. Redirect URL - Indicate the URL to which respondents will be redirected after the link or password expires.
  3. Info Message - Indicate the message that respondents will see after the link or password expires.

 

You have to specify either Redirect URL or Info Message parameter; only one of these fields is mandatory. If you specify both parameters, a respondent will see the Info message when the unique link or password expires.

Logical Remote Data Sender

 Click here for more details:

"Logical remote data sender" plugin is used to send data from the survey that is submitted by respondents to a third party application via HTTP request and only if the indicated condition is met.

  1. *Remote URL - Indicate URL to access a third party and send the data to. Here you can add {RespondentID} and {FormID} formats to get respondent ID and form ID respectively.

    Example

    The remote URL https://192.168.1.1/remote.php?respondent={RespondentID}&formID={FormID} would return respondent = 123456789 surveyID = 123456 on a server.
  2. *HTTP/HTTPS Request Method - Select the request method you want to use when sending data.
    POST - is recommended for using if the URL of the third party application is very long or contains non-ASCII characters.
    GET - this method is recommended if the target application is idempotent.
  3. Submit Value - Provide parameter for the submit event.
  4. *Send When Next or Submit - If your survey has more that one page you can enable data sending when respondents click Submit only or when they navigating between survey pages(e.g. they click Next).
  5. *Logical Expression to Enable Sending - Specify the logical expression upon which the request should be sent. If the request should be sent always, please use Remote Data Sender plugin. 
  6. *Form Elements Names and Values - Input parameter names and values using the Param_Name=Param_value format. For example FF_01=Q1.A1, where FF_01 is the arbitrary name of the parameter you are sending data to, Q1.A1 is the parameter value.

    If you need to send the links to the files which were added via File Upload questions, you may use the following tags: LINK:Qx.Ay for downloadable links, PLINK:Qx.Ay for preview links. The PLINK reference will show a preview of an image, or an icon for other files. 
    When an image is accessed by a direct link, a browser will show a download dialog. To view the images right away, place a link to the image inside the <img src='downloadable link'/> HTML tag.

Errors processing 

if there are multiple plugins set up in a form/survey, the requests generated by the plugins will be sent via separate queues. These queues are unique per User Identifier and remote URL.

Depending on the received errors codes, messages sending will be retried according to the following rules:

  • Code 500. Module retries to send a request after 1,5,25 min, then every 30 min for 3 hours, and then sends it to the error queue.
  • Codes 408,502,503,504. Module retries to send a request after 1, 5, 25 min, then every 30 min for 24 hours, and then sends it to the error queue.
  • Module retries to send exceptions without code(timeouts, etc.) after 1, 5, 25 min, then every 30 min for 24 hours.
  • Other(404,401) codes are logged as errors and module does not try to send a request again.

For more information, please refer to the following table:

HTTP Code(s)

1st Interval

2nd Interval

3rd Interval

4th Interval

4th Interval Duration

500 (Internal Server Error)

1 minute

5 minutes

25 minutes

30 minutes

3 hours

408 (Request Timeout)

1 minute

5 minutes

25 minutes

30 minutes

24 hours

502 (Bad Gateway)

1 minute

5 minutes

25 minutes

30 minutes

24 hours

503 (Service Unavailable)

1 minute

5 minutes

25 minutes

30 minutes

24 hours

504 (Gateway Timeout)

1 minute

5 minutes

25 minutes

30 minutes

24 hours

404 (Not Found)

Does not Resend

401 (Unauthorized)

Does not Resend

409 (Conflict)

Does not Resend

400 (Bad Request)

Does not Resend

All Other Valid HTTP Codes

Does not Resend

Exceptions without code (timeouts etc)

1 minute

5 minutes

25 minutes

30 minutes

24 hours

The initial request should happen near real time and if a failure occurs, the retry attempts will wait according to the above. Each request that retries will block all other requests for the same end point and the same user that the form belongs to. If there is the same endpoint but different forms that were created by different users – requests will be blocked in separate queues.

  • Please note, that this plugin also works with the question and answer identifiers, so you can use them instead of question and answer numbers in plugin parameters.
  • The Remote Data Sender can only send data to URLs on HTTP ports 80 and 443, FTP port 21.

Logical Workflow

 Click here for more details:

Logical Workflow plugin is basically a Workflow plugin that can be triggered by certain criteria. This plugin is used to pass data from one form/survey to another based on a Logical Condition and also launch the second form/survey after the first one is submitted.

To set up the Logical Workflow between two forms, proceed with the following settings:

  • Create an Email Alert of 'To Respondent' or 'To another person' type to send an email with the link to the target form/survey after the first response is submitted.
  • When composing the email alert, insert [LINK_TO_ANOTHER_SURVEY] tag. If the plugin is set up properly, the email alert will be sent upon submit and the tag will be automatically replaced with the link to the second form/survey.
  • The original form/survey should contain an <EMAIL_REPLY/> tag to capture respondents' emails in a 'Single Line text' question type. It can be added using Email Reply feature. You can use <EMAIL_REPLY/> tag once per form/survey.

    When forms are ready for launch, insert the plugin and set up the following parameters:

  1. *Target Form or Survey Id - Indicate the target form/survey ID into which the data should be imported. This ID may be found on the main Forms/Survey page. Select a form/survey and it's ID will be shown on the right information pane. It can also be retrieved from the Master URL.

    Example

    https://app.form.com/f/XXXXXX/YYYY/ - Where XXXXXX is the Survey ID, and YYYY is the password.

  2. Logical condition - Specify the logical expression that would determine if the plugin should execute.To create a complex expression for multiple questions use the OR, AND logic operators and Advanced Logic rules. 

    If you use "Single line with pre-format options" question as a reference, the structure of the Logical condition will depend on the data format specified for the answer field: 

    • General. For this data format use Advanced Logic rules for text responses.

       Table of rules:
      OperatorDescriptionExample
      Logic ExpressionResults
      ==If text responses contain the exact line string indicated next to '==', then logic transition is fulfilled.

      This operator can also be used to refer to the record within the dropdown box of the '3D Matrix' type of question in the Qx.Ay.Cz==N format, where N is the sequence number of the item within the dropdown box that is selected by the respondent.
      Q1.A2==CatFlower
      Big Cat
      Cathlene
      Cat
      <>If text responses do not contain the exact line string indicated next to '<>', then logic transition is fulfilled.

      This operator can also be used to refer to the record within the dropdown box of the '3D Matrix' type of question in the Qx.Ay.Cz<>N format, where N is the sequence number of the item within the dropdown box that is not selected by the respondent.
      Q2.A3<>CatBig Cat
      Cathlene
      Cat
      ==LIKEIf text responses contain the line string indicated next to '==LIKE' regardless of its position in the text responses, then the logic transition is fulfilled.Q2.A3==LIKECatCat
      Big Cat
      Cathlene
      Beautiful Flower
      <>LIKEIf text responses do not contain the line string indicated next to '<>LIKE' regardless of its position in the text responses, then the logic transition is fulfilled.Q2.A3<>LIKECatCat Flower
      Big Cat
      Cathlene
      Beautiful Flower
      ==RLIKEIf text responses contain the line string specified by regular expressions next to '==RLIKE' regardless of its position in the text responses, then the logic transition is fulfilled.==RLIKERed(\s|\w)+CrossRed Bull
      Cross Roads
      Red fine Cross
      <>RLIKEIf text responses do not contain the line string specified by regular expressions next to '<>RLIKE' regardless of its position in the text responses, then the logic transition is fulfilled.<>RLIKERed(\s|\w)+CrossRed Bull
      Cross Roads
      Red fine Cross
      ==RMATCHES==RMATCHESxxx is the same as ==RLIKE^xxx$Q1.A1==RMATCHESRed(\s|\w)+CrossRed fine Cross
      Red fine Cross only
      <>RMATCHES<>RMATCHESxxx is the same as <>RLIKE^xxx$Q1.A1<>RMATCHESRed(\s|\w)+CrossRed fine Cross
      Red fine Cross only
    • Decimal Number/Number>0 While creating logical rule for this data format use only the following symbols: >, <. >=, <=, ==, <>. For instance,Q1.A1==1, Q1.A1>=1 OR Q1.A1<=8
  3. Name of link - Enter the link name, and the link to the target form will look as a clickable name. Leave it empty if you want to see just HTML link instead of the linked name. Piping is supported.
  4. Create follow-up as - Follow-up forms created by this plugin may have Not Started or In Progress statuses. If In Progress option is selected, it is possible to pass data from the 3D Matrix questions of the original form/survey to the 3D Matrix questions with the same number of answer options and scale of the destination form/survey. 

    Please note that if you choose In Progress option under Create follow-up as setting, Reminder emails cannot be sent to such follow-up responses. Follow up responses with Not Started status will be able to receive Reminders.

  5. *Question References - Insert references to questions you are sending data from and to using the Qx.Ay=Qw.Az format where:

    • x - question number of the source survey you are sending data from;
    • y - answer choice number of the source survey you are sending data from;
    • w - question number of the target survey you are sending data to;
    • z - answer choice number of the target survey you are sending data to.

    Please note, that this plugin also works with the question and answer identifiers, so you can use them instead of question and answer numbers in plugin parameters.

  • If you have a couple of Logical Workflow plugins applied in the original form with different target forms and same condition for execution, the [LINK_TO_ANOTHER_SURVEY] tag will be replaced with all links that were triggered by response submission. If you would like to set up separate Email Alerts with a specific target form/survey link, you can use [LINK_TO_ANOTHER_SURVEY_<target survey id>] tag. For example, [LINK_TO_ANOTHER_SURVEY_1166005].
  • Question references may be edited in Quick Edit box.
  • Please note that questions you are sending data from and to must have the same structure, including Sub header references.
  • It is possible to pass files uploaded by respondents from one form to another. To do this, simply reference a "File upload" question type and the file uploaded in the original survey will be available for downloading in destination survey.
  • This plugin does not support 3D Matrix type of question, if the follow-ups are created as Not Started.

Logical Workflow (Participant Portal)

 Click here for more details:

The Logical Workflow plugin enables you to deploy a form on Participant Portal for a given user when the current form/survey is submitted. It is important that for the correct data transmission from the source to destination survey, destination survey must be launched on the participant portal for at least one contact.

To apply this plugin adjust the following parameters:

  1. * Target survey/form Id - Please enter the numeric ID of the survey or form into which the data should be imported. (This ID can be retrieved from the Master URL).
  2. Logical condition - Specify the logical expression that would determine if the plugin should be executed.
  3. * Contact Manager - Please select a Contact Manager for which the new form should be published.
  4. * Contact ID Field - Please enter a reference to the form field where the Unique Key value of the given user is stored. Must be in Qx.Ay format.
  5. * Question References - Specify the question references. Use the paired format shown here: Qx.Ay=Qx.Ay where x,y are sequence numbers of questions and answer options you are referencing to. Left part of the formula references the original (source) survey and right part of the formula references the new (destination) survey.

    Example

    Q1.A1=Q5.A3 means that question 1 answer 1 of the original survey will be placed into question 5 answer 3 of the new survey.Question references may be edited in Quick Edit box. 
  • Parameters marked with * are required.
  • Please note that questions you are sending data from and to must have the same structure, including Sub header references.
  • Autocomplete function allows you faster and easier insert questions references. After entering Q or Qx.A system will show you the list of available questions or answer options. Picked element will be substituted by its sequence number within the survey.
  • Question references can be edited in Quick Edit box.
  • It is possible to pass files uploaded by respondents from one form to another. To do this, simply reference to a "File upload" question type and the file uploaded in original survey will be available for downloading in destination survey.
  • This plugin does not support 3D Matrix type of question.

Please note, that this plugin also works with question and answer identifiers, so you can use them instead of question and answer numbers in plugin parameters.

Remote Data Sender

 Click here for more details:

"Remote data sender" plugin is used to send data from the survey that is submitted by respondents to a third party application via HTTP request.

  1. *Remote URL - Indicate URL to access a third party and send the data to. Here you can add {RespondentID} and {FormID} formats to get respondent ID and form ID respectively.

    Example:

    The remote URL https://192.168.1.1/remote.php?respondent={RespondentID}&formID={FormID} would return respondent = 123456789 surveyID = 123456 on a server.

  2. *HTTP/HTTPS Request Method - Select the request method you want to use when sending data.
    • POST - is recommended for using if the URL of the third party application is very long or contains non-ASCII characters.
    • GET - this method is recommended if the target application is idempotent.
  3. Timeout - Specify a possible timeout of a third party application where you want to send the data.
  4. Submit Value - Provide parameter for the submit event.
  5. *Form Elements Names and Values - Input parameter names and values using the Param_Name=Param_value format. For example, FF_01=Q1.A1, where FF_01 is the arbitrary name of the parameter you are sending data to, Q1.A1 is the parameter value. 

    If you need to send the links to the files which were added via File Upload questions, you may use the following tags:

    LINK:Qx.Ay for downloadable links

    PLINK:Qx.Ay for preview links. The PLINK reference will show a preview of an image or an icon for other files. 

    When an image is accessed by a direct link, a browser will show a download dialog.

    To view the images right away, place a link to the image inside the <img src='downloadable link'/> HTML tag

Errors Processing 

if there are multiple plugins set up in a form/survey, the requests generated by the plugins will be sent via separate queues. These queues are unique per User Identifier and remote URL.

Depending on the received errors codes, messages sending will be retried according to the following rules:

  • Code 500. Module retries to send a request after 1,5,25 min, then every 30 min for 3 hours, and then sends it to the error queue.
  • Codes 408,502,503,504. Module retries to send a request after 1, 5, 25 min, then every 30 min for 24 hours, and then sends it to the error queue.
  • Module retries to send exceptions without code (timeouts, etc.) after 1, 5, 25 min, then every 30 min for 24 hours.
  • Other (404,401) codes are logged as errors and module does not try to send a request again.

For more information, please refer to the following table:

HTTP Code(s)

1st Interval

2nd Interval

3rd Interval

4th Interval

4th Interval Duration

500 (Internal Server Error)

1 minute

5 minutes

25 minutes

30 minutes

3 hours

408 (Request Timeout)

1 minute

5 minutes

25 minutes

30 minutes

24 hours

502 (Bad Gateway)

1 minute

5 minutes

25 minutes

30 minutes

24 hours

503 (Service Unavailable)

1 minute

5 minutes

25 minutes

30 minutes

24 hours

504 (Gateway Timeout)

1 minute

5 minutes

25 minutes

30 minutes

24 hours

404 (Not Found)

Does not Resend

401 (Unauthorized)

Does not Resend

409 (Conflict)

Does not Resend

400 (Bad Request)

Does not Resend

All Other Valid HTTP Codes

Does not Resend

Exceptions without code (timeouts etc)

1 minute

5 minutes

25 minutes

30 minutes

24 hours

The initial request should happen near real time and if a failure occurs, the retry attempts will wait according to the above. Each request that retries will block all other requests for the same endpoint and the same user that the form belongs to. If there is the same endpoint but different forms that were created by different users – requests will be blocked in separate queues.

  • Please note, that this plugin also works with the question and answer identifiers, so you can use them instead of question and answer numbers in plugin parameters.
  • The Remote Data Sender can only send data to URLs on HTTP ports 80 and 443, FTP port 21.

Survey Opening Validator

 Click here for more details:

"Survey opening validator" plugins is used to verify if a specific respondent can open and submit your survey upon the response from the third-party application.

To apply this plugin adjust the following parameters:

  1. *Remote URL - Indicate a third-party application URL to which the validation request will be sent using the following format: https://domain.com/
  2. *HTTP Request Method - Select the request method which will be used to access a third-party application. It is recommended to use the POST method if the URL is very long or has some non-ASCII characters. Use GET if the target form is idempotent (usually a pure query form).
  3. *Activation Criteria - Indicate the activation criteria as a value or use regular expression. For example, ^\[0-9]$, which means that if server response is an integer from 1 to 9, it satisfies indicated expression. If a response from the remote server matches indicated criteria, the survey or form will be served to respondent. This parameter can not be empty.

  4. *Validation Parameters - Input parameter names and values using the Param_Name=Param_value format. For instance, FF_01=Q1.A1, where FF_01 is the arbitrary unique name of the parameter you are sending data to, Q1.A1 is the parameter value which gets data from the survey question. To use send multiple parameters use the following syntax: FF_01=Qx.Ay&FF_02=Qx.Ay.Cz

  5. *Alert Message - If a response from the remote server does not match the Activation Criteria, this message will be displayed to survey or form respondent.
  6. Redirect URL - If the response from the remote server does not match the Activation Criteria, respondents will be redirected to the URL indicated here. This can be URL to any webpage or to your website.

  7. *Serve survey if remote service is down: - this parameter defines survey behavior if the remote service does not response and there is no chance to validate respondents. You can allow respondents to fill they surveys by selecting Yes. Select No to redirect them to the URL indicated in the Redirect URL parameter above.
  8. Error Message & Redirect URL - If the remote server generates an exception, you can redirect respondents to the external URL depending on the received error. Input error message that can be received from the remote server and URL to redirect respondents.

    Example

    The remote server generates an exception and sends error message Error1 and you want respondents to be redirected to the https://worldapp.com/ website. Thus the syntax will be as follows Error1 -> https://worldapp.com/. You can add as many items as you need by clicking the Add button.

Task Workflow (Participant Portal)

 Click here for more details:

The Task Workflow plugin enables you to deploy a form on Participant Portal for a given user when the current survey/form is submitted.

To apply this plugin adjust the following parameters:

  1. * Task definition - Task definition which will be used to create task
  2. * Task summary - Task name may include question references like [Q1.A1] which will be substituted by real answers.
  3. Task description - Task description may include question references like [Q1.A1] which will be substituted by real answers. This field is limited to 2,000 characters.
  4. Condition for Execution - Specify logical expression for conditional plugin execution. If you leave the field empty, tasks will be created unconditionally upon form submission.
  5. *Task assignee Reference - Enter an answer field reference in Qx.Ay notaion to specify the Contact ID of the Task Assignee.
  6. Due date reference - Enter an answer field reference in Qx.Ay notation to specify the Task Due Date.
  7. Assignor Reference - Enter an answer field reference in Qx.Ay notation to specify the Assignor ID.
  8. Execute on Repeat Submissions - Select whether to allow or prohibit plugin execution on form/survey re-submission. When allowed, a new task can be created each time the same respondent resubmits the form, subject to the condition for execution. When prohibited, a new task can be created only once upon first submission, if the execution condition is met.
  9. Plugin ID - If you set up multiple instances of the Task Workflow plugins in the same form and if for at least one of them the "Execute on Repeat Submissions" parameter is set to "Prohibited", please specify a unique Plugin ID number for each plugin with the "Prohibited" setting. You can leave Plugin ID field empty if there is only 1 Task Workflow plugin, or if "Execute on Repeat Submissions" is set to "Allowed".
  10. Form Autofill Reference - Specify question references to autofill the form attached to a task. Use following format: Qx=Qy or Qx.Ay=Qz.Ac.


  • Parameters marked with * are required.
  • Please note that questions you are sending data from and to must have the same structure, including Sub header references.
  • Autocomplete function allows you faster and easier insert questions references. After entering Q or Qx.A system will show you the list of available questions or answer options. Picked element will be substituted by its sequence number within the survey.
  • Question references can be edited in Quick Edit box.
  • It is possible to pass files uploaded by respondents from one form to another. To do this, simply reference to a "File upload" question type and the file uploaded in the original survey will be available for downloading in destination survey.

Please note, that this plugin also works with question and answer identifiers, so you can use them instead of question and answer numbers in plugin parameters.

Workflow

 Click here for more details:

Workflow plugin is commonly used to send an invitation to a new form/survey and autofill that survey with the data from the previous (original) form/survey.

Let's consider an example: there are two forms/surveys you need to send to respondents. The first one is a regular form/survey and the second one should be prepopulated with the data from the first one. Please note that questions you are sending data from and to must have the same structure, including subheader references.

To set up Workflow between two forms, proceed with the following settings:

  • Create an Email Alert of 'To Respondent' or 'To another person' type to send an email with the link to the target form/survey after the first response is submitted.
  • When composing the email alert, insert [LINK_TO_ANOTHER_SURVEY] tag.If the plugin is set up properly, the email alert will be sent upon submit and the tag will be automatically replaced with the link to the second form/survey.
  • The original form/survey should contain an <EMAIL_REPLY/>tag to capture respondents' emails in a 'Single Line text' question type. It can be added using Email Reply feature. You can use one <EMAIL_REPLY/> tag per form/survey.

When forms are ready for launch, insert the plugin and set up the following parameters:

  1. *Target Form or Survey Id - Indicate the target form/survey ID into which the data should be imported. This ID can be retrieved from the Master URL.

    Example

    https://app.form.com/f/XXXXXX/YYYY/ - Where XXXXXX is the Survey ID, and YYYY is the password.

  2. *Question References - Insert references to the questions you are sending data from and to using the Qx.Ay=Qw.Az format, where:

    x - question number of the source survey you are sending data from;
    y - answer choice number of the source survey you are sending data from;
    w - question number of the target survey you are sending data to;
    z - answer choice number of the target survey you are sending data to.

    Please note, that this plugin also works with the question and answer identifiers, so you can use them instead of question and answer numbers in plugin parameters.

  • If you have a couple of Workflow plugins applied in the original form with different target forms and same condition for execution, the [LINK_TO_ANOTHER_SURVEY] tag will be replaced with all links that were triggered by response submission. If you would like to set up separate Email Alerts with a specific target form/survey link, you can use [LINK_TO_ANOTHER_SURVEY_<target survey id>] tag. For example, [LINK_TO_ANOTHER_SURVEY_1166005].
  • This plugin does not support 3D Matrix type of question.
  • If you pass data for questions of Multiline or Single Line types and comment fields of appropriate questions no more than 1024 characters will be imported. Characters that exceed the limit will be truncated.
  • Question references can be edited in Quick Edit box.

 

 

 

  • No labels