1c-bsp-registration

Registering an external data processor for BSP SSL in 1C requires inserting the ExternalDataProcessorInfo() function into the processor's ObjectModule. This Skill automates that insertion within the #Region PublicInterface section to properly configure the SSL registration.

1C BSP SSL registration supports multiple processor kinds including AdditionalDataProcessor, AdditionalReport, ObjectFilling, Report, PrintForm, and RelatedObjectCreation. Each kind receives specific command mappings and optional server handlers as required by its scope.

The ExternalDataProcessorInfo() method is injected directly into the ObjectModule.bsl file within the #Region PublicInterface region. This ensures correct API method references, versioning, and command mappings are applied based on the specific processor kind.

Server handlers are optional for 1C external report registration depending on the processor kind and its required scope. This Skill automatically handles and includes the appropriate server handler blocks during the ExternalDataProcessorInfo() insertion when they are necessary.

Yes, you can use this registration approach for PrintForm processor kinds in 1C. The Skill configures the correct API method references, versioning, and command mappings specifically required to register print forms within the BSP SSL framework.

1C external data processors fail BSP registration when ExternalDataProcessorInfo() is missing or incorrectly placed outside the #Region PublicInterface in the ObjectModule. Automating this insertion ensures correct API references, versioning, and command mappings per processor kind.