Versioning Settings
You can access these settings:
•When creating (see
“Managing Parameter Sets”). Here, you will see a ‘Lock in Production Plan’ check box (selected by default). If this check box is selected, the settings will be initially locked in the Settings pane. If this check box is deselected, the settings can be edited in the Settings pane.
•In the Settings pane, in the Plan tab of the Job Manager and the Ticket Editor. The settings may be initially locked, as indicated by the Lock icon. If you edit the job, you can unlock them as described in
“Settings Pane (Ticket Editor)”.
When you create a Parameter Set, you should specify a Parameter Set name. You can always change this name later by editing the job, choosing the Parameter Set from the Task Processor in the Plan tab, and unlocking the settings in the Settings pane.
The Versioning Task Processor settings are divided into four tabs:
•Run List: Allows you to specify how pages are input into the Run List.
•Versions: Allows you to define one or more versions within the job; includes the Create Versions assistant.
•Page Assembly: This is where you specify how Apogee should combine the different documents and specified layers within the job.
•Plates: This is where you specify the optimal sets of plates that you want to output.
Name
The name of the Parameter Set as it will appear in the Production Plan. When you create a Parameter Set, you should specify a Parameter Set name. You can always change this name later by editing the job, choosing the Parameter Set from the Task Processor in the Plan tab, and unlocking the settings in the Settings pane.
Run List
Here, you can specify the number of pages and number of the first page, and the page placement/adjustment and revision options.
Number of pages
The number of pages determines the size of the Run List (i.e., the number of pages in the job). More precisely, this is the number of available placeholders for the pages that you want to process.
First page starts at
The page number of the first page in the Run List. In most cases, this is ‘1’.
You could for instance change the page number of the first page when you only have to print a subset of a magazine or a book.
NOTE: This option only affects the page numbers in the Run List and the page placement rules. It does not affect how the pages are handled by the Imposition Task Processor. The first page position is always treated as page 1 in the imposition engine, no matter what the number is.
Page Adjustments
If you select one of these options or both of them, the job will automatically add Page Imposition Adjustments (PIA) to every Run List page of each job it creates. You can edit any resulting page adjustments individually.
Center pages
Ensures that by default, each page has a page adjustment set to center the page. You can edit the settings, but clearing returns it to the default centering action.
Scale pages to fit
Scales the page proportionally in order to fit either the width or the height, depending on which dimension needs the least amount of zoom factor. This adds also a check box with Retain original aspect ratio to every placeholder in the Run List.
For a summary of the page adjustment icons, refer to
“Page Store / Run List Icons”.
NOTE: You should use the center option in the output device Image operation to center a page on the output size.
from old below:
Page Adjustments
Center pages with page adjustments
If you select this option, the job will automatically add Page Imposition Adjustments (PIA) to every Run List page of each job it creates. You can edit any resulting page adjustments individually.
For a summary of the page adjustment icons, refer to
“Page Store / Run List Icons”.
NOTE: You should use the center option in the output device Image operation to center a page on the output size.
from old above:
Automatic Page Placement
These settings are only displayed when you choose to place pages in the Run List automatically. Versioning jobs always have a fixed number of pages.
Place pages automatically
If you choose this option Apogee will check documents as they arrive in the Page Store, and will attempt to place them in the Run List according to the file and layer name information you provide in the Page Assembly tab.
NOTE: Automatic page placement will not work for pages coming from a
Public Page Store.
NOTE: A document cannot be placed in the Run List if the Run List position is already occupied by a document with a different name.
Position Conflict: If a new document would occupy a run list position already occupied by a document with a different name
•Update the run list: Replaces the previous version in the Run List by the newer one, and starts reprocessing. This option is available for both automatic and manual page placement. The Page Store and Run List display a revision number after each document. The initial document has no revision number. Later revisions are numbered in order of arrival (or creation), starting with [1].
•Update the run list only when pages are not approved in WebApproval: Does the same as the previous option if the pages have not yet been approved in the WebApproval application. Pages are not replaced if they have already been approved.
•Do not update the run list: The previous version in the Run List is not automatically replaced: However, you can replace it manually.
•Notify: The previous version in the Run List is not automatically replaced: Instead Apogee sends a notification allowing you to decide what to do. All processing on results that use pages from the previous revision of the document are put on hold until you respond to the notification.
Revisions
These options determine how Apogee will deal with documents that are input with the same name as documents that are already in the Page Store. These are often newer versions (revisions) of the same document.
When the run list already contains a previous revision
•Update the run list: Replaces the previous version in the Run List by the newer one, and starts reprocessing. This option is available for both automatic and manual page placement. The Page Store and Run List display a revision number after each document. The initial document has no revision number. Later revisions are numbered in order of arrival (or creation), starting with [1].
•Do not update the run list: The previous version in the Run List is not automatically replaced: However, you can replace it manually.
•Notify: The previous version in the Run List is not automatically replaced: Instead Apogee sends a notification allowing you to decide what to do. All processing on results that use pages from the previous revision of the document are put on hold until you respond to the notification.
When the run list does not contain a previous revision
•Do not notify: Apogee does nothing.
•Notify: Apogee sends a notification informing you that a new revision has arrived. When you receive a new revision notification, you can choose to update the Run List to use the new document(s), ignore it and keep the previous one(s), or open the job for editing. This last option allows you to inspect the document and selectively replace pages. For more information, refer to
“Message Board”.
Versions
This is where you specify the different output variations a job will produce by means of a versions table. You populate this table with versions (rows), the version elements on which they depend (columns), and the version element variations (cells) which are used to help select the right content combination for each version.
#
Each version is automatically assigned a specific version number (V1, V2, etc.) and color code for easy identification.
Version
You can enter a name for each version you create (e.g. French, German, Italian). These names must be unique. Each version has its own set of pages and output. A versioning job must always have at least one version.
Version Element
You can add one or more version “elements” to add extra dimensions to your versioning job. Typically you would do this if you wanted to add extra categories for your incoming documents (to be able to include or exclude specific subsets of data in each version.
Copy Count
You can add one or more version “elements” to add extra dimensions to your versioning job. Typically you would do this if you wanted to add extra categories for your incoming documents (to be able to include or exclude specific subsets of data in each version.
Version Management buttons
You can enter the number of copies for each version.
Add
Click this button to add a new version. New versions are automatically assigned different colors and version numbers. You can rename them as required.
Duplicate
Click this button to duplicate the selected version. The duplicated version is automatically assigned a different color and version number, and you can rename it as required. The Elements values are also copied.
Delete
Click this button to delete the selected version. You are asked to confirm this action, since deleting a version will also delete any associated
Plates data.
Move up / Move down
Click this button to reposition the selected version within the Versions list.
Auto-fill
Click this cogwheel to automatically fill the version table either with the names of the PDF layers or the names of the documents in the Page Store. There are 2 options:
•Auto-fill with PDF layers
•Auto-fill with directory names
NOTE: This does not remove existing entries, nor change them. It only adds entries for those PDF layers or folder names that are not yet present in the table. If you have an existing setup and you want to start afresh, you should first delete the existing entries.
Create Versions button
When using the Versioning Task Processor in a production plan, you can click this button to open the Create Versions assistant. You can also use the Create Versions assistant when working in the Pages tab. See
“Create Versions Assistant in the Page Store”.
Version Element Management buttons
These work the same as the Version Management buttons.
Page Assembly
This is where you specify the layers that Apogee should use to assemble version pages together with name-matching rules to help populate the layout.
For each version, Apogee must produce a run of version pages. While the content of a version page is specific to its version, it will likely have elements in common with pages from other versions. Unlike in a conventional job where pages are delivered to the job ready-made in their final form, Apogee will combine separate ingredients to make version pages for you, such that common and version specific elements can be taken from a variety of sources.
The Page Assembly tab allows you to specify how many items of content are to be combined, by means of page assembly layers, each of which can hold a page or a PDF layer from a page. When the content in each assembly layer has become known and available, Apogee will combine the layers in order into a single version page, that is, with the first layer rearmost and the last layer foremost.
Name
The name of the Run List Layer. Each layer is equivalent to one or more columns in the Run List.
Range
The range of pages in the Run List to which the current layer is applied. By default, this is all pages (1-$). You can specify ranges in the same way as you do for the Discard Action (see
“Discard Settings”).
Depends on
Choose the version elements that a layer depends on. A layer that does not depend on any version elements will produce one column in the Run List, and its contents will be assembled into all versions. A layer that depends on one version element will produce one column per variation used in the versions table.
PDF Layers
The naming convention for the PDF layer.
Layers buttons
A group of buttons is provided to manage your layers:
Add
Click this button to add a new layer and default range.
Duplicate
Click this button to duplicate the selected layer.
Delete
Click this button to delete the selected layer. You are asked to confirm this action, since deleting a layer will also delete any positioned Run List files.
Move up / Move down
Click this button to reposition the selected layer within the list.
Layer
Name
Enter or change the layer name.
Depends on:
Apogee displays one check box for each version element column in the version table. By checking one of these boxes, you are declaring that the layer will vary according to the variations in the corresponding column in the versions table. The Run List column corresponding to this layer will in turn be split into a group of columns - one for each variation that you see in the versions table for the version elements you selected.
Run List
Range
Enter the range of pages in the Run List to which the current layer should be applied. You can use variables in this field (e.g. 1-$).
File Selection
Allows you to enter a pattern to match files by name.
Variable button
allows you to include version elements and system variables in your patterns. Include a version element in your pattern if you have already checked ‘Depends On’ for that element. Apogee will then direct matched files to be used in the appropriate layer variation.
<RLPAGE> position Absolute in Run List
Specifies an absolute position in the Run List with reference to the specified range.
<RLPAGE> position Relative to RL Page
Specifies a relative position in the Run List with reference to the specified range.
Content Selection
PDF Layers
Allows you to specify a pattern to match PDF layers by name. Include a version element in your pattern to pick the PDF layer and place that matches the particular variation used by a version.
Plates
This is where you can define and fine-tune your output - the plate set.
Plate-sharing is a well-established procedure when producing multiple versions of output. Significant savings are made by keeping plates on the press that do not differ between two consecutive versions of output, as well as providing the certainty that the reused plates are already proofed.
In the Plates tab you can declare which plates will be used to produce which versions. Apogee then knows which image data to combine to give you accurate proofs of each version. This is something that is not possible when using conventional jobs to produce versions. Furthermore, you can adjust the plate setup in response to any problems arising during processing, such as plates that are held up by problem pages.
By default, Apogee prints the first version in full CMYK, and the remaining versions print in K only.
Version Selection list
Each version is automatically assigned a specific version number (V1, V2, etc.) and color code for easy identification. Here, you can select a specific version, in order to display only the plates that contribute to this version. You can also select all versions.
Plates cogwheel
Group Plates check box
This option allows you to ungroup the plates. By default the C, M and Y plates are grouped together for easy management, but there may be situations where you want different settings (e.g., cyan + black). When selected, each plate is allocated its own on/off button and version selector. Note that grouping always keeps the K plate separate and groups the remainder of the process colors as a single set, regardless of the color model. Spot colors always have their own individual setup.
Edit Press Sheet Versions
Signature table
Signature
Indicates the signature number.
Version
Indicates the Version number and name.
Front
Indicates the front side of the signature.
Back
Indicates the back side of the signature.
All
Click this button to select all plates (CMY and K) for printing.
K Only
Click this button to select only the black (K) plates for printing.
None
Click this button to deselect all plates for printing.
Restore to Default
Click this button to restore the default settings for printing (i.e. first version prints in full CMYK, and the remaining versions print in K only).
Plate Count
Indicates the number of plates that will be printed for each version.
Plate colors
Dark gray-colored plates
These plates will be output for printing.
White-colored plates
These plates will not be output, but they can be used for .
Spot colors
You will see a separate column for each kept spot color used in the job.