Introduction

...

1. The file name auto-generation logic only affects the basename of the file; extensions are always set to .json for the report metadata file and .html, .csv  and .xlsx for  the different output formats.
2. Please note that any graph files associated with a report are not subject to this naming scheme; those names are completely dynamic and can be determined only by analysing the report metadata file.
3. On-demand reports generated from the GUI allow the user to supply the 'report name', and if that is present then it'll be used for the file names (but subject to de-clashing as outlined below).
   If no report name is supplied, then On-demand reports are treated like scheduled non-recurring/one-off reports.
4. All file names may be amended with a number if a clashing file already exists, e.g. "some_report.3.xlsx" and "some_report.4.xlsx" may be generated.
5. All file names are are adjusted to replace certain characters: all spaces and ":" are replaced by "_".
6. Depending on the report frequency, the following components are used to build the file name:

...