Monday, September 28, 2026
1 change · saas-18.4
Resolved issues and error corrections
This fixes a survey navigation issue where returning to a near-final question could leave the button in the wrong state. Users are now less likely to accidentally submit a survey early, improving completion accuracy and confidence.
Original PR description
On a potentially final survey question, the submit button's state is dynamically updated (from 'Submit' to 'Continue') if the selected answer triggers a subsequent conditional question. However, this dynamic check was not performed when a user navigated backwards to such a question. This could lead to a situation where the button incorrectly showed 'Continue'. If the user then selected an answer that did not trigger a new question, the survey would be prematurely and unexpectedly submitted. This is resolved by refactoring the logic that calculates these "triggering answers" into a shared helper method. This method is now invoked for both forward and backward navigation, ensuring the button's state is always correctly calculated before the page is rendered. Task-5114087