1c-form-patterns

Provides managed form design patterns, naming conventions, and layout archetypes for 1C:Enterprise forms.

Updated Jun 26, 2026
One-click install
npx skills add https://github.com/pavelvdo/universal-xml-exchange2 --skill 1c-form-patterns-pavelvdo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 1c-form-patterns
Source: https://github.com/pavelvdo/universal-xml-exchange2/tree/main/.cursor/skills/1c-forms/patterns
Command: npx skills add https://github.com/pavelvdo/universal-xml-exchange2 --skill 1c-form-patterns-pavelvdo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Designing managed forms in 1C:Enterprise without established patterns leads to inconsistent layouts, ad-hoc element naming, and rework during Configurator implementation or programmatic BSL form construction. ## Core Features & Use Cases - Form Archetypes: Ready-made structural templates for document forms, data processor forms, list forms, catalog item forms, and wizards, including events and properties. - Naming Conventions: Standardized names for groups, elements, and event handlers (e.g., HeaderGroup, Filter[Field]Use, ПриИзменении suffixes) to keep form code consistent. - Advanced Patterns: Collapsible groups, warning banners, popup menus in command bars, hyperlink labels, and forms without standard command bars, plus a full DSL example. - Use Case: When a change request requires a new data processor form, pick the Data Processor archetype, apply the naming conventions, and hand the layout to the Configurator or generate programmatic BSL elements. ## Quick Start Ask the assistant to design a managed form layout for a 1C document or data processor using the standard form archetypes and naming conventions.

Frequently Asked Questions about 1c-form-patterns

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design a managed form layout in 1C:Enterprise?

Start by selecting a matching archetype such as Document Form, Data Processor Form, List Form, Catalog Item Form, or Wizard. Each archetype defines the group hierarchy, required events like OnCreateAtServer, and properties such as autoTitle and windowOpeningMode.

What naming conventions should I use for 1C form elements?

Use purpose-based names: HeaderGroup and FooterGroup for layout groups, Filter[Field] plus Filter[Field]Use for filter pairs, [Command]Button for buttons, and Totals[Field] for totals. Event handlers combine the element name with a Russian suffix like ПриИзменении or Нажатие.

Can I create 1C form elements programmatically in BSL instead of Configurator?

Yes, the patterns apply to both Configurator-based design and programmatic element creation in the form module using BSL. The reference explicitly targets these two paths and excludes generated Form.xml editing.

How do I add filters to a 1C dynamic list form?

Place a horizontal filter group above the list table and create a pair of attributes per filter: Filter[Field] for the value and Filter[Field]Use as a boolean checkbox. Set autoSaveDataInSettings to Use so filter states persist.

When should I use a warning banner or collapsible group in a 1C form?

Use collapsible groups for optional sections like signatures or additional details, with behavior set to Collapsible and collapsed true. Use a hidden warning banner group with an image and label, shown programmatically when a specific state occurs.