Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| 2500_config_apps:4200_report_designer [2026/08/13 00:55] – ↷ Page moved from docs:2500_config_apps:4200_report_designer to 2500_config_apps:4200_report_designer localdev | 2500_config_apps:4200_report_designer [2026/08/13 07:33] (current) – Imported by DokuWiki Advanced Plugin aware_support3 | ||
|---|---|---|---|
| Line 2: | Line 2: | ||
| ====== Working with the Report Designer ====== | ====== Working with the Report Designer ====== | ||
| - | The Report Designer is used to create a layout of document templates of the Report type (or simply reports – see [[docs:2500_config_apps: | + | The Report Designer is used to create a layout of document templates of the Report type (or simply reports – see [[2500_config_apps: |
| {{ : | {{ : | ||
| Line 8: | Line 8: | ||
| The working area consists of the Design Area (shown as the white rectangle), the left menu and the Report Designer toolbar. There are also optional horizontal and vertical rulers. | The working area consists of the Design Area (shown as the white rectangle), the left menu and the Report Designer toolbar. There are also optional horizontal and vertical rulers. | ||
| - | The Design Area is broken into several sections or //bands// (they are shown as blue lines running across the Design Area). Each band has a special meaning and is processed in its own manner when the report is filled out with data at run time. Bands are explained in more detail in [[docs:2500_config_apps: | + | The Design Area is broken into several sections or //bands// (they are shown as blue lines running across the Design Area). Each band has a special meaning and is processed in its own manner when the report is filled out with data at run time. Bands are explained in more detail in [[2500_config_apps: |
| Reports are filled out with data at run time when the documents are generated from document templates (see [[2000_concepts: | Reports are filled out with data at run time when the documents are generated from document templates (see [[2000_concepts: | ||
| - While it is entirely possible and sometimes desirable to overlap different elements if your output is PDF, it is not recommended to overlap elements in HTML output – if you do only one of the overlapping elements will be shown. | - While it is entirely possible and sometimes desirable to overlap different elements if your output is PDF, it is not recommended to overlap elements in HTML output – if you do only one of the overlapping elements will be shown. | ||
| - | - The PDF format only uses a handful of default fonts – if you want to use a different font it has to be imported as a custom font (see [[docs:2500_config_apps: | + | - The PDF format only uses a handful of default fonts – if you want to use a different font it has to be imported as a custom font (see [[2500_config_apps: |
| It is worth repeating the first difference as a caution because it may severely impact how a report designated for HTML output is created: | It is worth repeating the first difference as a caution because it may severely impact how a report designated for HTML output is created: | ||
| - | <callout | + | <alert type=" |
| + | **warning** | ||
| + | |||
| + | When designing reports for HTML output make sure that elements of the report do not overlap (this applies even to lines – make sure that they do not intersect or start/end at the same point). If they do, only one of the overlapping elements will be shown.</alert> | ||
| See also: | See also: | ||
| - | {{simplenavi> | + | {{simplenavi> |