Hello, can you please consider including an option to not display the asterisk on input widgets that are marked as mandatory? It is a neat feature but can wreck havoc on the UI. Please see the image below for an example of the UI issue encountered.
Hi @kkl,
Thanks for sharing the request and I see your concern.
Generally, the red asterisk is important to include at least one visual signifier to the operator that the field is required. To encourage best practices, it is always there if the field is mark required. It looks like you’re creating a table of inputs, but I’m curious to learn more. What is your goal/use case for this step’s UI?
Best,
Yuji
1 Like
Hi @ychan164 , yes you are right. This is a table of user input.
I agree that a visual indicator for a manual field is best practices. In this case, I would prefer to add a single asterisk in the far-left column or indicate that the fields are required in another manner to reduce the number of asterisks and declutter the table.
Best,
Kevin
Hi Aiden,
Quick question about the use case you are modeling here.
I am trying to understand why there are 3x sample size & 3x accept fields on the same step.
What “goes” into the Accept fields? And why by 3?
Maybe what I am asking is “is this a paper on glass implementation”?
Cheers,
Hi @Olivier
does this effect the usefulness of hiding the asterisk?
I think the Label is far to far away from the input. Looks weird and takes a lot of space.
Also CI / CD may have rules for color and appearance of a mandatory-identifier… (we do)
That’s why I usually hide the Label as well and create an own one with a text-widget…
Paper on glas is a totally valid first step to digitalization. the rest is agile development after go live of a mvp … Tulips idea if you want so 
1 Like