Description - We would like a more intuitive way for requestors to clear out data in irrelevant form fields when they change their selections in a request form.
Why is this feature important to you - We want to eliminate confusion for requestors and prevent errors in automated processes and reporting. Currently, our Fusion scenario triggers messages based on a calculated field, and retained data from previously selected options can cause false positives. Requestors often believe they’ve submitted the request correctly, unaware that hidden fields still contain outdated data.
How would you like the feature to work - When a requestor unselects an option, any data entered in fields associated with that option’s conditional logic should be automatically cleared. This would ensure that only relevant data is retained and reduce the risk of errors caused by hidden, outdated inputs.
Current Behaviour - Our request intake form uses extensive conditional logic. Occasionally, a requestor will change their selection mid-submission or copy a previous request and modify it. When they deselect an option, the associated fields are hidden—but the data within them remains. This retained data can interfere with calculated fields and downstream automation, leading to confusion and incorrect outputs. I refer to this issue as the “ghost of a previous deliverable.” Despite efforts to educate requestors, many find it unintuitive that hidden fields still retain data. I’ve attached a tutorial video I created a couple years ago to demonstrate this behavior.