|
RP-2.0 |
Declares that the report template is to be processed by the 2.0 version of the report processor. If not present, the classic report manager (“1.0”) will be used by default. |
|---|---|
|
Application: AppName |
<<Application: AppName>>, where AppName is the application's name, sets the context of the report to a specific application. Subsequent class and filter name references will be scoped to this application. |
|
InsertFormattedTemplate |
Specifies the name of a secondary report template that will be formatted by a completely new Report Processor instance with the results inserted into the primary report. This tag is available only in version 2.0 report processor templates. However, inserted templates use the Classic Report Manager unless the <<RP-2.0>> tag also exists in this template. Named templates are expected to be in the WorkView resource directory, in the “Templates” subdirectory. Example: <<InsertFormattedTemplate: SubReport.tmp>> |
|
TruncateText |
When text attributes are included in a report, this tag can be used to control the maximum amount of text to include. For extremely long blocks of text, it might be desired to only display the first several hundred or thousands of characters. When TruncateText is set to On, values are truncated as if in “Filter Query” mode at 255 characters. Use this for your desired control. <<TruncateText: Off >> <<TruncateText: On >> (sets to the 255 default) <<TruncateText: 5000>> |
|
MaximumResults |
Controls the maximum count of result rows displayed in a pre-formatted HTML Filter Query table. The default is 1000. You may specify a numerical maximum or use OFF to turn this limit off completely. ON returns the setting to the default of 1000. This setting is executed when encountered, so it can be mixed in the overall template text and can turn limits on and off for different template areas. Example: <<MaximumResults: 5000>> <<MaximumResults: off>> <<MaximumResults: ON>> |
|
CondenseWhiteSpace |
The report processor includes all characters between tags as plain text in the report stream. This means that nicely formatted templates that use line feeds and tabs to show good visual structure may end up with unnecessary white space in the final report stream. This is left as-is by default. Including this tag in a template will ask the report processor to attempt to clean some of this white space up before closing the stream. Possible parameters are ON and OFF, OFF is the default. Example: <<CondenseWhiteSpace: On>> |
|
DateMathUnits |
Can be used to set the units used in date math. The default is DAYS, but often it is desirable to use months or years instead. This is an interactive setting and it is possible to change the setting for different template areas. Possible units are: Days, Years, and Months. Example: <<DateMathUnits: Months>> |
|
UseEquationProcessor |
Starting with release 17, the Report Processor SET tags, which assign values to variables, make use of the same EquationProcessor utilized by Triggers and Calculated Attributes. When this option is set to Yes, it allows the use of more complex formulas when setting a pre-declared variable. The option to use the simpler in-line equations is available here to support legacy reports. Values for this option are Yes and No. This option defaults to Yes. Example: <<UseEquationProcessor: No>> |
|
InsertImage |
Accepts an image referenced by URL or server-local path and file name and inserts an HTML base64 version of the image into the output. Some (older) web browsers have problems with embedded images larger that 32k, new browsers are more accommodating. Larger files sizes may cause issues. The first parameter is required and must specify either a file system path or an HTTP-based URL. In the case of a file path, it can be fully qualified but must be a server-accessible path. If no path information for the file is given, the processor will actually look for this file in the WorkView resources directory within the templates sub directory. If a URL is provided, a web request will be used to obtain the image. In either case, the source image is encoded as base64 and inserted into the output stream of the report wrapped in an HTML <img> tag. A second parameter may be specified for this tag that represents a CSS style class name that should be created to represent this image. This tag option must be used in the <header> section of the html template. This allows the single image to be repeated as many times as desired yet with only a single binary image in the output file. Example of an image inserted directly: <<RP-2.0>> <html> <body> <h4>Inline:</h4> <<InsertImage: Logo.png>> </body> </html> Example using a CSS style class name (for images used multiple times in a report): <<RP-2.0>> <html> <head> <<InsertImage: Logo.png, myimageclass>> </head> <body> <h4>As a styled DIV:</h4> <div class="myimageclass"></div> </body> </html> |