@Matthew_Ng Hi Matthew, after some debugging, I believe the problem is caused by required but hidden columns in the form.
Your form is divided into multiple pages using page header columns. Depending on the answers to certain questions, you want to hide some of these pages, and this is done using the Show_If constraint of the page headers. By hiding the page headers, you can hide all other columns in the entire page. However, some of these columns are marked as required. As a result, when you click save at the end of the form, the form will go into an error state and will not be submitted. Normally, the app will backtrack to the skipped required columns and highlight them to tell the app user to fill these columns. However, since these columns will no longer be visible at this point, this does not happen and thus the form appears to be stuck.
To fix this problem, you will need to modify the required columns in your form. Instead of using a hard requirement check, which makes the column always required, you configure the Required_If constraint of the column to use the same expression as the Show_If constraint of the page header. If the page header, and thus the entire, will only displayed if the answer to a previous question is โMRTโ, then the Required_If condition of the column should be something like this: [Answer] = โMRTโ. This way, the column will only be required if it is displayed, and the form will not fall into an error state when the user saves the form.
LinkedIn
Twitter
