More Articles About Reporting
Create Parameter Inputs - To manage report initialization and creation parameters, follow the steps below: 1Press the 'Settings' button at the top of Enterprise Manager. 2Select the Content page in the left panel, and select the Repository tab. 3Click to select the desired report in the tree. 4Select the Parameter tab. Note: Values that you assign to parameters here will also be used for report preview in Style Studio (for reports saved as "repository reports"). 5Press the 'Add' button below the table on the Parameter tab. This opens the 'Add Parameter' panel. 6Select 'Initialization Parameter' or 'Creation Parameter'. Creation parameters are parameters for template-based (.srt) reports. Use these to set default parameter values and bypass the default parameter prompting mechanism (not custom Parameter Sheets). Initialization parameters are used to set global properties at initialization for a manually coded Replet class. Some of these are generic and can be used for all report types. (Report creation parameters can also be set from the Scheduler tab; see Scheduler Actions...
How to Create an Executable Report - Replets are organized in a hierarchical structure in the repository. There can be any number of levels in the tree. The leaf nodes of the tree are replets and non-leaf nodes are folders. A non-leaf node can be empty, in which case it is simply an empty folder (with no reports in it). The tree position of a replet is encoded in the replet name. A replet name is a full path from the root of the tree to the replet leaf node. Each node is separated by a slash '/'. For example, the replet 'Replet2' in a top-level folder, 'Sales', would have the name 'Sales/Replet2'. Whenever a replet is referenced in a Java program or as a URL, the full name must be used. Because the entire tree structure is encoded in the replet full name, changing the name of a replet could have the effect of moving it among the branches of the tree...
Monitoring Report Execution - The 'Reports' page under the 'Monitoring' node provides key information about reports that are currently executing on the server, as well as reports that are awaiting execution, and those that have already been executed. A pending report is a report that the user has requested, but that has not yet been assigned an execution thread (due to natural or designed processing limitations). As soon as the required processing resources become available, the pending report will be generated and immediately displayed to the user. Note that a pending report is different that a queued report...
Summary of the Use of Report Templates - This chapter described the API that influences report templates created by the visual Designer. Report templates can be imported into a Java Program as ReportSheet objects. We also discussed template processing, which concerns binding data to an element on a template; and template execution, which executes scripts and queries bound to elements. Adding table styles, and all other formatting operations, should be performed at the template level using the Report Designer...
What Actions Can Be Executed from InetSoft's Report Scheduler? - InetSoft's Report Scheduler is a feature-rich tool designed to automate various reporting-related tasks, allowing organizations to schedule and manage report generation, distribution, and other actions. While the specific capabilities may vary based on the version and configuration of the software, here are common actions that can typically be executed from InetSoft's Report Scheduler: Report Generation: The primary function of the Report Scheduler is to automatically generate reports based on predefined schedules. Users can configure the scheduler to execute specific reports at regular intervals (e.g., daily, weekly, monthly) or on specific dates and times. Email Delivery: InetSoft's Report Scheduler enables automated email delivery of generated reports to predefined recipients. Users can specify email...