English | English
German | Deutsch
Indonesian | Indonesia
Italian | Italiano
Spanish | Español
Turkish | Türkçe
Properties — Tooltip and Required field
Scope: managed applications, mobile applications, and ordinary applications.
Scope: managed applications, ordinary applications. 1. Tooltip. The property is specified for objects—attributes, tabular sections, register dimensions, and resources—that appear in the user interface and require a short explanation about their purpose. Do not specify tooltips for the most frequently used attributes. Do not use tooltips to provide users with instructions on how to complete the task. Instead, adjust the user scenarios, so that the user could finish the task without reading the tooltips. Clear the tooltips that Designer automatically generates when you create controls or control groups. For example, "Header group". See also: Form tooltips |
2.1. Required field. For all required standard metadata objects, attributes, and tabular sections, set the "Required field" property to "Display error".
In some cases, posting of a document with unfilled attributes and tabular sections makes no sense for recording purposes. By the definition, a Sales order is a customer request for a definite quantity of goods or services. A sales order with the unfilled Customer field and Goods tabular section does not deliver its purpose. So, the Required field property for them must be set to "Display error."
2.2. Note that all checks and restrictions that are derived from the user scenarios should be implemented in metadata objects. That means that if even one scenario stipulates that an attribute is required, "Required field" for this attribute must be set to "Display error." If the attribute is not required in other scenarios, employ event handler FillCheckProcessing to adjust the "Required field" value.
It is not recommended that you would do otherwise: setting "Required field" to "No" and changing its value with the FillCheckProcessing event handler. Such approach makes the analysis of the configuration behavior more complicated.
2.3. If an attribute is conditionally required, use conditional appearance to toggle the "Unfilled mark" indicator that marks empty fields. If in the current object state the attribute is not required, turn the indicator off.
See also: