There are 2 scenarios where default values are likely to improve user experience: where most users pick the same answer or if you require the user to enter the same answer multiple times:
When you expect most users to choose a particular option.
Adding a default value would therefore save most users considerable amount of time. Please note that this feature works only in forms embedded in client portals.
A. Adding a default value to "yes/no" questions:
B. Adding a default value for multiple choice questions:
Add a number of your default choice (starting with 0)
2. When you require the users to enter the same value multiple times in several forms that are part of the same workflow.
Imagine a scenario where you need to ask for user's name or address multiple times in a complex onboarding workflow. This may be required because each form is then signed and the PDF is sent to another department which requires this information.
To set-up default values:
A. Add a variable name to the appropriate field in Form A
B. Add a variable name to the Form A
C. Add a 'default value' variable in the field that requires the value from Form A. Note how to construct the expression:
[Variable Name of the Source Form].[Variable Name of the Source Widget] (for example Form1.FirstName, where Form1 is the variable assigned to FormA and FirstName is the variable assigned to the Text field
if your source widget is embedded in a section, make sure you also assign a variable name to the saction and add it to the expression: [Variable Name of the Source Form].[Variable Name of the Section].[Variable Name of the Source Widget]
From the end user's perspective, the process will look like this:
Note that the 'default' value works when the data travels between forms. You cannot use it in the same form (so if you ask someone to enter the same data multiple times in the same form, they will have re-enter that data each time).