Generation of docket files
This Step Plugin allows you to automatically generate docket files in various file formats.
Overview
Name | Wert |
---|---|
Identifier | intranda_step_save_docket_file |
Repository | |
Licence | GPL 2.0 or newer |
Last change | 25.07.2024 11:20:26 |
Introduction
This plugin can be used in any task to automatically generate and save a docket when the task is processed. The plugin supports PDF and TIFF files.
Installation
The following file must be present to install the plugin:
To configure how the plugin should behave, various values can be adjusted in the configuration file. The configuration file is usually located here:
Overview and functionality
In case of an automatic task, the plugin will be executed automatically as soon as the corresponding task is executed. There is an additional button at the corresponding task in the task details, with which the docket can be generated manually at any time.
This plugin can also be integrated into the workflow in such a way that it is executed automatically. Manual interaction with the plugin is not necessary. For use within a work step of the workflow, it should be configured as shown in the screenshot below.
Configuration
Configuration of the plugin
The configuration of the plugin is as follows:
Value | Description |
---|---|
| This parameter specifies for which project the current |
| This parameter defines for which work steps the |
| This element specifies which docket template should be used for generation. The |
| This element specifies where and how the destination file should be stored. The |
| This value specifies the resolution of the exported document. The unit is pixels per inch. The default value is 150 DPI. |
Output file name
The file name of the generated docket file can optionally be specified individually with the following parameters.
Variable | Description |
---|---|
| Inserts the entire associated process title into the file name at this position. |
| Inserts the part after the first underscore ( |
If a process title does not contain an underscore and {process_suffix}
is used anyway, the entire process title will be inserted instead.
Examples:
Value in | Process title | Output file name |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Last updated