Scope: managed applications, mobile applications, and ordinary applications.
2.1. "Filling check" property. For all required standard metadata objects, attributes, and tabular sections, set the "Filling check" property to "Raise error".
In some cases, posting of a document with unfilled attributes and tabular sections makes no sense for recording purposes. For example, Sales order is a customer request for delivery of a definite quantity of goods. An order with unfilled "Customer" field and Goods tabular section makes no sense. That is why set the "Filling check" property to "Raise error" for the Customer attribute and the Goods tabular section.
2.2. Upon setting the "Filling check" property, remember to detail all restrictions and checks in the configuration metadata. If at least one object scenario requires this attribute to be filled, set the "Filling check" property to "Raise error". If this attribute is not required in other scenarios, consider such cases in the FillCheckProcessing object module event handler.
We do not recommend that you set the "Filling check" property to "Do not check" and provide extra filling checks in the FillCheckProcessing handler. Such extra checks complicate analysis of the configuration behavior.
2.3. If attribute filling check depends on certain conditions, manage automark of unfilled values using conditional appearance of object forms. It is not used if no attribute filling check is required for this object state.