Making multiline field mandatory on UI

[Shubham Tulsyan]

Hello Team,

I am creating one form where I have a multiline field named . This field was required in class level. This field is available on a “secondary” tab. After completing all required fields in the first tab, the OK button becomes enabled and after clicking ok … the multi-line string input gets highlighted. However unlike other inputs this particular control does not enable the OK button after entering the value.. When we changed the property of this field “Multiline=False”, then it started working.

Is it a product bug or we need to change some other property?

0

[Patrick Tsang]

Hi Shubham,

I think we’re discussing 2 issues here:

1. The OK button should stay disabled because the required field on the second tab has not been filled.
2. The OK button does not re-enable after editing the field on the second tab.

For #1, there is a framework limitation where it only checks the visible views on the current tab, so for Opportunity popup screens (OpportunityProperties and OpportunityEditProperties) we control initial enablement with the updateButtonEnablement function.  That function should be updated with any customized required attributes.  Generally, from a UX perspective, we also recommend you place as many (preferably all) required fields on the first tab if possible to prevent the user playing hide and seek for required fields.

For #2, as long as we fix #1 we did not observe this issue internally.  Please give it a try.

Regards,

Patrick

0

[Shubham Tulsyan]

Hi Patrick,

Issue is when after clicking OK button on TAB-1, TAB-2 mandatory fields are highlighted in red. So When We navigate to TAB-2 and if there are any multiline mandatory field, even after giving value in that field and navigating to other field, red highlight is not going away.

0

[Patrick Tsang]

I understand.  Please see my comment about updating “updateButtonEnablement”.  The OK button should not have been enabled in the first place, when you were on TAB-1.

0

[Shubham Tulsyan]

Hi Patrick,

Can you please provide more details on below statement:

“so for Opportunity popup screens (OpportunityProperties and OpportunityEditProperties) we control initial enablement with the updateButtonEnablement function.  That function should be updated with any customized required attributes.”

How to do this?

0

[Community Manager]

Hi Shubham,

Can you be more specific as in what you are not able to do ?

The updateButtonEnablement is a function in the script tab of the two screens mentioned. It is already checking for  two attributes to be not null and enabling/disabling the OK button.

You should be able to check for other required attributes (in different tabs) and enable/disable the button using the same logic.

 

Regards,
Dhruv

0

[Author]

Posts