epf-add-form

Automate adding managed forms to 1C external data processors.

413|90|Updated Aug 31, 2025
One-click install
npx skills add https://github.com/comol/cursor_rules_1c --skill epf-add-form
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: epf-add-form
Source: https://github.com/comol/cursor_rules_1c/tree/main/.cursor/source/epf-add-form
Command: npx skills add https://github.com/comol/cursor_rules_1c --skill epf-add-form

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Manually adding a new managed form to a 1C external data processor is error prone and time consuming; this Skill automates the creation of all necessary form metadata, XML descriptions, BSL module scaffolding, and processor registration.

Core Features & Use Cases

  • Create metadata for the new form under Forms/{ProcessorName}.xml with a unique UUID and proper Name and Synonym.
  • Generate the Form.xml description under Forms/{FormName}/Ext/Form.xml and a corresponding Module.bsl with the standard regions for event handlers and utilities.
  • Update the root processor XML to register the new form and set it as default when appropriate, ensuring the workflow can immediately reference the new form.
  • Support common use cases such as adding forms to existing external processors for new UI functionality or workflow extensions.

Quick Start

Invoke the tool to create and register a new managed form for your processor, supplying ProcessorName and FormName.

Frequently Asked Questions about epf-add-form

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

FAQPage Schema
How do I add a managed form to a 1C external data processor?

To add a managed form to a 1C external data processor, you need to create form metadata, generate the Form.xml description, scaffold a BSL module, and update the root processor XML for registration. This automates those steps using ProcessorName and FormName inputs.

What files need to be modified when registering a new form in a 1C external processor?

Registering a new form in a 1C external processor requires modifying the root processor XML and creating Forms metadata, a Form.xml description under the form directory, and a Module.bsl file for event handlers and utilities.

Can I set a default form automatically when creating a managed form in 1C?

Yes, when creating a managed form in 1C, the process can automatically set it as the DefaultForm in the root processor XML when appropriate, ensuring the external data processor workflow immediately references the new form.

Do I need to manually generate a UUID for a 1C external processor form?

No, you do not need to manually generate a UUID. The automated process creates the form metadata under Forms with a unique UUID, proper Name, and Synonym automatically as part of the generation workflow.

What parameters are required to create a 1C managed form for an external data processor?

Creating a 1C managed form requires the ProcessorName and FormName parameters. You can also supply an optional Synonym for the form metadata and an optional SrcDir to specify the source directory structure.

Why does adding a managed form to a 1C external data processor fail manually?

Adding a managed form to a 1C external data processor fails manually due to error-prone steps like mismatched XML registration and missing metadata. Automating the creation of Forms metadata, Form.xml, and BSL scaffolding eliminates these issues.