Reports are used to store and vizualize the results of a scheduled project. The content, the output format and the appearance of a report can be adjusted with report attributes. Reports can be nested to create structured document trees. As with other properties, the resource attributes can be inherited from the enclosing report or the project.

By default, report definitions do not generate any files. With more complex projects, most report definitions will be used to describe elements of composed reports. If you want to generate a file from this report, you must specify the list of formats that you want to generate. The report name will then be used as a base name to create the file. The suffix will be appended based on the generated format.

Reports have a local name space. All IDs must be unique within the reports that belong to the same enclosing report. To reference a report for inclusion into another report, you need to specify the full report ID. This is composed of the report ID, prefixed by a dot-separated list of all parent report IDs.

An optional ID. If you ever want to reference this property, you must specify your own unique ID. If no ID is specified one will be automatically generated. These IDs may become visible in reports, but may change at any time. You may never rely on automatically generated IDs.

The name of the report. This will be the base name for generated output files. The suffix will depend on the specified formats.It will also be used in navigation bars.