Answered
Fix the bug that allows a designer to make a field mandatory and hidden.
A field that is hidden and mandatory prevents submission taking place but user is unable to resolve.
1
Comments
Please sign in to leave a comment.
Interestingly enough, this one isn't a bug. We use it somewhat frequently as a way to ensure that values are being entered as expected. For example, this method of not allowing a user to create a Submission without being Dispatched or this, where you can prevent users from adding numbers that don't work and similarly, where you can have maximum and minimum values for a time field. So it definitely comes in handy when used appropriately. Maybe an interesting feature request here would be to decide on an account or app-by-app basis whether you'd like this functionality to be possible.
Seems it patches other problems.
Having it default to off on an app would be preferable with the designer opting to turn it on if they need it for a work around.
Use this in every app with workflows to coerce users into choosing the correct person for handoffs..
https://help.gocanvas.com/hc/en-us/community/posts/360025981094-Using-Reference-Data-and-Email-Field-for-a-Handoff-Screen
"Maybe an interesting feature request here would be to decide on an account or app-by-app basis whether you'd like this functionality to be possible"
Has this progressed to a feature request?
Feel free to turn it into one, or update this topic with that context if you'd like, Dave. I haven't marked this as answered, so you definitely have the opportunity to add that requirement.
I really hope someone else in GoCanvas reads these posts and stops to consider what the customer experience is like at the moment.
But yes, I can take your suggestion to fix this and put it in as a request.
Is anyone at GoCanvas reading these? The feature request has not received any update.
This is no longer considered a feature request. This is intended functionality.