What is the proposed idea/solution?
In forms, we are able to capture automatically the account of the person submitting the form (for logged in accounts). Since this is already a feature in place, it would be important to enable this information as a type of filter to be used to manipulate the visibility of subsequent inputs on the form.
This way, if user John is submitting the response, we can add a filter down the form so that only if user "john" is submitting the form, the field "A" becomes visible. If user is not "john", field "A" will not be shown.
Note: we are aware that using the manual requester assignment works, but our customers complain that they have to enter it manually, so the improvement is really on using the automated user detection.
How does is solve the user problems?
Big organizations with multiple teams have different requirements according to the different user groups/teams. This simple feature allows to have better control of the information requested without the need to duplicate a form based on different teams, hence, reducing the maintenance/operational costs.
How was this validated?
It is a problem that we have in our organization that we're not able to solve as we don't want to duplicate forms. At the moment we mitigate it with training and adding as many "helper texts" to the forms, however, people tend not to read those helper texts more often than we'd like, and our data continues to be corrupted and we need to manually review all the information and cleanup after, when this quick filter would reduce all of that.
Who is the target audience?
Enterprise customers.
