1c-bsp-registration

To register an external data processor in 1C, you add the ExternalDataProcessorInfo function to the object module. This function declares the processor kind and target metadata objects for the Additional Reports and Data Processors subsystem.

The ExternalDataProcessorInfo function is used in 1C to declare metadata for external data processors and reports. It maps the processor to a specific kind, such as PrintForm or AdditionalReport, ensuring the system recognizes it within the BSP subsystem.

Adding a print form to a 1C metadata object involves defining the PrintForm kind within the ExternalDataProcessorInfo function. This automatically configures the target object registration and generates the necessary server handler templates for the specified metadata object.

Yes, you can register an external report as an AdditionalReport by automating the ExternalDataProcessorInfo function generation. The process automatically determines the correct Kind and CommandType API methods based on your input, eliminating manual API mapping.

Supported 1C processor kinds for BSP registration include AdditionalDataProcessor, AdditionalReport, ObjectFilling, Report, PrintForm, and RelatedObjectCreation. Each kind maps to specific API methods and conditional sections for target objects.

Registering an ObjectFilling processor in 1C requires adding conditional target object sections within the ExternalDataProcessorInfo function. The system handles these conditional sections automatically, along with generating server handler templates for the specified kind.