That is to be expected. Here’s a revision of the basic differences in directions and when you might use what:
- IN - If you want to send a value TO the form, either to display or use for some calculations.
If you end up changing the value, it won’t reflect into your main workflow once the form is submitted. It only goes one way - inward
- OUT - The exact opposite, a value that your form gives back to the workflow, but it may not exist before calling the form. The easiest example is any user input - you present an empty field and whatever user enters/selects - is the OUTPUT from your form.
- IN/OUT - This is when you want to send a value in but also expect to know about any changes to its value during the course of the form execution.
An example could be that you’re getting an OCR extracted data validated from a user through a form. You present what the bot was able to capture and get the user to correct it if necessary.
The output will reflect into your workflow when the direction is two-way.
Now what @ppr and @ui_xpath are saying is that when setting direction to IN/OUT, it needs to be a SINGLE variable in the field. Referring to the explanation of IN/OUT above, because you want to read back whatever was changed, it should be ONE variable where the workflow will store it for further use.
In your screenshot above, continue to use IN/OUT if you need, just use a single variable that represents ‘matchValidationError’ variable, instead of the constructed string of 3 variables
To avoid confusion and as a good practice, please consider adding a prefix to your arguments:
in_ (for IN direction)
out_ (for OUT direction)
io_ (for IN/OUT direction)
followed by the variable name from the workflow.