The Reports enables users to generate PDF and text reports, interact with XML and JSON files, consume web services, and provide data to external applications. The intuitive configuration workflow simplifies the process of creating report forms, saving and visualizing reports, and generating WebData definitions.
In addition to promoting data exchange between systems by allowing users to publish and consume WebData objects, the Reports module also supports runtime execution, integration with PDF viewers and web services, and customizable advanced features. This page includes a dedicated section on troubleshooting and best practices for the Reports module, covering common issues, solutions, recommendations, and dataset report runtime attributes.
On this page:
The Reports module's purpose is to provide resources for data-driven decision-making. The concepts in the following ease the Reports module understanding:
Report Forms are Rich Text documents that can be saved to disk or visualized in displays. The content can include real-time tag values, tables, and symbols. These forms can be saved as Text or PDF files.
Web Data encapsulates everything needed to exchange JSON, XML, or HTML data with other applications or save its contents to a file. Web Data objects can also be used in displays, enabling interaction with web services and REST APIs.
This module gathers data from several sources and levels coming from different locations. This data is organized and transformed from these data into relevant information, providing a valuable resource for the decision-making process.
Reports module configuration workflow | |
---|---|
Action | Where |
Create Report Forms | Reports → Forms |
Manage WebData Definitions | Reports → WebData |
Customize Report Forms | Reports → Forms Editor |
Manage WebData scripts | Reports → WebData Code Editor |
You create text, formatting, and values using the text editor. To create or edit a report:
Report Configuration Properties | |
---|---|
Field | Description |
Name | Enter a name for the report. The system allows you to know if the name is not valid. |
Padding | Select padding when replacing a tag name with its value (the field for a tag will have the same number of spaces as the tag name is long).
|
SaveFormat | Select the report format:
|
SaveFileName | Enter a string and {ObjectProperties}. Use the full path. |
SaveTrigger | Enter an object property that will be the trigger. |
Append | Enter the file to append the report |
Size | Report size configuration. |
EditSecurity | Check what user groups can edit the report |
Header | Choose another report to be the Header. |
Footer | Choose another report to be the Footer. |
Legacy | Read-only. Show if the report is a legacy. |
Description | Enter a description of this report. |
To change the report format between “portrait” and “landscape”, you need to change it in both NovaPDF (printer used by our Platform ) and the target printer. |
In the Forms Editor, you can design your form layout by dragging and dropping UI components (e.g., text boxes, drop-down lists, charts) from the toolbox onto the form canvas, and configure the properties of each UI component, such as data binding, appearance, and behavior.
To use the text editor:
Check Forms Editor and Dynamic Cell Colors in Reports for additional information.
Report Configuration Properties | |
---|---|
Field | Description |
Name | Provide a unique name for your Web Data entry. |
Encoding | Select the appropriate encoding for the data exchange. |
DefaultURL | Enter the default URL for the data source. |
Authorization | Configure any required authorization settings. |
Headers | Specify any additional headers needed for the data request. |
SaveFileName | Define the file name for saving the data. |
Length | ------------------------ |
TemplateID | Associate a template ID with the Web Data entry. |
Description | Add an optional description for the Web Data entry. |
In the Web Data Editor, you can create, modify, or delete data entries according to your project requirements.
Check the WebAccess REST API page for additional information.
The Reports Monitor allows you to manage and control report entries, providing an overview of the status and results of each report.
Report Configuration Properties | |
---|---|
Field | Description |
Name | The unique name of the report entry. |
Disable | A checkbox to enable or disable the report entry. |
SavedFileName | The file name of the saved report data. |
LastStatus | The last status of the report entry, such as "Success," "Running," or "Error." |
LastStatusMessage | A message providing additional information about the report entry's last status. |
Manage individual report entries using the "Play," "Pause," and "Stop" buttons located above the spreadsheet. These buttons allow you to manually start, pause, or stop report execution.
Review the status of each report entry to ensure successful execution and identify any issues that may require attention.
By utilizing the Reports Monitor, you can keep track of report execution and quickly identify and address any issues that may arise, ensuring smooth operation and accurate data presentation.
The Report module may encounter some issues in its operation. Here are some common issues and their troubleshooting:
Solution
To ensure the smooth operation of the Report module, follow these best practices:
Recommendations
The Report namespace exposes properties and methods of the .NET objects used by the Dataset Module execution. For more information on namespaces and objects, go to Objects and Namespaces.
This section describes only some commonly used properties, for the full list properties and methods, go to the Namespaces Reference.
Report Module Properties examples | ||
---|---|---|
Property | Type | Description |
T.Modules.Report | RunObj | Class for Report operation. |
ReportItem.Append | int | Indicates whether the report will be overwritten or appended on Save commands |
ReportItem.Category | string | ReadOnly property with categories configured on Report object. |
In this section: