- Comment attribute of documents
- Deleting obsolete metadata objects from configurations
- Delivering data in configuration packages
- Document posting requirements
- Generic data storage principles
- Handling inactive objects
- Length of configuration object codes and numbers
- Limitations to usage of composite-type attributes
- Name, synonym, and comment
- Reflecting the nature of metadata objects using attributes
- Self-sufficiency of registers
- Tooltips and fill checks
- Using attributes of String type
- Using predefined items
- Using the Active property of register records
- Business process route map layout recommendations
- Code writing standards for easier localization
- Common module naming rules
- Configuration initialization
- General requirements to configurations
- Metadata object names in configurations
- Restrictions to renaming metadata objects
- Shared configuration development workflow
- Specifics of configuration development for Linux
- Thick client support in managed applications that run in the client/server mode
- Time zone differences
- User settings
- Using common attributes
- Using defined types
- Using functional options
- Using session parameters
- Using subsystems
