The REPORT operator enables the generation of a PDF document based on data processed on the input data bus. While processing data bus records, the operator generates one or more reports in a predefined format, consistent with the definition created in the 
Report Editor tool.
With this operator, you can:
- create automated statements, reports, and documents containing data from the processing workflow,
- precisely define the appearance of the PDF document, including layout, tables, text, and images,
- embed data from data bus bits in specific locations within the report according to the configuration.
The operator is often used as a process stage, enabling the generation of clear, distribution-ready documents based on input data.
An example of a project using the REPORT operator:
OPERATOR CONFIGURATION
To configure the report, launch the Report Editor by clicking the Show designer button on the Definition tab.
After completing the configuration, you can preview the operator’s output data bus on the Busbar details tab.
The report is attached to the output data bus as the following bits:
report_name→ a Text bit storing the generated report name.report_binary→ a blob bit containing the binary PDF report data, which you can process further in the workflow—for example, save it as a file on disk or FTP, or send it encoded in base64 using Automatic Invocation via REST API.
The number of bits and records on the input data bus may differ from the number of bits and records on the output data bus. When configuring the report, you decide which fields define the generated document (document fields), and these fields—together with the report_binary and report_name fields—will constitute the bits of the operator’s output data bus. The number of records on the output data bus will result from grouping the data by the document-defining fields.
After making any changes to the report, you will need to regenerate the output data bus bits.