Automation Engine
info related to a TIFF output device to one XML for each day (use SmartName
[date]
in the name of the XML file).
In the output field, minimally enter a name (use SmartNames). You can also define or browse to a specific folder to write the XML files into or you can leave this field empty and make the system use the default place for these files as defined in the next configuration item "
Via File
".
•
TXT file
: Same options as for XML files, but now you can also use templates to add custom text.
•
Template
: Templates add custom made texts. Learn more in
Notification Templates
on
page 97.
Note:
The "Templates" list and the "Edit Templates" button are only shown when at least one template was created before.
3.
Click
OK
to confirm and close.
Add more if you want to.
Via File
When setting up a notification rule that creates XML or TXT file, you can choose to not enter any output folder for these files, but only specify their name (learn more
here
). In that case,
these files are written in the default place that you define in these tabs.
•
Tab "Text"
•
Append the message in a Log File
: When you choose to add the notification information to a same file. Browse to change its location and there create/select an empty file.
•
Create a new file per message in a folder
: Define the folder where these notification text files will be created.
•
Tab "XML"
Same as for TEXT files, but you can also choose to include the tasks messages (that appear in the task's "details") and the ticket parameters it used.
Notification Templates
A notification template can add custom text to the notification.
To create, modify or delete templates, click '
Edit Templates...
' in the
Notification Rule Editor
.
Alternatively, go to
Pilot
>
Advanced
>
Edit Notification Templates...
Learn more below in
Edit Notification Templates
.
Edit Notification Templates
Creating a template
1.
Click
Add
.
9
97
9
Automation Engine
2.
The
Add
dialog pops up. Enter a name for the template. Click
OK
.
3.
The
Edit Template
dialog pops up.
It has dedicated fields for
Subject
and
Message
, SmartName enabled.
The field for
Task Information
is best only changed on advise of Esko support. It includes code-based conditional information that can include the attachments you requested while
creating the notification rule
.
Here is an example:
Tip:
You can also
Edit Notification Templates
in the
Configure
tool, provided that you already have templates available: go to
Configure
>
Notification
>
Rules
>
Task/Device
>
Add...
.
9.13.27 Odystar
This configuration is explained in the dedicated section on
Integrating with Odystar (soon outdated)
. Find a direct link
here
.
9.13.28 Proof Servers
This configuration is used to connect the Esko Proof Server which his required for
• the
Proof for Contract Approval
task (part of the Pack Proof product) . Learn more in the
user guide of Pack Proof
, in the page on
Pack Proof Configuration
.
98
Automation Engine
• the
Proof for Content Approval task
task (part of the Imaging Engine product). Learn more in
Imaging Engine Configuration
.
9.13.29 Plate Merger
This item is documented in the chapter
CDI Platemaking Workflow
. Find a direct link
here
.
9.13.30 Preflight Tools
This item serves to link Automation Engine to external preflight server software that you can then use in the
Preflight via External Application
task.
Caution:
In AE v16, the task 'Preflight via External Application' was declared to become
'Soon Outdated'. Learn more about this concept and your alternative in
Concept of
(Soon) Outdated Tasks
.
Note:
When you want to use Enfocus PitStop, consider using the version that is built into
Automation Engine. This is done when you use the task
Preflight with PitStop
.
Important:
• This external preflight server software (for example a separate install of PitStop Server) has to run on your Automation Engine server.
• You must share the folder containing the profiles (for example PitStop's C:\Program
Files\Enfocus\Enfocus PitStop Server 13 ) to be able to access it from the Preflight ticket.
9
Tool Name
: Select one of the supported preflight applications.
Report Language
: Select the language you want the report to be in. For Enfocus PitStop
Server, you can set this in the PitStop Server preferences.
Report Units
: Select the units to be used in the preflight report.
Report Type
: Select the type of report: PDF, XML or both.
Executable File
: Enter (browse to) the path to the preflight application's executable file.
99
9
Automation Engine
Profile Folder
: Enter (browse to) the path to the folder where the default profiles for the selected preflight tool are stored.
Action Folder
: Enter (browse to) the path to the folder where the action lists for the selected preflight tool are stored. The Preflight task will allow you to select multiple actions from this folder.
9.13.31 Printing Methods
Printing Methods
are defined in the Configure tool. You get a list of standard names. You can add custom ones.
You can set an ink to a specific printing method by using the Job setup's
Inks tab
or by using a one of these tasks:
Adjust PDF Screening
,
Extract Inks
,
Normalize PDF File
,
Normalize PostScript /
PDF / Illustrator 8.0 File
,
Optimize PDF Separations
,
Trap with PowerTrapper
,
RIP'ing with Imaging
Engine
.
For example:
100
These are typical examples of how to make use of a
Printing Method
:
