We use more and more the Request Forms as a way to optimize the resulting workflow and templates associated to the executable items.
As a way to standardize answers and reporting, we use as much as we can our custom fields in our request form.
The Pro's are great: structure and standardization.
The AS-IS Cons / User-story:
#1 the UI/UX in the request form can't be customized, and are ugly, particularly with custom fields with a long list of available options
Example1 : we do manage a portfolio of brands, and our WebDesign team needs to know which brand is concerned by the request. This list is really long, and the UI does not worth it
Idea: As a request form creator, i would like to be able to setup the look-and-feel of the field to be a a multi-value select field, where values to select only appear when you enter in the corresponding field.
It should be combined with a autocompletion-as-you-type, a bit like the similar experience in a Wrike table view. here the example is the same custom field "brand" from within Wrike Table view
#2 - The workforce is working for ALL value of a particular custom fields. BUT, in frontend, a form can have been designed for a more narrow group of people. They MUST NOT see all existing value of a fields.
As a Request Form Creator, I would like to be able to use an existing custom field, but then select which existing value will be availalable or not available on the Request Form front end experience
Example: In green, those would be the sole values available for a Customer X, while the Red value MUST not be visible. the absence of this possibility is preventing us to use custom fields mapping for some use case, loosing the efficiency we expect from a process perspective
many thanks in advance