1Ci Support Help Center home page
Submit a request
Sign in
  1. 1Ci Support
  2. 1C:Enterprise Development Standards
  3. Creating and modifying metadata objects
  4. Data storage arrangement

Tooltip and filling check

  • Data storage arrangement
    • General data storage arrangement information
    • Refining the essence of a metadata object
    • Name, synonym, comment
    • Tooltip and filling check
    • Using configuration objects codes (numbers)
    • Using string type attributes
    • Restrictions on the use of composite type attributes
    • Requirements for posting documents
    • Using record activity
    • Register self-sufficiency
See more

Scope: managed applications, mobile applications, and ordinary applications.

Scope (details): a managed application, an ordinary application.

1.1. "Tooltip" property. It is set for objects (attributes of objects, tabular sections, dimensions, and register resources) that are displayed as UI elements and require explanation of their purpose. Do not provide tooltips for daily used attributes.

We do not recommend that you provide instructions or explain the attribute behavior in your tooltips. Instead, optimize the scenarios related to it.

Remember to delete irrelevant tooltips automatically generated by Designer when creating form controls (groups). For example, "Header group".

See also: Form tooltips, Interface subsystems tooltips, Texts.

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.

See also:

  • Names, synonyms, and comments
© 2020 1C INTERNATIONAL LLC www.1Ci.com Support policy