Scope: managed applications.
If user presentation properties are defined for metadata objects, fill them in as follows.
1. Object synonym must briefly identify the object. It is required for every object.
2. Object presentation (for registers - a record presentation). Set an object name in singular, for example, "Currency". The name must be short and intuitive. For example, instead of "Version of the configuration being checked", use simply "Version".
Fill in an object presentation if the synonym cannot be used as an object name in singular.
3. Extended object presentation (for registers - an extended record presentation). Set a full object name in singular. Fill it in only if the object name specified in the object presentation (or in a synonym if not filled in) is less descriptive than its full name. For example, the extended object presentation is "Sales of goods and services", while the object presentation is "Sales".
4. List presentation. Set object names in plural, for example, "Currencies". Sometimes, if the list content can be described by an established term, you can use it to name the list. For example, "Standard Occupational Classification" instead of "Occupations". The name must be short and intuitive. For example, use "UoM classifier" instead of "Unit of measure classifier".
Fill it in if the synonym cannot be used as an object list name.
5. Extended list presentation. Specify a full name of the object list. Fill it in if a list name specified in the list presentation (or in the synonym if not filled) is less descriptive than the full list name.
For example, the extended list presentation is "Products (goods and services)", the list presentation is not filled in, and the synonym is "Products".
6. Extended presentation. Specify a full metadata object name. Fill it in if the object name set in the synonym is less descriptive than its full name.
For example, a data processor synonym is "Client bank", an extended presentation is "Client bank (payment documents exchange)".
7. Note. Sets a note for the metadata object purpose. Notes consist of complete phrases. Fill in notes for metadata objects whose presentations do not convey their purposes.
For example, you can use the following note for the Companies catalog: "Legal entities and entrepreneurs of our company".
8. Picture. Set pictures for upper level subsystems with the "Include in command interface" check box selected. Picture size: 32 x 32.
- Appendix 3. Rules of generating standard command texts and automatic form headers in 1C:Enterprise Developer Guide.