1c-bsp-command

To add a new 1C external data processor command, the Skill inserts a command record into СведенияОВнешнейОбработке() before returning registration parameters, generating the identifier, presentation, and execution context for server- and client-side handlers.

BSP command generation handles execution contexts by applying a mapping for command types with default behaviors, creating separate server-side and client-side handler stubs to ensure the 1C:Enterprise configuration routes execution correctly.

Yes, you can use this to extend configurations managing additional processing in 1C:Enterprise by applying it to existing external data processors to introduce command identifiers and presentations without manual coding.

No, manual insertion is unnecessary because the Skill automatically locates the Return RegistrationParameters statement in СведенияОВнешнейОбработке() and places the new BSP command record directly before it.

The best way to auto-generate a BSP command handler in 1C is to provide the processing name, command identifier, and optional command type, allowing the Skill to automatically insert the record and generate the matching handler.