The maintenance route PDF report brings together the basic details of a completed task and the inspection entries for its route targets. You can configure the shared report language, logo, header and footer texts, and styling. The settings apply to maintenance route reports throughout the service, including reports for tasks completed on Android and iOS.

Opening the settings and required permissions

Changing the settings requires local administrator permissions. From the browser's main menu, open Settings, expand PDF settings and click the name of the Maintenance route row.

These settings are separate from the task form PDF report settings and the settings for exporting task details in the browser. Maintenance route report settings are configured in the browser.

Report language

Language at the beginning of the form determines the language of the report's standard texts. The available options are Finnish, English, Swedish, German, Danish and French, as well as System default. If you want reports to always use the same language, select that language explicitly.

System default uses the language passed to report generation from the context in which the task was completed. It does not mean that a saved report changes language according to whoever reads it later. The language selection does not translate task or Spot names, inspection names, comments or header and footer texts you write yourself.

Logo and header and footer texts

Expand Report logo and select Add PDF report logo. Choose a PNG, JPG/JPEG, BMP or GIF image smaller than 25 MB. The logo appears at the top left of the report. To replace an existing logo, select a new image and save. This form has no button for removing a saved logo.

Expand PDF report headers. Header text center and Header text right appear at the top of the page beside the logo. Footer text left, Footer text center and Footer text right appear at the bottom of the page. You can use them for your company's contact details, for example.

Each header or footer text field can contain up to three lines and a total of 255 characters. You can leave the fields empty. To remove an existing text, clear its field and save. The report header also shows the page number and total number of pages.

Report styling

Expand Report styling and select In use to apply your custom styling choices to the report. You can configure the following groups separately:

  • Headers and footers: the font, font size and color of the header and footer texts.
  • Info pane: the font, font size and color of the task's basic details.
  • Sections: the font, font size and color of the route targets and inspection content, and the background color of the inspection areas.

The Font options are Noto Sans, Serif and Courier. Font size is specified in pixels: the available sizes are 10–18 px for headers, footers and the info pane, and 10–15 px for sections. The initial values on a new settings form are Noto Sans, black text, 13 px for headers and footers, and 11 px for the info pane and sections. The initial background color for sections is light gray.

The report uses darker shades of the selected colors for some headings and texts, and for background borders. The person who recorded an inspection entry and the time it was recorded are displayed in smaller text. The selected size or color therefore does not appear exactly the same in every part of the report.

If you clear In use and save, subsequent reports will use the standard styling. This does not remove the logo or header and footer texts or change the report's content. This setting does not include a report preview, email distribution settings, a custom filename or content options for task form reports.

Saving and the effect of changes

Select Save at the bottom of the form. Then reopen the same setting and check the language, logo, header and footer texts, styling values and In use selection. The basic settings and styling are saved separately, so check both, especially if an error appeared while saving.

The maintenance route report is generated in the background when the entire route task reaches its final completed state. The task must have route targets. Completing a single inspection target is not enough. If the task requires review, the report is generated only after approval; a task awaiting review is not sufficient.

The report uses the shared settings saved at the time it is generated. Because generation takes place in the background, a settings change made immediately after completion may still be included in a report that has not yet been generated. Save the desired settings before the task is completed.

Changing the settings does not update PDF files that have already been generated or trigger regeneration of old reports. It also does not change the task's status, inspection entries or information about who recorded them. Opening the report displays the saved file.

Checking the result

Check the layout in the report for the next route task completed normally. From the main menu, open Manage tasks → Tasks → Tasks, open the completed task and select its Maintenance route tab. Click the PDF icon on the left above the route list. The icon appears when the report file is available.

If the icon is missing, first make sure that the entire task has been completed and any required review has been approved. Report generation may take some time; reopen the task after a short wait.

Check the report's language, logo, header and footer texts, and text readability. The report shows the task name, the person who performed it, the task's Spot and completion time, followed by the route targets in order. For each target, it shows the Spot name, the tag number if present, and the inspection names and comments. The inspection entries distinguish between completed, unrecorded and skipped inspections. Completed and skipped entries show who recorded them and when. Completion and recording times are shown in Helsinki time.

Instructions for defining the route content are provided in Defining maintenance route inspection targets, and instructions for recording entries are provided in Performing a maintenance route on mobile.