Reports

Appendix F. Report Properties

The following tables show the locations of the properties of nodes in the Report Structure window and of widgets in the layout window; screen properties are also listed. Brief descriptions of the property headings follow the tables.

Note: Unlike screen properties, most report properties are not accessible during runtime.

Report Structure Window

The nodes in the Report Structure window–report, page format, print, detail, and group–have properties with some very different functions from those of the report layout window. These nodes control how information is output in the report.

Identity properties

Identify the node and its inheritance properties, and provide node-specific information including parameters for the report node, the name of the layout area for print nodes, the data source for the detail node, and the break field for the group node.

Composition properties

Control display options, such as page size and orientation, header and footer frequency and display, and the amount of information that appears on each page.

**Table F-1 Nodes**
Nodes	Abbreviation in table
Report	Rep
Page Format	Pag For
Instance	Ins
Detail	Det
Group	Grp
Print	Prn
Call	Call
Subreport	Sub
End Page	EPg

**Table F-2 Structure window: Identity**
Property	Dependencies	Rep	Pag For	Ins	Det	Grp	Prn	Call	Sub	EPg
Identity
Area							·
Break On						·
Bundle Name	Data Source=Receive Bundle				·
Comments		·	·	·	·	·	·	·	·	·
Data Source					·
Default Cursor	Data Source=SQL Query				·
Function Call	Data Source=Custom Function				·			·
Inherit From		·	·	·	·	·	·	·	·	·
Parameters		·
Pre Break Call					·
Name		·	·	·	·	·	·	·	·	·
Receive Widgets	Data Source=Receive Bundle				·
Report Invocation									·
Root	Data Source=TM View				·
Statement	Data Source=SQL Query				·
Use Caller Format									·
Use Caller Groups									·

**Table F-3 Structure window: Composition**
Property	Dependencies	Pag For	Det	Grp	Prn	Sub
Composition
Custom Space	One-Detail Footer=No			·
Floating Footer		·
One-Detail Footer				·
Indent					·	·
Justification					·
Keep on Page				·	·	·
Local Header Only				·
One per Page			·	·
Orientation		·
Page Size		·
Print Break Value				·
Reserve Space						·
Running Header				·
Shrink					·

Widgets

**Table F-4 Widgets**
Property	Dependencies	Dynamic Output	Static Output	Layout Area	Box	Line	Graph	Link
Identity		·	·	·	·	·	·	·
Geometry		·	·	·	·	·	·
Font		·	·	·			·
Validation		·
Format/Display		·	·
Transaction		·						·
Database		·
Composition		·	·
Context	Value=Normal, Copy, History. Total	·
Initialize In	Value=History, Total	·
Placement		·	·
Update In	Value=History, Total	·
Value		·
Value Source	Value=Copy, History, Total	·
Graph							·
XML		·			·

Layout Window

The properties for the report layout screen and widgets are similar to those of the editor screen, but there are differences. Not all properties are available to both.

Widget Properties

In general, the property headings listed here for widgets are common to all widget types; the properties within each heading vary depending on the widget type. Some properties appear only if other property specifications have already been indicated. For example, if the Data Formatting property is set to Date/Time, a System Update property is available. These dependent properties are preceded by -> in the Properties window. In addition, a default setting for a property can vary depending on the widget type; however, if the property is listed in the Properties window, you can change it.

Note: If you have more than one widget type selected, only those properties that apply to all appear in the Properties window.

Identity properties: Identify or change the identity of a selected widget, for example, name, type, source of inheritance (if applicable), label text, initialization state (e.g., active vs. inactive), and memo text (for additional comments and programmatic use).
Geometry properties: Define the size and location of a selected widget. Array and scroll properties are included under Geometry.
Font properties: Assign a font (this overrides a screen-wide or application-wide font specification). This can be a Prolifics font, a GUI-specific font, or an alias font name.
Validation properties: Write, define and identify the functions and events that occur during the widget's validation, that is, when the field receives or loses focus at runtime.
Format/Display properties: Control the way data is formatted and appears to the user, such as date/time and numeric formats, textual justification (positioning), and whether the widget displays a picture instead of text.
Transaction properties: Provide database-specific information as required by the transaction manager to control display attributes and protections based on the kind of transaction being performed.
Database properties: Provide database-specific information used by Panther's SQL generator to construct and generate SQL statements.
Composition properties: Control the placement and source of contents for a widget. You can set the placement of a widget's data to left or right float to close up space between two widgets that are aligned horizontally. You can specify the value as page number, or set the source to another widget to copy the data, collect history data for graphs, or total the data.
Web Options: Provide Web-specific information, including JavaScript and VBScript. If you set Export to HTML to Yes, the widget can be accessed by JavaScript.
Graph properties: Provide graph-specific information for designing a pie chart, bar graph, XY plot, or high/low graph, and are only available to graph widgets.
XML properties: Provide properties to use when generating an XML report.

Report File Properties

The screen of the report file has its own set of properties. You gain access to these properties when a report file screen is selected (no widgets on the screen can be selected).

Identity properties: Identify the screen–like the screen's name and its source of inheritance.
Geometry properties: Define the initial size and state of a screen as well as the height and width of the grid. You can set the height and width of the grid, or you can allow them to be driven by the font chosen for the report. If you change the font, Panther will ask you if you would like the grid to be rescaled. Rescaling will affect widget placement.
Font properties: Assign a font (this overrides the application-wide font specification). This can be a Prolifics font, a GUI-specific font, or an alias font name.
Inclusions: Define JPL procedures or provide the names of other report files that are to be accessible to the report file.
Transaction properties: Define the root table and transaction model used by the transaction manager to carry out its commands at runtime.