> For the complete documentation index, see [llms.txt](https://docs.videc.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.videc.de/acron-9.3/en/anlagenkonfiguration/jobs/auftragsmappe/berichtsauftrag_service.md). # Report job for Service Report job with custom configuration options including time frame or output filters. The report jobs can be moved within the [job folders](/acron-9.3/en/anlagenkonfiguration/jobs/auftragsmappe.md) by [drag & drop](/acron-9.3/en/erklaerung_zur_bedienung.md#drag-drop). ### Name Name of report job ### Active Activated/deactivate the job. Deactivated jobs are not executed. ## General ### Report type Display of report type ### [Report being generated](/acron-9.3/en/kzp_mit_parameter_starten/kzp_jobs.md#login-name) Display of the report to generate ### Output mode Selection of the output mode from * Preview * Print * E-mail * Recipient E-mail address of the recipient of the report job; You can select an already assigned recipient e-mail address from the pick list. You can enter it if it is not yet listed. Note To be able to send reports in an e-mail, an e-mail account with the [sender's e-mail address](/acron-9.3/en/anlagenverwaltung/register-adressen.md#absender) and the [host](/acron-9.3/en/anlagenverwaltung/register-adressen.md#host) must be set up in Plant Management on the 'Address' tab. * Subject / Content E-mail subject and content * Archive Archive path - Input/selection of the path where the report job is to be archived. Note To be able to send reports in an e-mail, an e-mail account with the [sender's e-mail address](/acron-9.3/en/anlagenverwaltung/register-adressen.md#absender) and the [host](/acron-9.3/en/anlagenverwaltung/register-adressen.md#host) must be set up in Plant Management on the 'Address' tab. ### Output format Selection of the output format from * PDF * EMX ### Printer Display/open the dialog to select and configure the printer to be used. In the dialog box you can configure parameters including the paper format and the alignment. The remaining settings depend on the options offered by the selected printer. ### Changing the printer selection before printing Facility to change the selection and configuration of the printer immediately before starting to print. ### Output all entities in a history All entities are generated in a history. ## Time frame ### Length of the report time frame Length of the report time frame ### Unit Unit of length of report time frame ### Time frame end Selection of the time frame end * Now All data up to the current time. * End of hour At 12:31 hours, for example, includes all data up to 13:00 hours. * End of day All data until end of day. * End of month All data until end of month. * End of year All data up to December 31 of the selected year Note For shift reports the time frame end cannot be changed. If a shift goes into the next day, e.g. 22:00 - 6:00, it is displayed correctly. The postponement of the time frame end in this case relates to the day on which the shift begins. ### Time frame end moved back by Number of hours, days, months or years by which the preset time frame for data output is to be moved back.
| | | | ----------------------------- | ------------------------------------- | | Current system time | 8/16/2014 | | Time range | 1 month | | Time frame end = End of month | 8/31/2014 | | Moved back by = 3 | 5/31/2014 (corresponding to 3 months) | The time frame extends from May 1, 2014 to May 31, 2014. When the current date reaches September 1, 2014, the time frame switches from June 1, 2014 - June 30, 2014.
### Unit of time offset Selection of the unit of the time offset ## Filter ### Service main group Selection of a specific main group for output. Display of an active or inactive filter ### Filter conditions for entities All filter condition inputs are *and* linked - additional inputs for Key or selecting an [action](#massnahmenstatus) or [instruction](#anweisungsstatus) status would constrain the result further. Info about the wildcards (placeholders): **\*** stands for any number of characters, or no character. **?** stands for any character. ### Identification Input of a character string or selection of an entity whose identifier is applied as a filter condition. Note The wildcard **\*** automatically added when using the selection option can be removed manually. Note If filter conditions are entered manually, the wildcards **\*** and **?** can be used in any way. They are not added automatically in this case.
| | | | | --------------- | ------------ | -------------------------------------------------------------------------- | | Identification: | \*pumpe\_1? | finds "Wasserpumpe\_1A", "Wasserpumpe\_12", "Umwälzpumpe\_17", etc. | | Identification: | \*pump\_?1\* | finds "Wasserpumpe\_11", "Wasserpumpe\_A12", "Umwälzpumpe\_X1\_UP27", etc. |
### Name Input of a character string or selection of an entity whose name is applied as a filter condition. Note The wildcard **\*** automatically added when using the selection option can be removed manually. Note If filter conditions are entered manually, the wildcards **\*** and **?** can be used in any way. They are not added automatically in this case.
| | | | | --------------- | ------------ | -------------------------------------------------------------------------- | | Identification: | \*pumpe\_1? | finds "Wasserpumpe\_1A", "Wasserpumpe\_12", "Umwälzpumpe\_17", etc. | | Identification: | \*pump\_?1\* | finds "Wasserpumpe\_11", "Wasserpumpe\_A12", "Umwälzpumpe\_X1\_UP27", etc. |
### Key 1/2 Input of a character string as a filter condition for the keys assigned to the entities. Note The wildcards **\*** and **?** can be used in any way. Note If filter conditions are entered manually, the wildcards **\*** and **?** can be used in any way. They are not added automatically in this case.
| | | | | --------------- | ------------ | -------------------------------------------------------------------------- | | Identification: | \*pumpe\_1? | finds "Wasserpumpe\_1A", "Wasserpumpe\_12", "Umwälzpumpe\_17", etc. | | Identification: | \*pump\_?1\* | finds "Wasserpumpe\_11", "Wasserpumpe\_A12", "Umwälzpumpe\_X1\_UP27", etc. |
### Action status Selection of an action status as a filter condition * No active filter * Actions becoming due * Actions performed ### Filter conditions for cyclic actions and associated instructions All filter condition inputs are *and* linked - additional inputs for Key or selecting an [action](#massnahmenstatus) or [instruction](#anweisungsstatus) status would constrain the result further. Info about the wildcards (placeholders): **\*** stands for any number of characters, or no character. **?** stands for any character. ### Identification Input of a character string or selection of an action whose identifier is applied as a filter condition. Note The wildcard **\*** automatically added when using the selection option can be removed manually. Note If filter conditions are entered manually, the wildcards **\*** and **?** can be used in any way. They are not added automatically in this case.
| | | | | --------------- | ------------ | -------------------------------------------------------------------------- | | Identification: | \*pumpe\_1? | finds "Wasserpumpe\_1A", "Wasserpumpe\_12", "Umwälzpumpe\_17", etc. | | Identification: | \*pump\_?1\* | finds "Wasserpumpe\_11", "Wasserpumpe\_A12", "Umwälzpumpe\_X1\_UP27", etc. |
### Name Input of a character string or selection of an action whose name is applied as a filter condition. Note The wildcard **\*** automatically added when using the selection option can be removed manually. Note If filter conditions are entered manually, the wildcards **\*** and **?** can be used in any way. They are not added automatically in this case.
| | | | | --------------- | ------------ | -------------------------------------------------------------------------- | | Identification: | \*pumpe\_1? | finds "Wasserpumpe\_1A", "Wasserpumpe\_12", "Umwälzpumpe\_17", etc. | | Identification: | \*pump\_?1\* | finds "Wasserpumpe\_11", "Wasserpumpe\_A12", "Umwälzpumpe\_X1\_UP27", etc. |
### Key 1/2 Input of a character string as a filter condition for the keys assigned to the actions. Note The wildcards **\*** and **?** can be used in any way. Note If filter conditions are entered manually, the wildcards **\*** and **?** can be used in any way. They are not added automatically in this case.
| | | | | --------------- | ------------ | -------------------------------------------------------------------------- | | Identification: | \*pumpe\_1? | finds "Wasserpumpe\_1A", "Wasserpumpe\_12", "Umwälzpumpe\_17", etc. | | Identification: | \*pump\_?1\* | finds "Wasserpumpe\_11", "Wasserpumpe\_A12", "Umwälzpumpe\_X1\_UP27", etc. |
### Activity status Selection of an activity status as a filter condition. ### Instruction status Selection of an instruction status as a filter condition * No active filter * Instructions output * Instructions not issued ### Sort order of histories Selection from * Sort order as per ACRON Designer configuration The sequence of histories is displayed as they were configured in the ACRON Designer. * Sort order chronological, starting with the oldest data record The sequence of the displayed histories starts with the oldest data record (the activity performed the longest time ago). * Sort order chronological, starting with the newest data record The sequence of the displayed histories starts with the newest data record (the activity performed most recently). ### Sort order of status reports Selection from * Sort order as per ACRON Designer configuration The sequence of the actions in the status report is displayed in the order they were configured in the ACRON Designer. * Sort order chronological, starting with the next due action The order of the displayed entities ends with the entity for which an action is due next. * Sort order chronological, starting with the next due action The order of the displayed entities ends with the entity for which an action is due next.
Selection of an object with the identification *UNIT\_1* produces the search criterion *UNIT\_1\**. In addition to UNIT\_1, this criterion also finds UNIT\_12, UNIT\_13, UNIT\_103 etc, if those objects exist. If a character string for the name is additionally entered, the result is constrained further. Entering *\*pumpe\** restricts the result to those objects whose identification begins with UNIT\_1 *and* whose name contains the character string *pumpe*. If character strings for keys are also entered, the result is further restricted to the objects that also meet that/those key constraint(s). Entering *\*pumpe\_1?* finds "Wasserpumpe\_1A", "Wasserpumpe\_12", "Umwälzpumpe\_17", etc. Entering *\*pumpe\_?1\** finds "Wasserpumpe\_11”, "Wasserpumpe\_A12”, "Umwälzpumpe\_X1\_UP27", etc.
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.videc.de/acron-9.3/en/anlagenkonfiguration/jobs/auftragsmappe/berichtsauftrag_service.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.