epf-bsp-add-command

Add a new command to 1C BSP external processing and update registration logic.

Updated Mar 29, 2026
One-click install
npx skills add https://github.com/Alex1980Alex/1C-Framework --skill epf-bsp-add-command-alex1980alex
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: epf-bsp-add-command
Source: https://github.com/Alex1980Alex/1C-Framework/tree/main/external/cc-1c-skills/.claude/skills/epf-bsp-add-command
Command: npx skills add https://github.com/Alex1980Alex/1C-Framework --skill epf-bsp-add-command-alex1980alex

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps maintain 1C BSP external processing code by adding new commands, updating the registration function, and creating the matching handler in the correct module.

Core Features & Use Cases

  • Command registration: Inserts a new command into СведенияОВнешнейОбработке with the right usage type and user-facing label.
  • Handler generation: Adds or extends the server-side, client-side, or print handler without creating duplicate procedures.
  • BSP-aware defaults: Infers the command type from the processing kind when the user does not specify it.
  • Use case: A developer needs to add an action that opens a form in an additional processing file and wants the command wired consistently with existing 1C conventions.

Quick Start

Ask the Skill to add a new BSP command for your 1C processing and let it update the registration code and matching handler in the appropriate module.

Frequently Asked Questions about epf-bsp-add-command

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

FAQPage Schema
How do I add a new command to 1C BSP external processing?

To add a new command to 1C BSP external processing, update the СведенияОВнешнейОбработке registration function with the correct usage type and label, then place the matching handler in the object or form module without duplicating existing procedures.

What is the correct way to register a command in СведенияОВнешнейОбработке?

Registering a command in СведенияОВнешнейОбработке requires inserting the new command details with the appropriate usage type and a user-facing label. The command type can be inferred automatically from the processing kind if not explicitly specified.

How do I prevent duplicate procedures when generating BSP command handlers?

To prevent duplicate procedures when generating BSP command handlers, the system adds or extends the server-side, client-side, or print handler by checking existing procedures in the object module or form module before inserting the new code.

Does this BSP command tool support safe-mode script handlers?

Yes, this BSP command tool supports safe-mode script handlers. It applies to additional reports and processors when opening forms, calling client or server methods, filling forms, or running safe-mode script handlers.

Can I use this to wire additional reports and processors with 1C conventions?

Yes, you can use this to wire additional reports and processors with 1C conventions. It ensures commands are connected consistently by updating registration logic and placing handlers in the correct module based on the processing kind.

Why is my new BSP command not working in 1C?

Your new BSP command may not be working in 1C if the registration function СведенияОВнешнейОбработке is not updated with the correct usage type, or if the handler is placed in the wrong module or duplicates an existing procedure.