External Survey using parameter reference

In the following tutorial in the first step Enter Data a survey form is filled out, which is uploaded via an external URI and in the second step Review Data the entries from the first step were displayed.
In both steps, the survey is loaded from an external URI as shown in the user guide External Survey URI. The survey Json looks like the next image.

{
 "logoPosition": "right",
 "pages": [
  {
   "name": "page1",
   "elements": [
    {
     "type": "text",
     "name": "Name",
     "isRequired": true
    },
    {
     "type": "text",
     "name": "Address",
     "isRequired": true
    },
    {
     "type": "text",
     "name": "Phone number",
     "isRequired": true,
     "inputType": "tel"
    }
   ]
  }
 ],
 "showQuestionNumbers": "off"
}

The form created from the external survey is displayed as follows at runtime.

The changes to the external survey are applied directly at runtime without prior adjustment of the process. For example we add a new field Date of birth to the external Survey form and this modified form is called in the client directly after the activity is suspended (see next image).

Survey form with newly added field 'Date of birth'

In the second step Review Data you review the data from the first step Enter Data.

Parameter Reference

As you can also see from the process diagram, the data from the first step was passed to the second step using the Survey Data parameter. However, we need the output parameter Name extra because we want to use it to create the instance name and thus the worklist entry. The output parameter Name is from the parameter template type Default and it is assigned to the question Name.

Now we will show you how we use parameter references in the process and how useful they can be for the user. In this case, in the second step, we replace the instance name with the parameter reference (%s:Name%) and display it in the worklist. To do this, we set a parameter reference in the basic properties of the process. Since a value is only assigned to the Name parameter in the first step, the instance name can be displayed in the second step.

In the second step, you can see the resolved parameter reference Instance Name in the worklist.