We currently have several request forms that use a decision tree to different pages, depending on what is selected by the requestor. Currently, we have a custom field called "Ticket #". We can only use this field once on a form, even if it's under a branch of a decision tree. This makes sense if you only have one flow to the form, but when you have multiple paths, it should be ok to show it multiple times on the form at the end of each path. It makes more sense for us to put it at the end of each path than at the beginning of the form. Logic needs to be built into the forms so that it can see there is only going to be the ability to enter the field once, even if it's on the form multiple times in the admin request form editor. Thanks.
Thank you for your feedback! Now other members can find, vote, and discuss your idea.
Our Community Team reads every suggestion (yes, every one) then compiles and shares the feedback with our Product Team. Happy posting!