Privacy Policy | Imprint | Prinect Know How | Prinect Release Notes "Create Versions with Page Lists" Window You can open this window by selecting "Create versions with page lists" from the context menu in a page list. This window allows you to output versioned jobs. In addition to the base elements, which are the same in all versions, versioned jobs contain versioned parts, which differ, for example, by different languages. This means that you can, for example, output jobs that are to be output in several languages in a "versioned" manner. In this case, the pages that are language-dependent are assigned to a version, while pages that are the same for all languages – e.g. images – are assigned to the language-independent base elements. With versioned output, it is not necessary to create a separate print job for each language version and to process the entire page content from prepress, but rather the base elements only have to be processed once (color management, rendering, etc.). The language-dependent versioned subjobs are processed separately. Finally, the processed pages of the base and version components are merged and printed by version. Dividing the data into base and version components can significantly reduce processing time and the amount of data processed. Versions can be defined for complete print jobs as well as separately for cover and content pages. Versioned jobs can be defined both within the Prinect Production workflow (including Prinect Signa Station) and in a connected management information system (MIS) – e.g. in Prinect Business – or in apps of the HEIDELBERG customer portal. In versioned jobs, the terms "version", "layer" and "level" have the following meaning: •Version In newer Prinect versioning workflows, "Versions" represent the top hierarchy level of versioning. Versions can contain layers and these can in turn contain levels. •Layer In older Prinect versioning workflows, the different versions are represented by "layers". There are no "versions" there. In newer Prinect versioning workflows, the layers are located below the "Versions". For example, if multiple layers are defined in a PDF document, individual layers that contain a particular language can be printed in the associated language version, while other layers that contain other languages are not printed (hidden) in that version. •Level In the context of versioning jobs, the definition of levels enables differentiated marking of a layer, e.g. in the form of base or text layers. Example for a multilingual document (4 Versions, 5 layers, 2 levels): Version Layer Level German Images Basic German Text English Images Basic English Text French Images Basic French Text Spanish Images Basic Spanish Text In this example, the layers of the "Images" type or the levels of the "Base" type are identical for all versions. You can add or remove them from the active table with the shortcuts "Command + Plus" or "Command + Minus". Press the Tab key to move to the next cell. Click on the "+" button to create a new version. You can change the default name. Click on the "–" button to delete the activated version. The version marked as activated (dot in the option circle) is the master version. If you want to make another version the master version, activate the desired version by clicking on the option circle. In the "Description" box, you can enter a description of the version you have created. Enter the page number of the relevant version in the "Pages" field. Delete the selected version by clicking on the "-" button. "Changed level names as default" option You can change the level names at a later time. If you enable this option, the last level names to be changed will be entered as the default. "Define a second master version" option If there are several versions with the same page list length (number of pages), you can define a second master version. Versions belonging together are highlighted in color in the "Cluster" column. In this way, you can create a maximum of two master versions with identical page list lengths. You can also define more versions with different page list lengths. In this case, each version can have two master versions in turn if they have identical page list lengths. Click the "+" button to create a new level. You can change the default name. Click the "–" button to delete the enabled level. Use the "up" or "down" buttons to move the selected line up or down. Layers Use the "+" button to create a new layer. You can change the default name in the "Page list" box. Click on the "–" button to delete the activated layer. You can use the filter function to filter by the criterion "Version". The version names are displayed under "Versions". The level names are displayed under "Level". The identifier of the respective product part is displayed under "Product part name", e.g. "End product". "Default names for versioning layers" option At the Prinect Signa Station, you can define default names for versioning layers. You can save these default names in Cockpit. When versioned layouts are created with the Prinect Signa Station, which is started interactively from the Cockpit, versions, page lists and layers defined in the Cockpit can be used in the Prinect Signa Station. In the Cockpit, the default names for layers are: "Image" and "Text". If this option is enabled and a layer name is then changed in the current job, the same name will be used again as the default name in the next job.
Privacy Policy | Imprint | Prinect Know How | Prinect Release Notes
Prerequisite: You can only open this window in versioned jobs. In addition, you must activate the "Page lists" view or the "Show page list assignment" view. See Changing views.
Note: The first level is always the base.
Note: The names of renamed levels are entered as the default for new levels added.
Note: When you confirm the "Create Versions with Page Lists" window with "OK", "Black" is automatically set to "Output (every version)".
Note: The setting for assigning default names for versioning layers is only effective for the logged-in user and only in the current Cockpit, i.e. each Cockpit user must individually redefine these default names if necessary.