Esko Automation Engine User Guide

PDF

Документ

Automation Engine

User Guide

Automation Engine

1. About Automation Engine........................................................................................................................................................6

1.1 Copyright Notice................................................................................................................................................................6

1.2 Getting Help.........................................................................................................................................................................8

2. What is Automation Engine.................................................................................................................................................... 9

2.1 The Automation Engine Pilot......................................................................................................................................11

2.1.1 The Pilot's Main Window................................................................................................................................ 11

2.1.2 Views....................................................................................................................................................................... 12

2.2 Data Management in Automation Engine............................................................................................................. 14

2.2.1 Containers............................................................................................................................................................. 14

2.2.2 Jobs......................................................................................................................................................................... 14

2.3 Files Processing in Automation Engine..................................................................................................................15

2.3.1 Tasks........................................................................................................................................................................15

2.3.2 Task Chains.......................................................................................................................................................... 16

2.3.3 Workflows.............................................................................................................................................................. 16

2.3.4 Tickets.....................................................................................................................................................................17

3. Getting Started with Automation Engine........................................................................................................................19

3.1 Starting Automation Engine........................................................................................................................................19

3.1.1 Starting the Automation Engine Server.....................................................................................................19

3.1.2 Starting the Pilot.................................................................................................................................................20

3.2 Performing Basic Configuration................................................................................................................................ 21

3.2.1 Creating Users.....................................................................................................................................................21

3.2.2 Defining User Access Rights.........................................................................................................................21

3.2.3 Configuring Output Devices...........................................................................................................................23

3.3 Uploading Files using the Pilot................................................................................................................................. 25

3.4 Launching a Task on a File.........................................................................................................................................26

3.5 Checking the Status of the Task.............................................................................................................................. 27

3.6 Checking the Result in the Viewer...........................................................................................................................28

3.7 Relaunching the Task.................................................................................................................................................... 29

3.8 Generating Output.......................................................................................................................................................... 29

4. Server Administration.............................................................................................................................................................. 30

4.1 Starting and stopping the server..............................................................................................................................30

4.2 Setting up the server.....................................................................................................................................................31

4.3 Backing up the server...................................................................................................................................................31

4.4 Restoring the server...................................................................................................................................................... 32

4.5 Managing databases..................................................................................................................................................... 32

4.6 Managing SQL servers................................................................................................................................................. 35

4.7 Managing application servers.................................................................................................................................... 35

Contents

5. Uploading Files to Automation Engine............................................................................................................................37

5.1 Uploading Files using the Pilot................................................................................................................................. 37

5.2 Uploading Files from a FTP Server......................................................................................................................... 37

5.3 Using Hot Folders to Upload and Process Files................................................................................................38

5.3.1 About Hot Folders............................................................................................................................................. 39

5.3.2 Creating a Task Hot Folder............................................................................................................................ 39

5.3.3 Modifying Hot Folder Settings......................................................................................................................47

5.3.4 Updating Your Task Hot Folders..................................................................................................................47

5.4 Using Shuttle to Upload and Process Files......................................................................................................... 49

5.4.1 What is Shuttle?................................................................................................................................................. 49

5.4.2 Shuttle Setup....................................................................................................................................................... 49

5.4.3 Launching Files from Shuttle Standalone.................................................................................................55

5.4.4 Launching Files from ArtPro.......................................................................................................................... 57

5.4.5 Launching Files from PackEdge or Plato................................................................................................. 61

5.4.6 Launching Files from FastImpose............................................................................................................... 62

5.4.7 Launching Files from Neo...............................................................................................................................64

5.4.8 Launching Files from the Shuttle Plug-in................................................................................................. 64

6. Running Tasks on Files.......................................................................................................................................................... 67

6.1 Creating a Task Ticket.................................................................................................................................................. 67

6.1.1 Creating a Custom Ticket from the Tickets View..................................................................................67

6.1.2 Creating a Custom Ticket when Working with Files.............................................................................67

6.1.3 Using Public Parameters.................................................................................................................................69

6.1.4 Using SmartNames............................................................................................................................................77

6.2 Launching a Task on a File.........................................................................................................................................79

6.3 Checking the Status of the Task.............................................................................................................................. 82

6.4 Relaunching the Task.................................................................................................................................................... 83

7. Running Workflows on Files................................................................................................................................................ 84

7.1 Building Workflows.........................................................................................................................................................84

7.1.1 Building a Workflow from Zero.....................................................................................................................84

7.1.2 Building a Workflow using Custom Tickets.............................................................................................88

7.1.3 Reusing a Task Chain Ticket to Build a Workflow................................................................................ 89

7.1.4 Nested Workflows.............................................................................................................................................. 93

7.1.5 Using Routing in Your Workflow................................................................................................................100

7.1.6 Using Public Parameters.............................................................................................................................. 109

7.1.7 Adding Sticky Notes to Your Workflow...................................................................................................118

7.1.8 Checking All the Workflow's Parameters............................................................................................... 119

7.2 Using Workflows........................................................................................................................................................... 120

7.2.1 Launching a Workflow on a File................................................................................................................ 120

7.2.2 Building a Workflow and Launching it on a File on the Fly.............................................................122

7.2.3 Pausing or Cancelling Your Workflow..................................................................................................... 123

7.3 Checking the Workflow's Processing Status.....................................................................................................124

7.4 Re-launching Your Workflow with Different Settings......................................................................................126

iii

Automation Engine

8. Viewing Files in the Automation Engine Viewer....................................................................................................... 127

8.1 About the Viewer.......................................................................................................................................................... 127

8.2 Checking the Result in the Viewer........................................................................................................................ 128

8.3 Comparing Files............................................................................................................................................................ 128

9. Integration with Other Applications................................................................................................................................131

9.1 Integration with WebCenter......................................................................................................................................131

9.1.1 WebCenter Setup.............................................................................................................................................131

9.1.2 Automation Engine Setup.............................................................................................................................135

9.1.3 Sending an Imposition from Automation Engine to WebCenter....................................................137

9.1.4 Approving the Imposition in WebCenter.................................................................................................141

9.1.5 Checking the Approval Results in Automation Engine..................................................................... 146

9.1.6 Overruling the WebCenter Approval.........................................................................................................150

9.2 Integration with Nexus............................................................................................................................................... 151

9.2.1 Setup on the Nexus Side.............................................................................................................................152

9.2.2 Setup on the Automation Engine Side....................................................................................................153

9.2.3 Running a Nexus Workflow from the Pilot.............................................................................................153

9.3 Integration with Odystar............................................................................................................................................ 155

9.3.1 Setup on the Odystar Side..........................................................................................................................156

9.3.2 Setup on the Automation Engine Side....................................................................................................159

9.3.3 Running an Odystar Workflow from the Pilot.......................................................................................160

9.4 Integration with i-cut Suite....................................................................................................................................... 162

9.4.1 i-cut Automate Workflow.............................................................................................................................. 162

9.5 Integration with Enfocus PitStop........................................................................................................................... 163

9.6 Integration with third party applications using Hot Folders.........................................................................164

9.7 Integration with MIS Systems................................................................................................................................. 166

9.7.1 About JDF and MIS Integration.................................................................................................................166

10. PDF Normalization in Automation Engine.................................................................................................................169

10.1 What Makes a Normalized PDF Special?........................................................................................................ 169

10.2 Which Tasks Require PDF Normalization?...................................................................................................... 170

10.3 How do PDF Tasks Work with Normalized PDF Files?...............................................................................171

10.4 How Do Normalized PDF Tasks Work With Regular PDF Files?............................................................. 172

10.5 PDF Normalization and Step and Repeat........................................................................................................174

11. Scripting....................................................................................................................................................................................177

11.1 Automation Engine Script Runner.......................................................................................................................177

11.2 Getting Started with Scripting.............................................................................................................................. 178

11.3 Use case: Scripting...................................................................................................................................................180

12. Integrating with Third Party Impositioning Systems............................................................................................ 183

12.1 Workflows: The bigger picture..............................................................................................................................183

12.2 Importing and Creating Impositions................................................................................................................... 183

12.3 Exporting Impositions...............................................................................................................................................184

12.4 Workflows with Selection and the Convert Selection tasks......................................................................185

Contents

13. Use Case: Setting up a Packaging Workflow......................................................................................................... 186

13.1 Build a Workflow........................................................................................................................................................ 186

13.1.1 Preflight your file............................................................................................................................................186

13.1.2 Normalize your File.......................................................................................................................................190

13.1.3 Trap your file................................................................................................................................................... 190

13.1.4 View your file...................................................................................................................................................192

13.1.5 Generate Step & Repeat............................................................................................................................ 193

13.1.6 Create Report................................................................................................................................................. 194

13.2 Use Shuttle in the Workflow..................................................................................................................................196

13.2.1 What is Shuttle...............................................................................................................................................196

13.2.2 What are Public Parameters.....................................................................................................................196

13.2.3 Making Your Tickets Public.......................................................................................................................196

13.2.4 Using Public Parameters............................................................................................................................197

13.2.5 Public Parameters in Sample Workflow: Packaging........................................................................204

13.2.6 Launching Files into a Workflow............................................................................................................. 205 v

Automation Engine

1. About Automation Engine

Maximizing Productivity

Automation Engine doesn't only enable you to keep track of your files throughout your workflow, it also optimizes and automates this workflow to increase your productivity.

Automation Engine:

• avoids double entry and possible operator errors,

• processes files faster (through digital standardization of production procedures, hot folders automation, smart notifications...).

• frees operators from administrative tasks so they can concentrate on value-adding graphical tasks,

• allows operators to share their expertise through tickets,

• keeps jobs, related files and related customer information organized to facilitate communication and treatment of additional orders.

All this maximizes your efficiency and the quality of your deliverables, while lowering the cost of prepress-related actions.

Integrating with your Existing Systems

Automation Engine can integrate seamlessly with your graphical editors, RIP, file servers, MIS system...

It supports the industry standards (PDF, XML, XMP, SQL queries, JDF communication...).

The Automation Engine client application (the “Pilot”) can be installed on any Macintosh or Windows machine in your network, so all your operators can view files, get information or launch processing tasks as needed.

Growing with You

Automation Engine is very modular and can be tailored to your needs, while always offering growth possibilities.

From a background assistant to Adobe® Illustrator® to a central prepress server to a complete server platform linking to your administrative systems, Automation Engine can grow with you to let you handle larger accounts, accepting more jobs without increasing your costs.

You can find an overview of all Automation Engine modules on

the Esko website

1.1 Copyright Notice

All rights reserved. This material, information and instructions for use contained herein are the property of Esko Software BVBA. The material, information and instructions are provided on an AS IS basis without warranty of any kind. There are no warranties granted or extended by this document.

Furthermore Esko Software BVBA does not warrant, guarantee or make any representations regarding the use, or the results of the use of the software or the information contained herein. Esko

Automation Engine

Software BVBA shall not be liable for any direct, indirect, consequential or incidental damages arising out of the use or inability to use the software or the information contained herein.

The information contained herein is subject to change without notice. Revisions may be issued from time to time to advise of such changes and/or additions.

No part of this document may be reproduced, stored in a data base or retrieval system, or published, in any form or in any way, electronically, mechanically, by print, photoprint, microfilm or any other means without prior written permission from Esko Software BVBA.

This document supersedes all previous dated versions.

PANTONE

, PantoneLIVE and other Pantone trademarks are the property of Pantone LLC. All other trademarks or registered trademarks are the property of their respective owners. Pantone is a wholly owned subsidiary of X-Rite, Incorporated. © Pantone LLC, 2012. All rights reserved.

This software is based in part on the work of the Independent JPEG Group.

Entertainment.

Part of the software embedded in this product is gSOAP software. Portions created by gSOAP are

This product includes software developed by the Apache Software Foundation (http:// www.apache.org/).

Adobe, the Adobe logo, Acrobat, the Acrobat logo, Adobe Creative Suite, Illustrator, InDesign, PDF,

Photoshop, PostScript, XMP and the Powered by XMP logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and/or other countries.

Microsoft and the Microsoft logo are registered trademarks of Microsoft Corporation in the United

States and other countries.

SolidWorks is a registered trademark of SolidWorks Corporation.

The Esko software contains the RSA Data Security, Inc. MD5 Message-Digest Algorithm.

Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun

Microsystems in the U.S. and other countries.

Part of this software uses technology by BestTM Color Technology (EFI). EFI and Bestcolor are registered trademarks of Electronics For Imaging GmbH in the U.S. Patent and Trademark Office.

Contains PowerNest library Copyrighted and Licensed by Alma, 2005 – 2007.

All other product names are trademarks or registered trademarks of their respective owners.

Correspondence regarding this publication should be forwarded to:

Automation Engine

Esko Software BVBA

Kortrijksesteenweg 1095

B – 9051 Gent [email protected]

1.2 Getting Help

You can find the PDF version of this manual on the Automation Engine Documentation DVD.

To get an overview all of the keyboard shortcuts you can use in the Automation Engine Pilot, go to

Help > Shortcuts...

Automation Engine

2. What is Automation Engine

Automation Engine Architecture

Automation Engine is a client/server workflow software, running on Mac and PC. This means that one machine runs the Automation Engine server, to which you can connect from all Mac and PC machines in your network (using the Automation Engine Pilot).

Your Automation Engine server can connect to graphical editing software like ArtPro, PackEdge,

Adobe Illustrator (using the DeskPack plug-ins)...

It can also connect to your RIP software to ensure professional output.

You can store your files either on the Automation Engine server, on a dedicated file server, or on different machines over the network (using containers).

Automation Engine

Automation Engine Processing

Automation Engine processes your files using Tasks (for example a Trap or RIP task), Task Chains

(a succession of tasks, for example normalizing your PDF file, trapping it, then zipping it), and

Workflows (more powerful and flexible grouping of tasks, that can take complete care of the file from input to output).

Automation Engine

Files and Jobs in Automation Engine

In Automation Engine, your files can be part of jobs (customer orders that contain files and related customer information), that are located in containers (local or remote shared folders that Automation

Engine can access).

Depending on how you want to work with Automation Engine, you can link your jobs to customer products, focus on job pages, proofs, plates...

Automation Engine Integration

Automation Engine can not only connect to editing and RIP software, but also to WebCenter (Esko’s collaborative web platform) and other Esko workflow software (Nexus and Odystar).

2.1 The Automation Engine Pilot

The Automation Engine server software runs on a Windows server. Every Automation Engine action is performed through the Automation Engine client, called the Pilot.

The Pilot can be installed on any Mac or Windows machine on your local network.

Depending on the user access rights you will set, operators can use the Pilot to:

• organize jobs and files,

• create and modify tickets,

• launch and monitor tasks,

• control workflows and devices,

• administrate users and perform general configuration,

• etc.

2.1.1 The Pilot's Main Window

1. These icons show different modes in the Pilot:

Automation Engine

•

Containers : this shows all the data that Automation Engine can access, in the different

Containers. For more information, see

Containers

•

Job Overview : this lists all jobs existing in the Automation Engine Job database. See

Jobs

•

Last used Job : this shows the last job you worked on, and the job's data (files and folders).

2. The Views highlight different parts of the Automation Engine functionality. Certain views are only accessible in defined workflows. For more information, see

Views

3. The Tools area contains tools useful to administrate Automation Engine. See

Tools

for more information.

The Create Job button allows you to create a job.

The New Task button creates a new Ticket from the pilot. You can create a new workflow from the pilot using files.

. Using the button, you can access the information regarding the

Note: In the Job Overview mode, only Create Job is available.

The contents of the central panes depend on the View you are in.

2.1.2 Views

The Pilot's Views highlight different parts of the Automation Engine functionality. You can use them to work with your data in different ways (see

Different Ways of Working with Automation Engine

Note:

• Depending on the mode you are using (Containers, Job Overview or Last used job), you will have access to different views.

• Depending on your

access rights

, you may not be able to see some of the views.

Files

The Files view allows you to manage your jobs, files, favorites, tasks... See

The Files View

for more information.

To Do List

The To Do List view lists all actions that need user intervention. For more information, see

The To

Do List View

and

To Do List

Pages

The Pages view is only used in page workflows. It is extremely useful when working with impositions.

For more information, see

Working with Pages

Automation Engine

Products

The Product view shows the production files associated with your jobs, and allows you to reuse those files for a similar order from the same customer. For more information, see

Working with Products

Proofs

The Proof view is only used in page workflows. It shows the proof sets and the proof details. See

Working with Proofs

WebCenter

Before you can use the WebCenter view, make sure that your WebCenter site is correctly configured.

See

Integration with WebCenter

Plates

The Plates view is only used in page workflows. It shows details about all plates associated with a job. It also includes advanced features for managing plates for jobs with multiple versions. See

Working with Plates

CDI

The CDI view shows all the files sent to the Digital Flexo Suite and used to image a flexo plate on a Cyrel Digital Imager. See

The CDI View

Tasks

The Tasks view shows the current state of processing: the running tasks, the tasks waiting for execution and the recently finished tasks. See

The Tasks View

Devices

The Devices view lists all output devices connected to your Automation Engine server. It allows you to monitor, start and stop your devices and device queues.

Milestones

The Milestone view shows all milestones set for your last job (in Last used job mode), or the milestones set for all jobs (in Job Overview mode). See

Milestones

Hot Folders

The Hot Folders view lists all hot folders defined on the server (in Container mode) or all hot folders defined for a job (in Last used job mode). It offers all the necessary tools to create and manage hot folders. See

About Hot Folders

Tickets

The Tickets view shows a list of all tickets available on your server (both the default and your custom tickets). See

Tickets

Jobs

This view is only visible in Job Overview mode. It lists all jobs defined on the server. See

The Jobs

View

Automation Engine

2.2 Data Management in Automation Engine

Automation Engine works with containers, jobs, files and folders.

In the Pilot, you can view your data (files and folders) inside containers or/and jobs. There are three modes:

•

Containers : this shows all the data that Automation Engine can access, in the different

Containers. For more information, see

Containers

•

Job Overview : this lists all jobs existing in the Automation Engine Job database. See

Jobs

Last used Job : this shows the last job you worked on, and the job's data (files and folders).

2.2.1 Containers

A container is a special folder containing your files, folders and jobs, that Automation Engine can access. It can be located either on your Automation Engine server or another machine.

By default, you have an empty ExampleJobContainer, on the drive Automation Engine was installed on.

You can have many containers, that you can see in the Pilots’ Containers mode.

To create a container, see

Creating a Container

in the Reference Guide.

2.2.2 Jobs

What is a Job?

A job contains all the files and information relative to a customer job you process in Automation

Engine.

It has a blue icon and is stored in the Automation Engine Job Database. The database can hold up to 100 000 jobs.

In the Containers mode, you can see your job in its container.

Automation Engine

In the Last used job mode, you can see your job’s subfolders and files.

Job Metadata

You can attach an extended set of metadata to every job: customer information, inks to use, bar codes, impositions...). This metadata is stored in the Automation Engine database, and will be used when launching tasks on the job.

Job Automation

Automation Engine is very job-centric. On top of launching tasks and workflows on the job, you can also have tasks be launched automatically when the job reaches a certain status (for example: a new page has been delivered, the sheet is complete...).

For more information about Jobs, please see

Working with Jobs

in the Reference Guide.

2.3 Files Processing in Automation Engine

In Automation Engine, you can process your files using Tasks, Task Chains (old BackStage workflows), and Workflows.

Each of these has a Ticket, which contains all the parameters for that task, task chain or workflow.

2.3.1 Tasks

What is a Task?

A task is an action executed on a file, a folder or a job on the Automation Engine server.

Types of Tasks

There are seven types of tasks:

1. Conversion tasks such as Export to PDF, Export to PostScript...

2. File Creation tasks such as Create Wrapper File, Create PAF / JPG / XML...

Automation Engine

3. File Editing tasks such as Contourize & Clean, Trap...

4. Verification tasks such as Check Job Parameters, Check Print Rules, Preflight...

5. Administration tasks such as Prepare to Archive, Upload via FTP, Zip...

6. RIP tasks.

7. Device Output tasks.

Task Settings

You can define settings for the tasks, and save these settings as Tickets to reuse them (see

Tickets

Task Progress

When a task is launched, you can monitor its progress in the Pilot. See

Checking the Status of the

Task

2.3.2 Task Chains

Old BackStage workflows are still supported in Automation Engine (just as in BackStage), but are now called Task Chains.

A task chain is a succession of tasks, linked together in the task chain ticket.

You can build new workflows from your task chains, while keeping all your tickets settings (see

Reusing a Task Chain Ticket to Build a Workflow

2.3.3 Workflows

Automation Engine workflows are more powerful and flexible than the old BackStage workflows.

Automation Engine

You can build them and launch them on your files using the workflow editor (see

The Workflow Editor

You can also launch them from the Pilot or from Shuttle (see

Using Shuttle to Upload and Process

Files

2.3.4 Tickets

What is a Ticket?

The settings used when executing a task, task chain or workflow on a file can be saved as a ticket.

Default and Custom Tickets

The Pilot comes with a default ticket for each task, but you can also create custom tickets. You cannot overwrite or delete default tickets.

You can see all the available tickets (default and custom) in the Pilot's Tickets view.

Global and Job Tickets

Global tickets ( ) can be used on any file you can access through the Automation Engine Pilot, whereas job tickets ( ) are linked to a particular job.

Public Tickets

You can make tickets public if you want to submit files to them from Shuttle. There are several ways to make a ticket public (see

Making Your Ticket Public

in the User Guide).

Public tickets have a mark in the Public column.

Automation Engine

Note: Depending on your

access rights

, you may only see public tickets, and public parameters inside the tickets.

Automation Engine

3. Getting Started with Automation Engine

3.1 Starting Automation Engine

To start working with Automation Engine you need to:

• Start the Automation Engine server, see

Starting the server

• Start the Automation Engine pilot, see

Starting the pilot

3.1.1 Starting the Automation Engine Server

Automation Engine features a new web tool for server administration. This means you can access the server administration tool from any workstation via http://servername or http://servername:9999/.

On this web server administration tool you will also find the client application(s) such as the

Automation Engine Pilot, a diagnostics tool, a back-up tool, ...

To start the Automation Engine server:

1. Open your web browser and go to http://servername or http://servername:9999/.

2. Log in with your user name and password.

3. In the Server administration > Start/Stop Server window, you have access to all admininstration tasks for the Automation Engine server.

Automation Engine

For more information on working with the server, see

Server Administration.

3.1.2 Starting the Pilot

On your Automation Engine client machine:

1. Do one of the following:

• double-click the Pilot desktop icon ,

• go to Start > All Programs > Esko > Automation Engine Client 10.0 > Pilot.

2. In the Logon Information dialog that opens:

20 a) Enter a User name and Password valid for your Automation Engine server.

Automation Engine

Note:

Before you define any user, you can log in using admin

as both user name and password.

Once you have created users (see

Creating Users

), you can log in with one of your users’ credentials.

b) In Server, enter either your Automation Engine server’s name or its IP address.

c) Click OK.

This opens the Pilot’s main window.

3.2 Performing Basic Configuration

3.2.1 Creating Users

1. In the Pilot, go to Tools > Users.

2. In the Users window, do one of the following:

• go to File > New User,

• use the CTRL + N shortcut,

• click the icon.

The New User dialog opens.

3. Enter the user's Name, Full Name, Password, Description and valid E-mail address.

4. If you want the user to be able to administer Automation Engine, check the toggle.

This will give all user access rights to that user.

5. Click OK to add your new user to the Users list.

Attention:

Creating a user via Automation Engine means that Automation Engine requests the Windows OS to create that user.

Some changes to that user can then no longer be made through the Automation Engine Pilot, but need to be done via the Windows user administration tools.

3.2.2 Defining User Access Rights

Not all users have the same responsibilities, so you can assign them different access rights in

Automation Engine.

• To give access rights to a single user: a) in the Users window, double the user you want to give access rights to,

Automation Engine b) in the Access Rights tab of the Properties window, check the access rights you want this user to have.

Note: Automation Engine Administrators automatically have all access rights. You cannot change this.

• To give a particular access right to several users: a) in the Users window, click the Access Rights button to switch to the Access Rights view, b) select the access right you want to give to your users, c) check the users you want to give this access right to.

Automation Engine

3.2.3 Configuring Output Devices

Automation Engine can output files to a variety of output devices (CDI, HP Indigo, Kodak Approval, etc.).

Automation Engine uses EskoArtwork’s FlexRip engine to RIP the file in preparation for output.

To connect Automation Engine to an output device, you need to connect it to FlexRip.

1. In the Pilot, go to Tools > Configure.

This opens the Configure dialog.

Automation Engine

2. Select the option corresponding to your output device in the list at left (for example, select FlexRip

- Proofer Output to output to a proofer).

3. Go to File > New or use the Insert key (on Windows).

This shows tabs with parameters at right.

Automation Engine

4. In the General tab: a) To output to a RIP, enter the name or IP address of your RIP server in RIP Node.

For a FlexProof output, enter the name / IP address of your proof server in Proofer Node.

b) Enter the EskoLink port number used by the Dispatcher in EskoLink Portnr. (only for FlexRip outputs).

Note: You can find that port number by going to Info > Ports in the Dispatcher.

c) Click the Synchronize with Rip / Synchronize with ProofNode button.

After a few seconds, your RIP/proof server is connected to Automation Engine, and you can see its name in the Type field.

5. In the Queue tab: a) Give your queue a name in the Queue field.

b) Choose a Queue Job Limit:

• choose 1 to have the RIP handle one file at a time (this ensures the files are ripped in the order they enter the RIP),

• choose 2 to have the RIP handle two files at once (the files may not be ripped in the order they enter the RIP if for example you send a big then a small file).

6. Go to File > Save to save the configuration.

You can now see the devices you are connected to in the Pilot’s Devices view.

3.3 Uploading Files using the Pilot

1. In the Pilot’s Containers mode, select the container and folder in which you want to upload your file.

2. Go to File > Upload...

3. In the browser dialog that opens, browse to your file and click Upload.

Automation Engine

3.4 Launching a Task on a File

There are several ways to launch a task on a file (from the Pilot, from Shuttle, via Hot Folders or via

JDF/JMF). Here is how to launch a task from the Pilot's Files View.

1. In the Pilot, select the Files view from the Views bar (or use Go > Files ).

2. In the Containers mode, browse to your chosen file.

3. Right-click it, select New Task then More Tickets...

Note: If you have launched tasks previously, the most recent task tickets you used are listed above More Tickets...

4. In the Select Ticket dialog that opens, select the task ticket you want to use.

Note: This dialog contains all the tickets suitable for the file type you selected. You can choose either a Default ticket, or a custom ticket (saved under a different name) if you have already created one.

5. Click OK.

This opens the task’s ticket.

Automation Engine

6. Fill in the settings you want to use in the ticket.

Note: For a description of all of the ticket's settings for each task, see

The Tasks: an Overview

in the Reference Guide.

7. Click the Launch button.

You can monitor the tasks progress in the Files View's Task pane or in the Tasks View. See

Check the Status of the Task

3.5 Checking the Status of the Task

After launching a task on one or several file(s), you can check its processing status in the Pilot’s

Tasks pane. You can see the Tasks pane in the Files, Product or Tasks views.

You can see the progress (in percentage) and the processing state. The state can be:

Automation Engine

•

: starting

: success

•

: warning

: failure

•

: processing cancelled

If you click on the

You can also double-click the task entry in the Tasks pane to open your task ticket and check its parameters.

Note: Depending on your

access rights

, you may only see the public parameters.

3.6 Checking the Result in the Viewer

The Automation Engine Viewer can open different file types (PDF, AI, PSD...). For a full list, see

Supported File Types

in the Reference Manual.

In the Files view, you can easily view different types of files using viewer. However, the viewing privileges depend upon the specified user rights.

Note: If the the user access right for deep zoom is not enabled (read more here

Defining User Access

Rights

)while defining user rights:

• you can only view prepared files

• your zoom is restricted.

Automation Engine

You can now zoom in on the file, measure distances and densities, view separations individually or together, etc.

3.7 Relaunching the Task

• To relaunch the task without changing the settings: a) Select the task to relaunch in the Tasks pane.

b) Go to Tasks > Relaunch.

• To change the settings and relaunch the task: a) Select the task to relaunch in the Tasks pane.

b) Go to Tasks > Open.

c) Change the task settings as necessary.

d) Click the Launch button.

3.8 Generating Output

To output a file, use a task related to the output device you have configured (see

Configuring Output

Devices

For example, use the Proof (FlexProof) task if you have configured a proofing device using FlexRip

- Proofer Output.

Note: The task related to your output device will only be available once you have correctly configured your output device.

Automation Engine

4. Server Administration

Automation Engine features a new web tool for server administration. This means that you can access your server administration tool from any workstation via http://servername or http:// servername:9999/.

On this web server administration tool you will also find the client application(s) such as the

Automation Engine Pilot, a diagnostics tool, a back-up tool, ...

Server administration consists of:

•

Starting/Stopping the server

•

Setting up the server

•

Backing up the server

•

Restoring the server

•

Managing databases

•

Managing SQL servers

•

Managing application servers

4.1 Starting and stopping the server

In this window you see an overview of the connected clients and the number of running tasks. You can:

• Start and stop the Automation Engine server

• Activate the server after install

• Restart the web server

• Download the server administration log files for support purposes

Automation Engine

4.2 Setting up the server

In the Server Setup window you can change the server role: master, assistant or idle. You can also:

• View and remove Assistant Servers

• Change the system account and/or password

• Change the processing capabilities

• Redirect central resources to a central file server

4.3 Backing up the server

In the Server Backup window you can manage the backup settings:

• Specify a backup folder on the server

• Choose the number of backups to keep

• Set a backup schedule or manage existing schedules

Automation Engine

4.4 Restoring the server

In the Restore window you can view and restore back-ups. You can also:

• Restore, duplicate or migrate your server configuration

• Restore resources or databases only

Note: Take into account that the server should be stopped before you can restore a back-up.

4.5 Managing databases

In the Databases window you can manage all databases that are on any accessible SQL server in your network. You can:

• View the SQL server status

• Login and view the properties and status for each database

• Create or remove databases

Automation Engine

• Back-up or restore databases

• Repare or move databases

Note: Take into account that, even if you are logged in to the Server Administration, you also need to log in to the SQL Server instance separately.

Automation Engine

4.6 Managing SQL servers

In the SQL Server window you can manage any accessible SQL server in your network. You can:

• View the SQL server status

• Stop and restart an SQL server

• Login and change the properties: modify the maximum physical memory of the SQL server

• Look at the SQL server logs

Note: Take into account that, even if you are logged in to the Server Administration, you also need to log in to the SQL Server instance separately.

4.7 Managing application servers

In the Application Server window you can view the status of any accessible application server in your network. You can:

• Start, stop or activate the local application server

• Download log files for support purposes

• Deploy components on the application server

• Log on to another application server

Automation Engine

5. Uploading Files to Automation Engine

You can work with files that are already stored in your containers, or upload new files to Automation

Engine. You can upload files from the Pilot, using Hot Folders or with the Shuttle application and plug-in.

5.1 Uploading Files using the Pilot

1. In the Pilot’s Containers mode, select the container and folder in which you want to upload your file.

2. Go to File > Upload...

3. In the browser dialog that opens, browse to your file and click Upload.

5.2 Uploading Files from a FTP Server

1. In Containers mode, right-click the folder in which you want to upload your file, and select Upload from FTP Site...

This opens the Upload from FTP Site dialog, where you can enter the details necessary for the

FTP connection.

2. In Host, enter the name of the FTP server that hosts your files.

Tip: To use a port other than the default port, add

and the port number after the host name.

For example: myftpserver:1085

3. Enter the User Name and Password you use to connect to the FTP server.

Make sure you use a valid User Name and Password corresponding to an account that exists on the FTP server.

4. In File Transfer, choose between Binary and ASCII.

Binary will always work, but if you have an ASCII file, the transfer will go a bit faster when selecting

ASCII.

5. By default, the transfer uses Active Connection Mode (where the FTP server opens the data connection).

If your system is behind a firewall that blocks incoming FTP server connections, select Passive to use Passive Connection Mode (where the client initiates the connection).

6. Select Secure FTP if you are connecting to a secure FTP server (over FTPS, not SSL or SSH).

Tip: If you are experiencing problems using secure FTP, try connecting over regular FTP, and ask your IT administrator to check the security settings of your FTP server.

7. If desired, you can delete the files from the FTP site once they are uploaded to the Pilot (select

Remove remote data after transfer).

Automation Engine

If you do this, you can choose to Backup remote data before removal. Select the Backup Folder in which to copy the files.

8. When you are done, click Connect.

5.3 Using Hot Folders to Upload and Process Files

To use Hot Folders to upload files to Automation Engine, you need to:

1. Create a Hot Folder.

See

Creating a Task Hot Folder

and

Creating a JDF Hot Folder

2. Drop files into your Hot Folder...

• either manually or by setting an application to output files there (for Task Hot Folders),

Automation Engine

• by setting your MIS system to output files there (for JDF Hot Folders).

5.3.1 About Hot Folders

A Hot Folder is a special folder monitored by Automation Engine. When you drop a file into the Hot

Folder, Automation Engine will pick it up and process it.

There are two types of Hot Folders:

• Task Hot Folder: when you drop a file of the right file type into the Hot Folder, Automation Engine launches a task, task chain or workflow (that you have attached to the Hot Folder), on the file.

See

Creating a Task Hot Folder

• JDF Hot Folder: when your MIS system drops a JDF file into the Hot Folder, Automation Engine processes it. When processing is finished, it writes the result into the output folder associated with the JDF Hot Folder.

See

Creating a JDF Hot Folder

5.3.2 Creating a Task Hot Folder

1. Either:

• click the Hot Folders view in the Views bar,

• go to Go > Hot Folders,

• use CTRL + SHIFT + H.

Click the Create New Hot Folder button .

3. In the dialog that opens, select Task Hot Folder and click OK.

This opens the New Hot Folder dialog.

Automation Engine

4. Browse to the folder you want to turn into a Hot Folder.

Note:

• You cannot select folders that are already Hot Folders ( ).

•

You can create a new folder with .

5. If desired, you can change the responsible Operator.

6. You can also make the Hot Folder Inactive at certain times (to decide when the files will be processed and / or use less resources).

7. Set the Poll Interval (how often Automation Engine will check the Hot Folder for new files).

By default, this is set to 5 minutes.

8. Assign a Low, Normal or High processing Priority to the files coming into your Hot Folder.

9. Attach a task or workflow to your Hot Folder.

This task / workflow will be launched automatically on files coming into the Hot Folder.

You can either:

•

Attach a task or task chain that will process all file types

•

Attach a workflow that will process all file types

•

Attach different tasks / workflows to process different file types

10.When you are done, click OK in the New Hot Folder dialog.

Automation Engine

The Hot Folder is now listed in the Pilot's Hot Folders View. You can see information about the

Hot Folder in the Details pane at the bottom.

Attaching a Task for All File Types

1. Choose A Task (Chain) for all File Types in Automatic Tasks.

2. Click Edit... near Task Type and Settings.

3. In the Add Step dialog, select the task (or task chain) ticket you want to use and click OK.

Automation Engine

4. In the Select Task Type and Settings dialog, enter your settings and click Save and Close.

Automation Engine

Note:

• You can add other tasks as steps to create a task chain (for more information, see

Task Chains

• Task (chain) tickets are copied into the hot folder and lose all relation with the original tickets.

Automation Engine

5. Select Grouped Launching if you want the files in the Hot Folder to be processed together (in one workflow) instead of individually.

Tip: Use this with a specific Inactive time (for example

08:00 AM

05:00 PM

, so the files are only processed at the end of the day) or a very large Poll Interval.

6. Select a Working Folder (Automation Engine will copy the input files to this folder and start the processing from there).

7. Choose to Delete the input files when the automatic task is finished or not.

8. Add an Annotation if you wish.

Attaching a Workflow for All File Types

1. Choose A Workflow for all File Types in Automatic Tasks.

2. If you want to run the workflow in a job context: a) Select First, move files (to Job).

b) Define the Job Folder to move the file(s) into.

c) Define the name to give to the File.

You can browse to a location and / or use SmartNames.

3. Click the Set Up Workflow... button.

4. In the Select a Workflow to Start from dialog, select the workflow ticket you want to use and click OK.

This opens that workflow in the workflow editor window.

Automation Engine

5. Modify your workflow if desired, then save and close it.

Note: The workflow ticket is copied into the hot folder and loses all relation with the original ticket.

6. Select Grouped Launching if you want the files in the Hot Folder to be processed together (in one workflow) instead of individually.

Tip: Use this with a specific Inactive time (for example

08:00 AM

05:00 PM

, so the files are only processed at the end of the day) or a very large Poll Interval.

7. Select a Working Folder (Automation Engine will copy the input files to this folder and start the processing from there).

8. Choose to Delete the input files when the automatic task is finished or not.

9. Add an Annotation if you wish.

Attaching Tasks or Workflows for Different File Types

1. Choose Based on File Type in Automatic Tasks.

2. Click Add...

3. In the Add Step dialog, select the task (or task chain, or workflow) ticket you want to use and click OK.

4. In the Select Task Type and Settings dialog, enter the settings for the task(s), or for each workflow step, and click Save and Close.

Note:

• You can add other tasks as steps to create a task chain (for more information, see

Task Chains

• The tickets you choose are copied into the hot folder and lose all relation with the original tickets.

5. In the dialog that opens:

Automation Engine

46 a) Select the File Types you want to automatically process with this task, task chain or workflow.

Note: Some files with external references are not supported (PLA, STA, GRQ, GRI...).

b) Select a Working Folder (Automation Engine will copy the input files to this folder and start the processing from there).

c) Choose to Delete the input files when the automatic task is finished or not.

d) Add an Annotation if you wish.

e) Click OK.

Automation Engine

6. Back in the New Hot Folder dialog, add tasks, task chains or workflows for other files types if desired.

5.3.3 Modifying Hot Folder Settings

If you need to modify a Hot Folder’s settings after creating it, do the following:

1. In the Hot Folders view:

• double-click the Hot Folder you want to edit,

• right-click it and select Open Hot Folder...

• select it and go to File > Open Hot Folder... (or use CTRL + O).

2. In the Open Hot Folder dialog: a) change the Hot Folder settings (Hot Folder, Operator, Inactive between... ) as necessary, b) change the attached task or workflow's settings as necessary, c) click OK.

Tip: You can export the task ticket used for your Hot Folder, to be able to use it throughout

Automation Engine. Use the Export Ticket... button and give the ticket a different name.

5.3.4 Updating Your Task Hot Folders

If you have Hot Folders created in Automation Engine 12.0 that launch a task chain containing a workflow ticket (for example Copy Or Move File + Workflow as below), you can use them to make new Hot Folders that launch the workflow directly.

Automation Engine

Note: You can only do this if your old Hot Folder was launching a workflow, not a task chain consisting only of task steps.

You don't need to make new Hot Folders as your old Hot Folders will keep on working, but the advantages of updating your Hot Folders are:

• You don't need to add a separate Copy Or Move File task to copy the incoming files to a job folder (you can use First, move files (to Job)).

• You can edit the workflow to launch directly from within the New Hot Folder dialog.

• You can set a Poll Interval (how often Automation Engine will check the Hot Folder for new files).

• You can assign a processing Priority to the files coming into your Hot Folder.

• You can use Grouped launching to process the files in the Hot Folder together (in one workflow) instead of individually.

1. Open the old Hot Folder setup and: a) Click the workflow icon in the chain.

b) Select the whole workflow except the Start step.

c) Right-click the selection and click Copy.

You can also use Ctrl + C (on PC) or Command + C (on Mac).

d) Close the old Hot Folder setup window.

Automation Engine

2. Create a new Hot Folder and: a) Choose A Workflow for all File Types in Automatic Tasks.

b) Click the Set Up Workflow... button.

c) In the Select a Workflow to Start from dialog, select the Default workflow ticket.

d) In the workflow editor window that opens, paste the workflow you copied from the old Hot

Folder and connect it to the Start step.

Do the rest of the Hot Folder setup as explained in

Creating a Task Hot Folder

on page 39.

5.4 Using Shuttle to Upload and Process Files

You can upload and process files from any Mac or PC client machine using the Shuttle application.

5.4.1 What is Shuttle?

Shuttle is a small stand-alone application that enables you to submit files to Automation Engine tasks or workflows, Odystar canvases, and Nexus workflows, and monitor their progress. You can use

Shuttle to connect to several servers.

The Shuttle functionality is also integrated in ArtPro, Neo, PackEdge, Plato, FastImpose and in Adobe

Illustrator as a DeskPack plug-in.

5.4.2 Shuttle Setup

Automation Engine Setup for Shuttle

1. In the Pilot, go to Tools > Configure.

2. Select Shuttle in the left pane.

Automation Engine

3. Enter the Port to use for communication between your Automation Engine server and the Shuttle clients.

Note: By default this is port 5182, but if this port is already used by other processes, you should enter the next available port.

4. Choose an Upload Folder using the Browse... button.

This is where Shuttle clients will upload files that are not located in a container (except the Shuttle plug-in, that will always upload files to the DeskPackContainer).

Automation Engine

Note: The Upload Folder must be located on a container.

5. Select Start Shuttle server automatically when Automation Engine is started if you plan to make frequent use of the Shuttle technology.

6. Click the Start button to start Shuttle server.

Shuttle server makes Automation Engine’s workflows, tasks and files accessible to the Shuttle clients.

7. Save your settings.

Note: If you need to make changes to this Setup, you must Stop the Shuttle server first.

Making Your Ticket Public

Important: With Shuttle, you can submit files to any Automation Engine task, task chain or workflow that has a custom ticket. To do this, you need to make the ticket public.

You can either:

• Select the Public option when creating the ticket.

•

Select your ticket in the Ticket view, click and select Public.

• Right-click your ticket in the Ticket view and select Public Ticket.

Note: Public tickets have a mark in the Public column.

Automation Engine

Shuttle Clients Connecting to Any Server

Shuttle Standalone, the Shuttle plug-in, and the Shuttle clients in ArtPro, Neo and FastImpose

Standalone can connect to a number of Odystar, Nexus and Automation Engine servers.

1. Launch your application.

2. Open the Preferences.

In...

Shuttle Standalone go to...

• Shuttle > Preferences... or use Command

+ , (comma) on Mac

• Edit > Preferences... on Windows

Illustrator

• Illustrator > Preferences > EskoArtwork >

Shuttle Preferences... on Mac

• Edit > Preferences > EskoArtwork >

Shuttle Preferences... on Windows

ArtPro

Neo

ArtPro > Preferences... or use Command + K

Neo > Preferences... or use Command + ,

(comma)

FastImpose Standalone Tools > Shuttle Preferences...

In the Servers tab (Advanced tab for Neo), click the button at the bottom of the Servers list.

Automation Engine

This opens the following pop-up:

4. Enter your User Name and Password.

• When connecting to an Automation Engine server, enter the User Name and Password you use to log in to the Pilot (the password can be blank if your server is configured to accept this).

You will have the same access rights (for example, the right to set processing priorities or not) in Shuttle as you have in the Pilot.

Note: If you don’t know which User Name and Password to use, contact your system administrator.

5. To connect to a server not broadcasting over the Bonjour network (Automation Engine servers or non-Bonjour-enabled Nexus servers): a) Select Manual in the Browse Method list b) Enter your server’s name or IP address in Server Address c) Fill in the Server Port used by your server

Automation Engine

Note:

When connecting to an Automation Engine server, enter the port you defined in Configure (see

Automation Engine Setup for Shuttle

6. Click the Add button.

This adds a connection to your server in the Servers list.

•

To remove the connection to a server, select it in the Servers list and click the button.

• To check or edit a server’s settings, double-click it in the Servers list.

Note:

If you are using the Shuttle plug-in with other Deskpack plug-ins, and you have set up a server connection with the Server Connection Assistant, you will see this connection in bold in the Shuttle plug-in’s Servers list (after restarting Illustrator).

You will be able to change the user name and password if necessary, but you will not be able to remove this connection from the Shuttle plug-in.

See the Adobe Illustrator Client documentation for more information on the Server Connection

Assistant.

Shuttle Clients Connecting only to Automation Engine

The Shuttle clients in PackEdge, Plato and FastImpose Server can only connect to one Automation

Engine server.

1. Launch your application.

2. Open the Preferences.

• In PackEdge or Plato, go to Edit > Preferences or use Ctrl+Alt+Shift+P.

• In FastImpose Server, go to Tools > Options...

3. In the Server&Resources tab (the Server tab for FastImpose Server): a) Select Connect to Automation Engine Server.

b) Enter the Automation Engine Server Name and click Check.

You should see a message saying the server is up and running.

c) Select Login with the following user account settings, and fill in the User Name and Password you use to login to the Pilot.

If the connection is successful, you will see a green dot and the message Connected as user ...

Automation Engine

Tip:

If you are running an Automation Engine Pilot on the same computer, or another Shuttle client connecting to it (either PackEdge, Plato or FastImpose Server), you can select Login automatically with user name and password from other application connected to the server.

This way, if you are already logged in to the Pilot or the other client application, you won't need to log in when starting PackEdge / Plato / FastImpose Server.

4. Restart your application.

5.4.3 Launching Files from Shuttle Standalone

1. To assign a Job ID and / or Job Part ID to the files to process in your workflow, go to Window

> Context and fill in the Job ID and / or Job Part ID.

Do this when:

• you want to add your file(s) to an Automation Engine job,

Note: If the file you are launching is already located in an Automation Engine job, it will automatically be processed within that job’s context (you don’t need to enter the Job ID).

2. Open the Launch window using:

• File > New Launch Window... ,

• Option + Command + N on Mac or Alt + Control + N on PC.

3. Select the Workflow you want to launch on your file.

• For Automation Engine workflows, you will see public tickets.

Automation Engine

Note:

You can open several Launch windows, and select a different workflow in each.

If you quit and restart Shuttle, your Launch windows will be remembered.

4. Launch your file in one of the following ways:

• Drag and drop your file on the Drop Files Here arrow.

• Click the Launch... button and browse to the file you want to launch.

• Go to File > Launch... and browse to the file you want to launch.

• Use Command + S (on Mac).

5. If your workflow has public parameters, you will see a pop-up where you can fill them in.

Note:

For more information on public parameters, see:

•

Using Public Parameters

5.4.4 Launching Files from ArtPro

1. To launch your current file to Shuttle, go to File > Launch Workflow...

This opens the Launch Workflow window.

Automation Engine

2. Choose what file type you want to launch your file as.

If your workflow is...

you can launch the file as...

Normalized PDF with...

an Automation Engine workflow accepting

Normalized PDF files as input either Normalized PDF or Normalized PDF

(embedded) an Automation Engine workflow accepting PDF files as input

PDF any of the available PDF flavors an Automation Engine workflow accepting ArtPro files as input

ArtPro with the included images

(TIFF, EPS...) or without

(only the ArtPro and the

ArtPro CT file)

3. If you want to add your file to an Automation Engine job, select it in the Job list or fill in the Job

ID and/or Job Part ID.

Automation Engine

Note: Use the Search... button to see a list of your server's jobs, with job information and a filter.

4. If you want to add your file to an Automation Engine product, select it in the Product list or fill in the Job ID and/or Job Part ID.

Note: Use the Search... button to see a list of your server's products.

5. Select the workflow you want to launch your file to.

6. If your workflow has public parameters, you can fill them in in the same window.

Automation Engine

7. Click the Launch button.

5.4.5 Launching Files from PackEdge or Plato

Attention: You must save your file on an Automation Engine container before you can launch it into a workflow from PackEdge or Plato.

1. Go to File > Launch Workflow...

This opens the Launch Workflow window.

2. Select the workflow you want to launch on your file in the workflow list.

3. If your workflow has public parameters, you can fill them in in the same window.

Note: For more information on public parameters, see

Using Public Parameters

Automation Engine

4. Click Launch to launch the workflow on your file.

Tip:

To access Shuttle easily in the future (without using the menus):

Go to Window > Toolbars > Shuttle to open the Shuttle palette.

2. Drag it into your application’s toolbar.

Click to open the Launch Workflow window, or to open the Shuttle window.

5.4.6 Launching Files from FastImpose

When working with FastImpose Server, you must save your file on an Automation Engine container before you can launch it.

1. Go to File > Launch Workflow...

This opens the Launch Workflow window.

Automation Engine

2. Choose what file type you want to launch your file as.

• When working with FastImpose Server, you can only launch your file as an IMP file.

• When working with FastImpose Standalone, you can launch your file either as a JDF or a PDF file.

Click the Settings... button to set JDF or PDF Export Preferences (see the FastImpose manual for more information).

3. Select the workflow you want to launch on your file in the workflow list.

4. If your workflow has public parameters, you can fill them in in the same window.

5. Click Launch to launch the workflow on your file.

5.4.7 Launching Files from Neo

1. Go to File > Launch Workflow...

This opens the Launch Workflow window.

Automation Engine

2. Select the workflow you want to launch on your file in the workflow list.

3. If your workflow has public parameters, you can fill them in the same window.

For more information on public parameters, see:

•

Using Public Parameters

Note: If you want to go back to the default parameters values after changing them, use the Reset

To Defaults button.

4. Click Launch to launch the workflow on your file.

5.4.8 Launching Files from the Shuttle Plug-in

To launch a file into a workflow through the Shuttle plug-in, it needs to be the current file in Illustrator

(open and at the front).

1. Go to File > Launch Workflow... or use Option + Command + Z.

This opens the Launch window.

Automation Engine

2. When launching to Automation Engine, choose Normalized PDF in Launch As.

This copies the Normalized PDF version of your file onto the DeskPack Container.

Note: This uses the PDF Export plug-in to convert your Illustrator file to Normalized PDF. To refine the conversion, click Settings... and edit the PDF Export Preferences.

3. If you want to link your file to an existing Automation Engine job, fill in the Job ID and/or Job

Sub ID.

Automation Engine

Note:

• You must enter a Job ID / Job Sub ID that already exists on your Automation Engine server.

The Shuttle plug-in cannot create jobs.

• The Normalized PDF that you launch with a Job ID / Job Sub ID will be linked to that job, so that tasks and workflows processing that file can use the job parameters.

• If you are launching a file that was already in an Automation Engine job, the Job ID and/or Job

Sub ID will be filled automatically.

4. Select the workflow you want to launch your file to in Launch To Workflow.

5. If your workflow has public parameters, you can fill them in in the same window.

6. Click Launch to launch your file.

Automation Engine

6. Running Tasks on Files

6.1 Creating a Task Ticket

6.1.1 Creating a Custom Ticket from the Tickets View

To create a ticket with your own parameters, that you will be able to reuse:

1. Open the Default ticket of your chosen task.

Note: To create a custom workflow ticket, see

Building a Workflow from Zero

2. Fill in your parameters.

3. Go to File > Save As... or use Ctrl + Shift + S (on PC) / Shift + Command + S (on Mac).

4. In the Save As pop-up: a) Enter the name to give your custom ticket b) Add the ticket to your favorites if you like c) Make the ticket public if you want to be able to use it from Shuttle (send files to that task using your ticket's parameters)

Note: The Scope is always Global when creating a custom ticket from the Tickets view.

6.1.2 Creating a Custom Ticket when Working with Files

You can create a custom ticket when launching a task on a file too:

Automation Engine

1. Right-click your file, select New Task then More Tickets...

2. In the Select Ticket dialog that opens, select the Default ticket for the task you want to use.

3. Fill in the settings you want to use in the ticket.

4. Go to File > Save As... or use Ctrl + Shift + S (on PC) / Shift + Command + S (on Mac).

5. In the Save As pop-up: a) Enter the name to give your custom ticket b) Add the ticket to your favorites if you like c) Make the ticket public if you want to be able to use it from Shuttle (send files to that task using your ticket's parameters)

Note:

• If you are not in a job context, the Scope is always Global.

Automation Engine

• If you are in a job context, you can choose between Job and Global Scope.

When choosing the job scope (called after your job), you cannot make the ticket public.

6.1.3 Using Public Parameters

Public parameters are ticket parameters that operators can define when submitting files through

Shuttle.

For each public parameter, you can either:

Automation Engine

• enter a list of predefined values the operator will choose from,

• let the operator enter a value himself.

Making a Parameter Public

Note: You need to define which parameters are public before files are submitted to your workflow.

In the ticket containing the parameter to make public:

1. Right-click the parameter and select Make Parameter Public.

2. Right-click it again and select Modify Public Parameter...

3. In the Modify Public Parameter dialog that opens: a) If necessary, change the way the parameter will be called in Shuttle in Prompt as.

b) Choose either:

• Allow the user to set the value if you want Shuttle users to be able to freely enter a value for that parameter.

• Let the user select a predefined value if you want Shuttle users to choose from a list of values that you define.

Automation Engine

If that parameter already has a list of values to choose from in the Ticket, they will be displayed here. You can Add or Remove values.

Note: Shuttle operators will see (and choose from) the Predefined Settings but not the associated Values.

c) If you have chosen Let the user select a predefined value: in Default Predefined Setting, choose the setting that will be selected by default when submitting files from Shuttle (if the operator doesn’t select another setting, this one will be used for processing).

4. Don’t forget to save your ticket.

This is how your public parameter will look to Shuttle operators:

If you chose Allow the user to set the value

If you chose Let the user select a predefined value

Managing Public Parameters in Your Ticket

Once you have made parameters public in your ticket, you can have an overview of your public parameters and edit them at the ticket level.

1. In your ticket, go to Advanced > Manage Public Parameters...

Automation Engine

The Manage Public Parameters dialog that opens contains all of your ticket’s public parameters.

The left pane shows all parameters that can be made public for that ticket (the ones you have made public are greyed out).

Automation Engine

The right pane shows the parameters you have made public, with their settings (predefined values, etc.).

2. You can:

• drag parameters from left to right to make them public;

• click a public parameter’s cross if you don’t want it to be public anymore;

• rearrange the order of your public parameters (drag them up or down);

• change public parameters’ settings (Prompt as, Predefined Settings, etc.);

• group public parameters under a header (click Add Group, click to edit the header, and drag parameters from the left);

• use presets to simplify operators’ choices (see

Using Presets to Simplify Operators’ Choices

Automation Engine

Using Presets to Simplify Operators’ Choices

You can use presets to minimize the amount of public parameters your operators have to choose from, and make it simpler for them.

For example, you want operators to use different trapping settings for printing with offset or dry offset. You can define those trapping settings in a preset, so that operators will only have to choose between offset and dry offset.

In the Manage Public Parameters dialog:

1. Click the Add Preset button.

2. Enter what your operators will see: a) in Prompt as, enter the name to give the preset parameter in Shuttle, b) enter the values that operators will choose from (replacing

Type a value here

Click Add if you need to add extra values.

3. Drag parameters from the dialog’s left pane into the preset.

You can drag as many parameters as you want. They will appear under each value (here both under

Offset

and

Dry Offset

Automation Engine

4. Define the parameters values for each preset value.

For example, define normal trapping, 50% opacity and object dependant end caps for Offset, and reverse trapping, 100% opacity and round end caps for Dry Offset.

5. Don’t forget to save your ticket.

This is how your preset will look to Shuttle operators:

Making Your Ticket Public

Important: With Shuttle, you can submit files to any Automation Engine task, task chain or workflow that has a custom ticket. To do this, you need to make the ticket public.

You can either:

• Select the Public option when creating the ticket.

Automation Engine

•

Select your ticket in the Ticket view, click and select Public.

• Right-click your ticket in the Ticket view and select Public Ticket.

Note: Public tickets have a mark in the Public column.

SmartNames in Public Parameters

You can use SmartNames in your public parameters (for parameters taking SmartNames as input).

In Shuttle, use square brackets around SmartNames when submitting a file with public parameters.

Automation Engine

6.1.4 Using SmartNames

What is a SmartName?

A SmartName is a variable that refers to a predefined value, for example

[File]

refers to the name of the input file, and

[Date]

refers to the current date.

You can use SmartNames to fill in settings all across Automation Engine. They are displayed in green and between square brackets.

You can also combine them with plain text.

Using SmartNames ensures you can use existing information as a setting without having to remember it, and reduces errors.

Automation Engine

Using a SmartName

You can use SmartNames anytime you see the SmartName symbol in a text field.

1. Click .

2. In the Insert SmartNames dialog: a) browse to your SmartName using the Categories, b) select it, c) click Insert.

You can also double-click the SmartName.

Tip:

• You can type the first letters of the SmartName you are looking for to show it in the list.

• The dialog closes automatically after inserting a SmartName. To keep it open (to insert more

SmartNames), hold Alt while clicking the Insert button or double-clicking a SmartName.

• If there are several SmartName-enabled text fields (in a ticket for example), keep the Insert

SmartNames dialog open and just click on the next SmartName-enabled field to insert

SmartNames in it.

• You can choose a smartname as Folder of first input of master workflow from Task information or Name of folder of originating input of (enclosing) workflow from Workflow context to keep the names of folders from the original input for the output

Automation Engine

6.2 Launching a Task on a File

There are several ways to launch a task on a file (from the Pilot, from Shuttle, via Hot Folders or via

JDF/JMF). Here is how to launch a task from the Pilot's Files View.

1. In the Pilot, select the Files view from the Views bar (or use Go > Files).

2. In the Containers mode, browse to your chosen file.

3. Right-click it, and select either:

• New Task to fill in the ticket's settings before launching the task.

• Launch with to launch the task without changing the ticket's settings.

Note:

If you don't have the Tickets: Show All Tickets and their Parameters (Public and other) access right (see

Access Rights

in the Reference Guide), you will only see Launch with.

In this case, you can only select public tickets, and only fill in public parameters in the ticket.

4. Select the ticket to use.

• If you have launched tasks previously, the most recent task tickets you used are listed.

• If you didn't, or if you need a different ticket, select More Tickets...

In the Select Ticket dialog that opens, select the task ticket you want to use and click OK.

Automation Engine

5. If:

• You chose New Task, the task ticket opens. Fill in the settings you want to use in the ticket and click the Launch button.

Automation Engine

• You chose Launch with and you have the Tickets: Show All Tickets and their Parameters

(Public and other) access right, the task is launched on the file as soon as you selected the ticket. You don't need to fill in any settings.

• You chose Launch with and you don't have the Tickets: Show All Tickets and their

Parameters (Public and other) access right, the task is launched on the file as soon as you selected the ticket if there are no public parameters.

If the ticket contains public parameters, it will open for you to fill them in (you will only see the public parameters). Click Launch when you are done.

Automation Engine

Note: For a description of all of the ticket's settings for each task, see

The Tasks: an Overview

in the Reference Guide.

You can monitor the task's progress in the Files View's Task pane or in the Tasks View. See

Check the Status of the Task

6.3 Checking the Status of the Task

After launching a task on one or several file(s), you can check its processing status in the Pilot’s

Tasks pane. You can see the Tasks pane in the Files, Product or Tasks views.

You can see the progress (in percentage) and the processing state. The state can be:

•

: starting

Automation Engine

•

: success

: warning

: failure

: processing cancelled

If you click on the

You can also double-click the task entry in the Tasks pane to open your task ticket and check its parameters.

Note: Depending on your

access rights

, you may only see the public parameters.

6.4 Relaunching the Task

• To relaunch the task without changing the settings: a) Select the task to relaunch in the Tasks pane.

b) Go to Tasks > Relaunch.

• To change the settings and relaunch the task: a) Select the task to relaunch in the Tasks pane.

b) Go to Tasks > Open.

c) Change the task settings as necessary.

d) Click the Launch button.

Automation Engine

7. Running Workflows on Files

7.1 Building Workflows

You can build workflows from zero or using custom tickets, you can migrate task chains to

Automation Engine workflows, and create nested workflows.

You can also choose to have the prepress manager build workflows that operators will use, or let the operators build workflows on the fly while processing files.

7.1.1 Building a Workflow from Zero

Click in the Tickets view to open the workflow editor.

The workflow editor window only contains two steps by default (

2. Drag and drop your chosen steps from the workflow step list into the canvas.

and ).

Note: To find a step quickly, you can either use the step filter or the search field on top of the steps list.

3. If desired, double-click your steps’ names to rename them.

Automation Engine

You will still be able to see the original name (the task type or workflow control type) by hovering on the step.

4. Connect your steps with one another.

To do this, click a step’s green pin and drag it onto the next step. This links the two steps with a green tube.

Note: You can connect a step’s output to several other steps. Automation Engine will automatically check the format of the files going through, and send them to the appropriate step(s) depending on it.

Automation Engine

Tip: If you want to align your workflow steps on a grid, hold Shift while dragging them.

5. Double-click each step and fill in its parameters in the step ticket.

Automation Engine

6. Save your workflow using either:

• File > Save or Ctrl + S,

• File > Save As... or Ctrl + Shift + S.

7.1.2 Building a Workflow using Custom Tickets

Click in the Tickets view to open the workflow editor.

Click the tickets button up.

in the workflow editor’s toolbar to open the Ticket Browser pop-

3. Select the custom ticket you want to use and:

Do...

to...

drag the ticket into your workflow use a copy of the original ticket.

Note: Changes to the ticket settings will not be reflected in the original ticket.

hold Ctrl + Shift (on PC or Mac) or Cmd + Alt

(on Mac only) and drag it into your workflow link the original ticket to your workflow (you can see an arrow next to the ticket name).

Note: Settings changed here will also be changed in the original ticket.

4. If desired, double-click your steps’ names to rename them.

5. Connect your steps with one another.

Automation Engine

Tip:

If you want to reuse part of an existing workflow, you can copy and paste it into your new workflow

(using Ctrl + C and Ctrl + V or Edit > Copy and Edit > Paste). This keeps all of the steps’ settings.

You can also use nested workflows if you plan to reuse workflow parts several times (see

Nested

Workflows

6. Save your workflow using either:

• File > Save or Ctrl + S,

• File > Save As... or Ctrl + Shift + S.

7.1.3 Reusing a Task Chain Ticket to Build a Workflow

Your old BackStage task chain tickets will still work in Automation Engine.

However, we recommend that you make full use of the new workflow editor’s extended capabilities.

To do this, you can gradually migrate from using task chains to using workflows.

Important: You cannot automatically convert task chain tickets to workflow tickets, but you can preserve all your settings while migrating to workflow tickets.

1. In the Pilot’s Tickets view, search for the task chain ticket you want to convert.

2. Open the workflow editor.

3. Drag and drop your task chain ticket into the workflow editor window.

Automation Engine

Tip: When dragging the ticket over the canvas, you will see a message telling you where to drop it.

This shows all the steps of your task chain in the canvas.

Automation Engine

Note:

• Each step keeps all of its settings in its own ticket (you can double-click on a step to see its ticket).

• The steps are detached so you can optimize your workflow construction (the workflow editor enables you to build workflows in a more flexible and more efficient way than the task chains).

•

Deprecated steps (as the Mark File step in the example below) will be displayed in red for three seconds, then disappear. You should replace them with the corresponding workflow controls (for example, replace Mark File by Mark). See

Workflow Controls

and

Deprecated

Steps

Automation Engine

4. Turn your existing steps into a workflow: a) add tickets or workflow controls if necessary (and fill in their settings), b) make sure you have replaced the deprecated steps, c) double-click your steps names to rename them if necessary, d) connect your steps together.

Automation Engine

5. Save your workflow.

7.1.4 Nested Workflows

When you need to reuse a part of your workflow in several other workflows, you can make a subworkflow out of it.

You can then integrate this subworkflow as it is (with its settings etc.) in other workflows, creating nested workflows.

Working with nested workflows will also make your workflows look smaller and more streamlined, so you have a better overview of the current processing.

For example, the following workflow can be nested:

Automation Engine

Here is the nested workflow:

Automation Engine

7 with the first subworkflow:

Automation Engine

96 and the second subworkflow:

Automation Engine

Building a Nested Workflow

To add a subworkflow into your workflow:

In the workflow editor, drag the Workflow step into your workflow.

Tip: To find it quickly, select Workflow in the step list filter.

Automation Engine

2. Double-click the workflow step.

This shows a new workflow editor window, where you can build your subworkflow.

Automation Engine

The

3. Build your subworkflow:

indication shows you this is a subworkflow.

a) drag and drop steps into the canvas, b) connect your steps with one another, c) double-click each step and fill in its parameters in the step ticket.

Click your main workflow to go back to it (click

5. Save your workflow.

in the example).

Note: You can nest several layers of subworkflows.

Automation Engine

7.1.5 Using Routing in Your Workflow

The workflow routes files automatically to OK, Warning or Error outputs depending on their processing status.

Within your workflow, you can also route files in different ways.

Simple Processing Routing

When building your workflow, you can use the green tubes to route your files to different workflow steps.

For example, you can use this to create an imposition and a WebCenter project based on your file at the same time.

100

Note: When a step’s output pin is connected to several other steps, Automation Engine will automatically check the format of the files going through, and send them to the appropriate step(s) depending on it.

Routing in Nested Workflows

When working with nested workflows, the end steps of your subworkflow correspond with the outputs of the workflow step in your main workflow.

For example, the subworkflow below has two OK end steps, named One Up and S & R.

Automation Engine

In the main workflow, you can see that they correspond to the two green output pins of the workflow step.

This means that:

• files sent to the One Up step of your subworkflow will go through the One Up output in your main workflow (on to the Zip One Up step),

• files sent to the S & R step of your subworkflow will go through the S & R output in your main workflow (on to the Print S & R step).

Operator Routing

You can build your workflow so that operators will route your files based on their expertise.

They will get a notification, and the processing will be paused until they decide where to send the file.

To use this in your workflow:

Add the Wait for Action (Checkpoint)

2. Double-click the step to open its settings.

step to your workflow.

101

3. Create the notification that will be sent: a) Choose which user you want to send it to b) Enter a Subject c) Add a Message if desired

Automation Engine

4. Choose a Due date. Either:

• choose one of the predefined due dates (from Immediate to Next sunday),

• choose Other... in the Due date list and pick the due date yourself.

102

5. In Output states, define the output possibilities you want for your checkpoint.

By default, this step has two outputs: Completed and Aborted.

To add an output:

Automation Engine a) Click Add b) Enter the output’s name

Add as many outputs as you like.

6. If necessary, use the Move Up and Move Down buttons to display your outputs in a different order.

Note: You can Remove the default outputs if you don’t need them.

7. If you want your file to be automatically sent through one of the outputs if no action is taken by the operator after a period of time: a) Select Release automatically b) Enter the time delay after which the file should be released c) Choose the output to release the file to

8. Click OK to apply your settings.

9. On your canvas, the Checkpoint step has the outputs you defined. Connect each output to the appropriate step.

103

Automation Engine

Operators will be able to route files gone through the Checkpoint from the Pilot’s Tasks pane, the workflow editor, or Shuttle.

In the Pilot

In the Pilot, the operator will see User intervention needed in the Tasks list, and one To-Do .

He/she can:

• Click either of these elements to route the file to one of the outputs defined in the Checkpoint step (and close the To-Do).

104

In the Workflow Editor

In the workflow editor, the operator will see User intervention needed as the file status and the

Checkpoint step will jump up and down.

Automation Engine

The workflow editor will also show one To-Do

To route the file and close the To-Do, he/she can:

• Right-click the file icon and select one of the outputs defined in the Checkpoint step.

• or...

a) right-click the file icon and select Open To-Do...

b) select one of the outputs defined in the Checkpoint step.

• or...

105

Automation Engine a) click the To-Do icon , b) select Checkpoint Actions in the Actions Filter list, c) select one of the outputs defined in the Checkpoint step.

In Shuttle

Note:

The user name you used in the Checkpoint step settings and the user name your operator uses in

Shuttle (to connect to Automation Engine) must match.

If they don’t, your operator can still see the file(s) to route, but only in Shuttle’s Show All mode

( ).

For more details, please see the Shuttle manual.

In the Shuttle window, the operator will see an icon ( ) indicating that the file needs attention.

Note: This icon is not on the workflow level, but at the Checkpoint step level. Clicking shows the workflow steps.

The Inspector panel also shows an attention icon, and the notification defined in the Checkpoint step.

106

To route the file (and close the To-Do in Automation Engine), the operator can:

• In the Shuttle processing list: a) Right-click the file or the attention icon and select Attention in the context menu.

Automation Engine

This shows the notification and output states set in the Checkpoint step.

b) Select one of the output states to route the file.

• In the Inspector panel: a) Select the step in the processing list to show the notification set in the Checkpoint step.

Click and select one of the output states to route the file.

Automatic Routing

You can use the Router workflow control to route your files automatically.

In the Router’s settings, you can choose to automatically route your files based on certain criteria

(the file type, the number of separations, the value of a job parameter...).

Files matching your chosen criteria will automatically be sent through the corresponding output.

107

For example, you can route files on their file type...

Automation Engine

108

... and send each file type to a different step in the workflow.

Automation Engine

In the example above, ArtPro files and PDF files are each routed to their own normalization step, while Normalized PDF files are sent directly to the Trap step.

For more information about the routing criteria, please see the Automation Engine Reference Manual.

7.1.6 Using Public Parameters

Public parameters are ticket parameters that operators can define when submitting files through

Shuttle.

For each public parameter, you can either:

• enter a list of predefined values the operator will choose from,

• let the operator enter a value himself.

Making a Parameter Public

Note: You need to define which parameters are public before files are submitted to your workflow.

In the ticket containing the parameter to make public:

1. Right-click the parameter and select Make Parameter Public.

2. Right-click it again and select Modify Public Parameter...

3. In the Modify Public Parameter dialog that opens: a) If necessary, change the way the parameter will be called in Shuttle in Prompt as.

b) Choose either:

• Allow the user to set the value if you want Shuttle users to be able to freely enter a value for that parameter.

109

Automation Engine

• Let the user select a predefined value if you want Shuttle users to choose from a list of values that you define.

110

If that parameter already has a list of values to choose from in the Ticket, they will be displayed here. You can Add or Remove values.

Note: Shuttle operators will see (and choose from) the Predefined Settings but not the associated Values.

4. Don’t forget to save your ticket.

This is how your public parameter will look to Shuttle operators:

Automation Engine

If you chose Allow the user to set the value

If you chose Let the user select a predefined value

Managing Public Parameters in Your Workflow

Once you have made parameters public in your workflow steps’ tickets, you can have an overview of your public parameters and edit them at the workflow level.

1. In the workflow editor, go to Advanced > Manage Public Parameters...

The Manage Public Parameters dialog that opens contains all of your workflow's public parameters, sorted by workflow step.

111

Automation Engine

112

The right pane shows the workflow steps for which you have made parameters public.

The middle pane shows the public parameters for the selected workflow step.

The left pane shows all the parameters you have made public, with their settings (predefined values, etc.).

2. You can:

Automation Engine

• drag parameters from right to left to make them public;

• click a public parameter’s cross if you don’t want it to be public anymore;

• rearrange the order of your public parameters (drag them up or down);

• change public parameters’ settings (Prompt as, Predefined Settings, etc.);

• group public parameters under a header (click Add Group, click to edit the header, and drag parameters from the right);

• use presets to simplify operators’ choices (see

Using Presets to Simplify Operators’ Choices

Using Presets to Simplify Operators’ Choices

You can use presets to minimize the amount of public parameters your operators have to choose from, and make it simpler for them.

113

Automation Engine

In the Manage Public Parameters dialog:

1. Click the Add Preset button.

2. Enter what your operators will see: a) in Prompt as, enter the name to give the preset parameter in Shuttle, b) enter the values that operators will choose from (replacing

Type a value here

Click Add if you need to add extra values.

114

3. Drag parameters from the dialog’s left pane into the preset.

You can drag as many parameters as you want. They will appear under each value (here both under

Offset

and

Dry Offset

Automation Engine

4. Define the parameters values for each preset value.

For example, define normal trapping, 50% opacity and object dependant end caps for Offset, and reverse trapping, 100% opacity and round end caps for Dry Offset.

5. Don’t forget to save your ticket.

This is how your preset will look to Shuttle operators:

Checking All the Workflow's Public Parameters Values

You can quickly check the public parameters' values for your whole workflow, without having to go into each workflow step ticket.

You can do this for the default public parameters' values saved in your workflow ticket, or the public parameter values passed on to your workflow when running a file.

115

Automation Engine

1. In the workflow editor, go to Advanced > Modify Public Parameter Values...

The Modify Public Parameter Values dialog that opens contains all of your workflow's public parameter values, sorted by workflow step.

The right pane shows the workflow steps containing public parameters, and the left pane shows the parameter values.

2. Check and edit the values if necessary, and click OK.

Making Your Ticket Public

Important: With Shuttle, you can submit files to any Automation Engine task, task chain or workflow that has a custom ticket. To do this, you need to make the ticket public.

You can either:

• Select the Public option when creating the ticket.

116

•

Select your ticket in the Ticket view, click and select Public.

Automation Engine

• Right-click your ticket in the Ticket view and select Public Ticket.

Note: Public tickets have a mark in the Public column.

SmartNames in Public Parameters

You can use SmartNames in your public parameters (for parameters taking SmartNames as input).

In Shuttle, use square brackets around SmartNames when submitting a file with public parameters.

117

Automation Engine

7.1.7 Adding Sticky Notes to Your Workflow

If you want to give additional information to the operators using your workflow, you can add sticky notes to it.

To do this, right-click your workflow background and select Add Sticky Note. This creates an empty sticky note where you right-clicked.

118

To enter text, click and enter your text. When you are done, click .

You can move the sticky note on the workflow canvas, or resize it by dragging its bottom right corner.

If you want to delete the sticky note, click .

To hide all of your workflow's sticky notes, go to View > Hide Sticky Notes . To show them again, go to View > Show Sticky Notes .

Automation Engine

When saving your workflow, all of its sticky notes are saved with it.

7.1.8 Checking All the Workflow's Parameters

You can use the Parameter Inspector to quickly go over all your parameters, without having to go into each workflow step ticket.

1. Right-click any workflow step (task or workflow control) and select Show Parameter Inspector...

2. The left column shows all of the workflow steps in alphabetical order. Click the task / workflow control whose parameter you want to see.

The parameters are shown at right.

3. Change the parameters as you wish.

Your changes are applied instantly in the workflow.

4. If you want, you can also:

• Save the parameters of the task you just edited as a new ticket (using Save As...).

• Edit that task's public parameters (using Manage Public Parameters...).

See

Using Public Parameters

on page 69 for details on how to use public parameters.

5. Close the Parameter Inspector when you are done.

119

Automation Engine

7.2 Using Workflows

After launching a workflow on your file, you can check its processing status, pause the workflow, or relaunch your workflow with different settings.

7.2.1 Launching a Workflow on a File

There are several ways to launch a workflow on a file (from the Pilot, from Shuttle, via Hot Folders or via JDF/JMF). Here is how to launch a workflow from the Pilot's Files View.

1. In the Files view, right-click the file(s) to process and select either:

• New Task to fill in the workflow's settings before launching it.

• Launch with to launch the workflow without changing its settings.

Note:

If you don't have the Tickets: Show All Tickets and their Parameters (Public and other) access right (see

Access Rights

in the Reference Guide), you will only see Launch with.

In this case, you can only select public workflow tickets, and only fill in public parameters for the workflow.

2. Select the workflow ticket to use.

• If you have launched workflows previously, the most recent workflow tickets you used are listed under Workflow.

• If you didn't, or if you need a different ticket, select More Tickets...

In the Select Ticket dialog that opens, select the workflow ticket you want to use and click OK.

120

Automation Engine

Tip: Workflow tickets have Workflow as task type. You can use the search field in the Select

Ticket dialog to find them easily.

3. If:

• You chose New Task, the workflow editor window opens. Fill in the settings you want to use in each workflow step and click the Launch button.

Tip: Hold Alt while clicking Launch to keep the workflow editor window open to monitor your workflow (the Launch button shows an eye ).

• You chose Launch with and you have the Tickets: Show All Tickets and their Parameters

(Public and other) access right, the workflow is launched on the file as soon as you selected the workflow ticket. You don't need to fill in any settings.

• You chose Launch with and you don't have the Tickets: Show All Tickets and their

Parameters (Public and other) access right, the workflow is launched on the file as soon as you selected the workflow ticket if there are no public parameters.

If the ticket contains public parameters, it will open for you to fill them in (you will only see the public parameters). Click the Launch button when you are done.

121

Automation Engine

You can monitor the workflow's progress in the Files View's Task pane or in the Tasks View. See

Checking the Workflow's Processing Status

on page 124.

Note: If you send files linked to several jobs to the same workflow at the same time (for example when using the Files view and Shuttle or a Hot Folder), a separate workflow will be started for each job context.

7.2.2 Building a Workflow and Launching it on a File on the Fly

You can build and use workflows at once or separately, depending on who in your company performs it.

• If you want to keep workflow creation and workflow use separated, the Prepress Manager can create workflows in the Tickets view, then Prepress Operators can launch them on files in the

Files view.

• If you prefer your users to be able to create and launch workflows on the fly, they can do it all from the Files view:

1. In the Files view, select the file(s) you want to launch your workflow on.

Click to open the workflow editor.

122

Automation Engine

Note: You can see your file(s) in the files pane of the workflow editor window.

3. Build your workflow as described previously (see

Building a Workflow from Zero

Building a

Workflow using Custom Tickets

Reusing a Task Chain Ticket to Build a Workflow

Building a

Nested Workflow

Note:

Save your workflow if you want to be able to reuse it later.

Any settings change you make after saving your workflow will only be used on this file and not saved in the ticket.

Click the Launch button.

Tip: Hold Alt while clicking Launch to keep the workflow editor window open to monitor your workflow (the Launch button shows an eye ).

7.2.3 Pausing or Cancelling Your Workflow

While monitoring your file’s progress in the workflow editor window, you can:

• click to pause your workflow (at the end of the task currently running),

• click to make your workflow run again,

• click to cancel your workflow’s processing.

123

Automation Engine

7.3 Checking the Workflow's Processing Status

In the Pilot's Tasks Pane

After launching a workflow on one or several file(s), you can check the processing status in the Pilot’s

Tasks pane. You can see the Tasks pane in the Files, Product or Tasks views.

You can see the progress (in percentage) and the processing state. The state can be:

•

: starting

: success

•

: warning

•

: failure

•

: processing cancelled

In the Workflow Editor

Double-click the Workflow entry in the Pilot’s Tasks pane to open your workflow in the workflow editor.

124

Automation Engine

You can see your file(s) going from task to task, with the status displayed in blue.

Note: The file icon can represent a single file or a collection of related files, depending on your workflow step’s output.

Each task or workflow control indicates the number of files ran successfully (in green) or with an error (in red) through it.

125

Automation Engine

You can also:

•

Open a processed file in the Tasks view: right-click the file (if it is still being processed) or the step

output widget

(if processing is finished) and select Show in Tasks View.

• Open the output of a step in the Files view: right-click the step's output widget and select Show in Files View.

• Check all public parameter values used in this workflow: go to Advanced > Modify Public

Parameter Values... (see

Checking All the Workflow's Public Parameters Values

for details).

•

See Details (stranded files...) by clicking .

• See the To-Do list (Checkpoints, Milestone Actions...) associated with the workflow by clicking

7.4 Re-launching Your Workflow with Different Settings

1. Double-click the Workflow entry in the Pilot’s Tasks pane to open your workflow in the workflow editor.

2. In the workflow editor window, double-click the task(s) you want to edit and change the settings as necessary.

Note: Save the workflow if you want to keep the new settings in the ticket.

Click Launch .

126

Automation Engine

8. Viewing Files in the Automation Engine

Viewer

8.1 About the Viewer

What is the Automation Engine Viewer?

The Automation Engine Viewer is a comprehensive, powerful and integrated Viewer and QA tool.

It can easily be integrated in your Automation Engine workflow, to view, check and compare graphic production data.

It can be launched directly from within the Automation Engine Pilot, on any Macintosh or Windows

PC in your network. Anywhere you can install and log on to an Automation Engine Pilot you can start the Automation Engine Viewer (DTP, prepress, QA department, CSR desk...).

You can use as many Automation Engine Viewers as you have Automation Engine Pilot connections.

Opening the Automation Engine Viewer does not allocate an extra Pilot connection.

It is even possible to have two or more Automation Engine Viewers on one workstation by opening a second Automation Engine Pilot (Pilot - File menu - New window) and opening a file in the Automation

Engine Viewer from there.

If you are an Esko Bitmap Viewer user, you will notice that the interface and shortcuts are nearly identical.

What does the Viewer offer you?

• Reliability: Showing the data in a correct way. At best in the same way the RIP / Proofer will see them.

• Detail: Unlimited zoom, high detail measuring, measuring traps and exact distances (die objects).

• Speed: Opening files swiftly, even when it concerns large files. Fast zooming.

Prepared View Data

Reliability is a must. Detail can also not be compromised, it is always offered. The challenge lies in opening very large files quickly. That is why the Automation Engine Viewer offers 2 view modes: with or without Prepared View Data.

• In case you do not prepare View Data, the server will stream the data to the Automation Engine

Viewer. When a large file has to be opened or compared or when the server is very busy, a delay can be noticed. Deep zoom detail mode is immediately available.

• In case you do opt to prepare View Data in advance, then the Viewer will show you the prepared

View Data instantly. Zooming in will of course require object data streaming from the server, but then for a smaller area.

For more information about creating View Data, see

Prepare for Viewer

(in the Automation Engine

Reference Manual).

127

Automation Engine

8.2 Checking the Result in the Viewer

The Automation Engine Viewer can open different file types (PDF, AI, PSD...). For a full list, see

Supported File Types

in the Reference Manual.

In the Files view, you can easily view different types of files using viewer. However, the viewing privileges depend upon the specified user rights.

Note: If the the user access right for deep zoom is not enabled (read more here

Defining User Access

Rights

)while defining user rights:

• you can only view prepared files

• your zoom is restricted.

You can now zoom in on the file, measure distances and densities, view separations individually or together, etc.

8.3 Comparing Files

The Automation Engine Viewer is not only a powerful viewing tool, but also holds a strong compare tool. It is an ideal way to compare two files and have a close look at the differences, if needed per separation, including changes in images (internal or referenced images).

128

Automation Engine

1: The names of the two files that you are comparing

2: Enable difference view - to activate the Compare tool

129

Automation Engine

3: View both - highlight the difference: the differences between the two files is highlighted in red.

Right-click this button to see the other options for compare that are available.

While comparing you can also use other tools like for example "view separations in separate windows", measure, (de)select, rotate, etc...

1: Show channels (Automatic tiling) - Right-click this button to see the other options that are available to see the different channels.

130

Automation Engine

9. Integration with Other Applications

9.1 Integration with WebCenter

With the Approval Workflow, you can send documents to be approved from Automation Engine to

WebCenter, approve them in WebCenter and see the results back in your Pilot.

This allows you to collaborate with your colleagues and customers for maximum efficiency and minimum error.

9.1.1 WebCenter Setup

In WebCenter, you need to set up a Project Template with Approvers.

You will use this template in Automation Engine when sending impositions: it will allow you to create new WebCenter Projects (already containing your Approvers) as needed, directly from Automation

Engine.

Note: Alternatively, you can set up a WebCenter Project with Approvers in WebCenter, and send your impositions to it from Automation Engine. But then you will only be able to create new Projects from WebCenter and not from Automation Engine.

1. Create a new Project.

2. Add Members to the project.

3. Choose Approvers from within the Project’s members.

4. Save the Project as a Template.

Creating a New Project

1. Log in to WebCenter as a user who is a Project Manager.

2. Click Projects.

The Favorite Projects page is shown.

3. Click Create New Project at the top right of the page.

4. Choose Start from a Blank Project and click Continue.

5. Enter the name for the Project in the Project Name field.

• To make another user or user group the Project Manager for this project, select his or her name, or the group name, from the Project Manager list.

• If desired, enter a description in the Description field.

• To make the Project active, set the Status as Active.

131

Automation Engine

• To specify an optional due date, click the calendar control at the end of the Due On field and select the desired due date. To set the due time, click the drop-down list box to the right of the calendar control.

Note: This is not the Approval Due Date. You will set the Approval Due Date when setting the Approval Cycle.

• To use a custom thumbnail, click Change and enter the complete path and filename in the associated field or Browse for it. To use the default thumbnail, leave that choice selected.

6. Click Create Project.

The Project is created.

Adding Members to a Project

1. Once the project is created, click Members > Add Members .

132

This shows a list of the current WebCenter members.

2. Select the users or groups to add as members and click Continue.

Automation Engine

3. Set the members’ permissions as desired. For Approval tasks, members need at least View permissions (selected by default).

Note: The permissions you set here apply to all members you have just added.

4. Click Finish.

5. Once the members are added, click Go back to the project.

Adding Approvers to the Project

Approvers can be either regular users or they can be user groups.

When you add a group as an approver, you must indicate whether:

• all the members of the group (select the group entry labeled as whole group

) must approve the document before it gets the approved status, or

• whether the approval of a single group member (select the group entry labeled as one of group

) will set the document to approved status.

Note: You can only change (add or remove) Approvers when the Approval Cycle is stopped.

1. In the Project Page, click Approval.

133

Automation Engine

2. Click Setup Approval.

3. Open the Add approver list, and select the individual users or the groups you want to add.

Tip: Use Ctrl+Click to select multiple members.

Note: The Project Manager is not automatically made an Approval User and must be explicitly added to the list of Approvers.

134

Saving a Project as a Template

Note: To save a Project as a Template, you need have Administrator permissions.

1. If the user you are logged in with is not an Administrator: a) Log out.

b) Log back in with an Administrator user.

c) Go back to your Project page.

2. In the More actions menu on the left, click Save as Template.

Automation Engine

3. Enter the Template Name (different from your Project Name) and a Description.

To use a custom thumbnail, click Specify New Thumbnail and enter the complete path and filename in the associated field or Browse for it. To use the default thumbnail, leave that choice selected.

4. Click Finish.

The Template is created.

9.1.2 Automation Engine Setup

1. In the Automation Engine Pilot, go to Tools > Configure.

2. In the left panel, select Webcenter Sites at the bottom of the list.

3. Go to File > New or use the Insert key (on Windows only).

135

Automation Engine

136

4. Enter your WebCenter server address in Website.

Note: You can use the Open button to open your WebCenter website.

5. Check if your Webcenter and your Automation Engine servers are on the same Local Area

Network:

• If they are, enable Webcenter and Automation Engine are in the same LAN,

Note: Your Webcenter and Automation Engine servers must be on the same Local Area

Network to be able to use the page list approval feature in WebCenter.

• If they are not, enter the Automation Engine Approval Client’s Name and Password.

Note: The Name and Password you enter here must match the Workflow Approval Client’s

Name and Password specified in WebCenter by the WebCenter administrator.

6. Use the Check Connection button to check that your Automation Engine server is now connected to your Webcenter server.

7. In the left panel, select the WebCenter connection you have just set up and click on it to rename it. You can also use File > Rename or F12 (on Windows).

8. Go to File > Save to save your WebCenter connection. You can also use Ctrl + S on Windows or Command + S on Mac.

Automation Engine

Note: To remove a WebCenter connection, select it in the left panel and go to File > Delete or use the Delete key.

9.1.3 Sending an Imposition from Automation Engine to WebCenter

Preparing the Imposition

1. In the Files view, browse to the FastImpose imposition file (

*.imp

) you want to upload.

Note: The imposition file must be part of a job.

2. Right-click it and select Add to Imposition Gallery from the context menu.

When you switch to the Pages view, you can see your file in the Imposition Gallery.

3. If the imposition doesn’t show the pages preview (as in the example above), add them this way: a) Click on the first page’s file name in the Page Gallery. This shows the page’s preview in the

Details area at right.

b) Drag this preview onto the first page of the imposition in the Page list area.

c) Repeat this for the other pages of your imposition.

137

Automation Engine

138

Sending the Imposition to WebCenter

If your imposition contains several books, you must send the books one by one to WebCenter. Each book will be shown as a Page List in WebCenter.

1. In the Imposition Gallery, right-click the imposition (or the book) and select New Task > Prepare

Imposition for WebCenter Workflow.

If the Prepare Imposition for WebCenter Workflow task does not appear in the context menu, choose More Tickets and select the task in the Select Ticket dialog.

2. Modify the settings of the Prepare Imposition for WebCenter step (the first step in the chain) if needed.

3. In the Send Imposition to WebCenter step, modify the settings of the Destination tab (you can use SmartNames where indicated by the SmartNames button ): a) Select your WebCenter Site from the list.

b) Enter the name to give to your Project. Automation Engine will create this project in WebCenter, from the Project Template you specify below.

Automation Engine

Note: You can also send your imposition to a Project already existing in WebCenter. In that case, you don’t need to enter a Project Template. Note that this Project must have Approvers defined in WebCenter.

c) If you want to send your imposition to a subfolder in the project, enter that Folder’s name. If this folder doesn’t exist in the template (or project), Automation Engine will create it.

d) Enter the name to give to your imposition Document. This is the name that will be shown in

WebCenter. For example you can use

[ImpositionName][BookName][LayerName]

e) Enter the Project Template to use to create your WebCenter project.

Important: This Project Template must be defined in WebCenter. See

WebCenter Setup

f) Enter the User Name and Password used to connect to your WebCenter site. You can use an

Encrypted password or SmartNames.

139

Automation Engine

140

4. Modify the settings of the Approval tab: a) Enable Start the Approval Cycle.

b) Select a Due date and time.

Automation Engine

5. Click the Launch button in the top left corner to upload the imposition to WebCenter.

Note:

If you don’t start the Approval Cycle from Automation Engine, you will still be able to start it from

WebCenter, and view the approval results in Automation Engine.

For more information, see the WebCenter manual.

9.1.4 Approving the Imposition in WebCenter

In WebCenter 7.1, you can:

• Approve / reject documents sent from Odystar, Nexus or Automation Engine as regular documents (see

Approving a Document

• Approve / reject documents FastImpose impositions added to the Pages View in Automation

Engine as regular documents or Page Lists (see

About Page Lists

and

Approving a Page List

When approving a Page List, you can:

• Approve / reject not only the whole multipage imposition but each individual page.

• Update and have version control not only on the whole multipage imposition but on each individual page.

Note: Only FastImpose impositions that have been added to the Pages View in Automation Engine are recognized as Page Lists in WebCenter. Multipage files uploaded from within WebCenter, or from

Odystar, Nexus, or even other Automation Engine documents will never be treated as Page Lists.

Instead, they are considered regular multipage PDF documents.

141

Automation Engine

When approving a Document, you can:

• If you are an Approval User:

Approve

the document, Reject it, or leave it

Pending

to approve / reject it in the future.

• If you are a Project Manager:

Approve

or Reject the document, leave it

Pending

, or Force

Approve / Force Reject it if you need to overrule the approval status granted by the approval users.

Note:

For more information about Forced Approval or Rejection, see the WebCenter manual.

Approving a Document

Documents waiting for your approval are shown on My To Do List under My Work. If you are an

Approval User, do the following to Approve or Reject a document:

Note:

You can also approve or reject documents in the Viewer.

1. Click Approve/Reject at the end of the Approval field in the document header.

142

2. Choose the desired Approval Status from the drop-down list:

Approved

indicates approval;

Pending

indicates future Approval or Rejection, and

Rejected

indicates disapproval.

3. Once you choose Approved or Rejected, you may not change the status later; a view-only version of the page will be shown showing the choice you picked. Only a Pending status allows future changes.

If desired, you can add a comment in the Comment field. Submitted approvals and comments are shown on the Action History page.

4. Click Finish to change the status of the document.

To cancel the changes, navigate to another page without clicking Finish.

About Page Lists

What is a Page List document?

Page Lists are a special type of multipage PDF documents in WebCenter that represent imposed books or magazines. As such they are an important tool for commercial printers.

Automation Engine

Page Lists are uploaded from a Automation Engine production server using the Pages View in the

Automation Engine Pilot.

Note: Only FastImpose impositions that have been added to the Pages View in Automation Engine are recognized as Page Lists in WebCenter. Multipage files uploaded from within WebCenter, or from

Odystar, Nexus, or even other Automation Engine documents will never be treated as Page Lists.

Instead, they are considered regular multipage PDF documents.

Page List documents have two major advantages over other multipage PDF files:

• You can upload either the complete document, or specific pages only (for example, pages 6-12);

• individual pages can be approved or rejected in WebCenter (for example, you can approve pages 3, 5 and 7-16 of a 16-page Page List).

Note: A multipage PDF file can only be approved or rejected as a whole.

Working with Page Lists

Page List documents are displayed as a single document in document lists. Click the Page List name to view its pages and details in the dedicated Page List views.

Note: Page Lists cannot be downloaded.

Approving a Page List

In order to approve your imposition as a Page List in WebCenter, you need to first login to WebCenter as an approver, then navigate to the document (Page List) to approve, in the project created from

Automation Engine.

You can also access this Page List from the link in the approval notification email, if you received one.

Make sure you have the correct permissions to approve documents in WebCenter. For more information, please see your WebCenter manual.

You can choose from a number of different methods to approve the pages in a Page List:

• Use the WebCenter Viewer: a) In the Project, click on the Page List’s thumbnail image. The Viewer opens, displaying the

Page List.

b) In the Approval area in the sidebar on the right of the Viewer window, select the appropriate approval state (Approved, Rejected, Pending) from the list.

The Approval dialog opens in which you can add approval comments.

143

Automation Engine c) Enter your comments, provide your password if required and click Commit.

Note: You can approve / reject one page at a time, or all of the document’s pages (using

Apply to all pages).

• Use the Page Gallery view: a) In the Project, click on the Page List’s name.

The Document Details page appears.

b) Select Page Gallery from the menu.

c) Select the pages you want to approve and then click Approve/Reject. You can also use

Approve/Reject all Pages.

144 d) Enter your comments, provide your password if required and click Commit.

Automation Engine

• Use the Page List view: a) In the Project, click on the Page List’s name.

The Document Details page appears.

b) Select Page List from the menu.

c) Select the pages you want to approve and then select Approve/Reject from the gearbox menu.

You can also use Approve/Reject all Pages.

9 d) Enter your comments, provide your password if required and click Commit.

• Use the Approve/Reject link on the Document properties page to approve all the pages at once.

145

Automation Engine a) Enter your comments, provide your password if required and click Commit.

9.1.5 Checking the Approval Results in Automation Engine

• To view the status of documents in a WebCenter Approval Cycle in Automation Engine, you can use either:

• the Pages View,

• the Proofs View,

• the WebCenter View.

In the Pages and Proofs Views

• Go to the Pages or Proofs View to view the approval status of each page of the imposition.

• In the Pages View:

146

• In the Proofs View:

Automation Engine

Note:

When you try to expose a sheet that contains a rejected page, you will get an error in the

Expose task and an error status in the Plates View.

If you really need to expose the sheet anyway, you can overrule the WebCenter approval status from Automation Engine (see

Overruling the WebCenter Approval

In the WebCenter View

In the WebCenter View, you can view the approval status of the whole imposition.

Important: You need to first set up the WebCenter View before you can view all the approved / rejected documents in the WebCenter project you created.

1. Right click the WebCenter View’s background and choose Configure.

2. Enter the URL of your WebCenter site.

3. Enter the User name and Password used to connect to your WebCenter site.

4. In Project Name, enter the name of the WebCenter project you sent your imposition to. You can use SmartNames.

Important: Make sure this matches the Project Name of the project you created (or used) when sending your imposition from Automation Engine to WebCenter. See

Sending the Imposition to

WebCenter

5. To check that the information you entered is correct and that the WebCenter server is running, click the Retry Connection button at the bottom of the view.

You can also use the link at the top of the view to open the web page of the WebCenter project.

6. Once you have checked that your configuration is correct, use the Save to Configuration button to save it.

147

Automation Engine

Once it is saved, you will be able to return to this configuration using the Load from Configuration button after any unwanted change.

7. Click the Show Documents button to view the documents in your WebCenter project.

148

Automation Engine

Note: If at least one page of the imposition is rejected, the status of the whole imposition is Rejected.

Possible Document Statuses

This icon...

means that...

the page and the original imposition layout have been approved by all approvers.

Note: The imposition layout can be approved even if some of its pages are rejected.

the page has been approved by all approvers, but it may have changed the imposition layout, which needs to be checked (for example for a new page replacing a rejected one).

the page or the whole imposition has been rejected by at least one approver.

the page or the whole imposition has yet to be approved or rejected by at least one approver.

149

Automation Engine

When you hover on the top of a page in the Pages or Proofs View, you can see:

• the approval status,

• any comment entered,

• the date and time of the approval,

• the WebCenter user who approved/rejected the page.

9.1.6 Overruling the WebCenter Approval

After your imposition has been approved or rejected in WebCenter, you can still overrule the approval status of some of the pages in Automation Engine, if necessary.

1. In Automation Engine Pilot, go to either the Pages or the Proofs View and locate your imposition document.

2. You can either:

•

Select a page of your document and use the and to approve/reject the document without entering a comment.

buttons in the View’s toolbar

• Right-click on a page of your document and choose Approve/Reject... to open the Approve/

Reject dialog where you can enter a comment.

3. In the Approve/Reject dialog, select Manual as Approval Type.

150

Automation Engine

4. Choose to either:

• Approve,

• Approve with warning,

• Reject the document.

5. Enter a Comment if you wish and click OK.

Note: You can hover on the top of a page to view approval information, whether it has been approved/ rejected automatically in WebCenter, or manually in Automation Engine.

9.2 Integration with Nexus

Why run Nexus workflows from the Automation Engine Pilot?

You can use all the power of Nexus workflows from within a Automation Engine Job. This allows you to bring both Automation Engine and Nexus workflows in line, running them from within a single controlling environment: the Automation Engine Pilot.

How does it work?

The Send to Nexus ticket gives you access to the workflows that are available on a specific Nexus server.

151

Automation Engine

Any public parameters that have been defined in the Nexus workflow (NeXML) will show up on the

Send to Nexus ticket in Automation Engine. In addition, these public parameters are SmartNameenabled, so you can use Job metadata to drive the Nexus workflows.

On the Nexus side the Copy to BackStage activity allows you to set up workflows that send their resulting files back to Automation Engine.

Behind the scenes, Automation Engine and Nexus communicate via the SOAP protocol, exchanging files and notifying each of other of their progress.

NeXML

Setting up public parameters in Nexus requires knowledge of NeXML. Please refer to the NeXML

Manual for more information.

9.2.1 Setup on the Nexus Side

To enable the Automation Engine Pilot to launch Nexus workflows, you must perform a number of setup tasks on the Nexus server.

Mounting Your Containers on the Nexus Server

The Automation Engine containers have to be mounted on the Nexus server.

• If the Nexus server runs on a Windows OS, the container should be mapped to a drive letter on the operating system.

• If the Nexus server runs on a Mac OS, the container has to be mounted over the SMB protocol.

Setting up the Nexus SOAP Server and Workflows

1. In the Modules list, double-click the NexusSoapServer module.

2. Enter a port number in the Listening Port field of the NexusSoapServer Module Defaults dialog, and click OK.

The Nexus SOAP server is now active.

Note:

The option User Management, which determines the workflows that a particular user can access, is ignored by the Automation Engine Pilot. As a result, Automation Engine Pilot operators automatically have access to all Nexus workflows.

3. Create valid Nexus workflows with the Input Type: Hot Folder.

4. Configure the Hot Folder queues for the workflows. Make sure the option Show in Shuttle is selected.

Only Hot Folders that have Show in Shuttle enabled are published to the Nexus SOAP server and become accessible to the Automation Engine Pilot.

5. Create the workflows with the Nexus Workflow Editor.

6. Make sure you add the Copy to BackStage activity at the end of the workflow.

152

Automation Engine

Your Nexus workflow is now available for use with the Automation Engine Pilot.

9.2.2 Setup on the Automation Engine Side

1. In the Pilot, go to Tools > Configure and select the Nexus category.

2. Click File > New .

3. Enter the name of the Nexus server in the Host field.

4. Enter the Port on which the Nexus server is accessible.

5. Click Test Connection to verify the settings you entered.

Note: You can also test whether the Nexus SoapServer is online by browsing to the following url in your favorite web browser: http://NexusServerName:5182

9.2.3 Running a Nexus Workflow from the Pilot

To run a Nexus workflow from within the Automation Engine Pilot, you can use the Send to Nexus ticket.

Additional integration features allow you to check the progress of the workflow in the Automation

Engine Task Monitor, to jump to the workflow in Nexus Manager, and more.

Understanding the Send to Nexus Ticket

The Send to Nexus ticket consists of two parts:

• the top section of the ticket dialog is always the same, and allows you to:

• select a particular Nexus workflow from the Workflow list;

• indicate whether you want to launch a new, separate workflow in Nexus for every file you select in the Pilot (Separate Tasks), or whether you want to send all the selected files to one Nexus workflow (One Single Task).

• the bottom section of the ticket dialog contains fields for the public parameters for the workflow you selected. These parameters can be different for every Nexus workflow (they are defined using

NeXML).

153

Automation Engine

154

Note: You can also manage your Nexus workflow's public parameters (not one by one but as a group) in your task ticket. See

Managing Public Parameters in Your Ticket

Launching a Nexus Workflow from the Pilot

1. In the Pilot, select the file(s) you want to process with your Nexus workflow.

2. Launch the Send to Nexus task.

3. Select the Workflow you want to run.

4. If you selected multiple files:

• select One Single Task to send all the files to a single workflow in Nexus.

• select Separate Tasks to launch a separate Nexus workflow for every selected file.

5. Provide the required public parameters for the different activities in the workflow.

Note: You can use SmartNames in all the public parameter fields.

6. Click Launch to send the files to the Nexus workflow.

Automation Engine

The Send to Nexus task appears in the Task List, where you can see the progress of the Nexus workflow. Note that progress is not displayed in real time.

The processed files from Nexus are returned to Automation Engine as the output of the Send to

Nexus task. In other words, you can include Send to Nexus as a step into a more complete workflow.

Switching Between Automation Engine and Nexus

• In the Automation Engine Pilot: in the Task List, right-click on the Send to Nexus task and choose

Go To Job in Nexus Manager to view the job in Nexus Manager (this command is only available on Mac OS).

• In Nexus Manager, double-click the Copy to BackStage activity to view the job in the Automation

Engine Pilot.

Note: In order to jump from the Nexus Manager 9.0 to the Automation Engine Pilot, you must connect to Nexus Manager with a blank user name and the password awsnexus

9.3 Integration with Odystar

Why Run Odystar Workflows from the Automation Engine Pilot?

You can use all the power of Odystar workflows from within a Automation Engine Job. This allows you to bring both Automation Engine and Odystar workflows in line, running them from within a single controlling environment: the Automation Engine Pilot.

How Does it Work?

The Send to Odystar ticket gives you access to the workflows that are available on a specific Odystar server. You can use the Send to Odystar ticket as a single task or as part of a more complete

Automation Engine workflow.

Any public parameters that have been defined in the Odystar workflow will show up in the Send to

Odystar ticket in Automation Engine. In addition, these public parameters are SmartName-enabled, so you can use Job metadata to drive the Odystar workflows.

On the Odystar side the Copy File gateway allows you to set up workflows that send their resulting files back to Automation Engine.

Behind the scenes, Automation Engine and Odystar exchange files and notify each of other of their progress.

Example

• The Automation Engine workflow (top) sends the files to Odystar for additional processing before outputting them to a proofer.

• The Odystar workflow (bottom) applies PrePress changes to the files before copying them back to Automation Engine, where they go through the rest of the workflow (Proof step).

155

Automation Engine

Note:

Odystar accepts Normalized PDF files as input, but its changes may render the files non-Normalized.

We suggest that you do either (or both) of the following:

• send regular (not Normalized) PDFs to Odystar (add an Export to PDF File step before Send to

Odystar),

• re-normalize the files you get back from Odystar (add a Normalize PostScript / PDF / Illustrator

8.0 File step after Send to Odystar).

9.3.1 Setup on the Odystar Side

To enable the Automation Engine Pilot to launch Odystar workflows, you must perform a number of setup tasks on the Odystar server.

Mounting Your Containers on the Odystar Server

• Mount the Automation Engine containers on your Odystar server using the SMB protocol.

156

Automation Engine

Note: Make sure you have Read and Write permissions for those mounted volumes from your

Odystar server machine.

Setting up the Hub and Your Odystar Canvases

1. On your Odystar server, launch the Hub application. You can find it in Odystar’s Server Software folder.

2. Go to Hub > Preferences.

You can also use the shortcut Command + , (comma).

3. In the Shuttle tab, enter the IP Address of the server running your Hub, and the port to use for communication between Automation Engine and the Hub (in Shuttle Port).

Note: By default this is port 5182, but if this port is already used by other processes, you should enter the next available port.

4. Create your Odystar workflow using the Inspector.

5. Double-click the Receive Process Folder of your Odystar workflow to open its parameters.

6. In the Shuttle tab, click Enable Shuttle Queue.

157

Automation Engine

158

7. Make sure you add a Copy File gateway, with the Copy Back To Automation Engine mode selected, at the end of your workflow.

Automation Engine

Your Odystar workflow is now available for use from the Automation Engine Pilot.

9.3.2 Setup on the Automation Engine Side

1. In the Pilot, go to Tools > Configure and select the Odystar category.

2. Click File > New.

3. Enter the name or IP address of the Odystar server in the Host field.

4. Enter the Port on which the Odystar server is accessible.

5. Click Test Connection to verify the settings you entered.

159

Automation Engine

Note: You can also test whether the Odystar Hub is online by browsing to the following url in your favorite web browser: http://OdystarServerNameorAddress:5182

9.3.3 Running an Odystar Workflow from the Pilot

To run an Odystar workflow from within the Automation Engine Pilot, you can use the Send to Odystar ticket. You can use it as a single task or as part of a more complete Automation Engine workflow.

You can also check the progress of the Odystar workflow in the Automation Engine Task Monitor.

Understanding the Send to Odystar Ticket

The Send to Odystar ticket consists of two parts:

• the top section of the ticket dialog is always the same, and allows you to:

• select a particular Odystar workflow from the Workflow list;

Tip: If you can’t see the workflow you are looking for, use the refresh button .

• indicate whether you want to launch a new, separate workflow in Odystar for every file you select in the Pilot (Separate Tasks), or whether you want to send all the selected files to one

Odystar workflow (One Single Task).

• the bottom section of the ticket dialog contains fields for the public parameters for the workflow you selected. These parameters can be different for every Odystar workflow (they are defined in the Inspector).

Note: You can also manage your Odystar workflow’s public parameters (not one by one but as a group) in your task ticket. See

Managing Public Parameters in Your Ticket

160

Automation Engine

161

Automation Engine

Launching an Odystar Workflow with the Send to Odystar Task

1. In the Pilot, select the file(s) you want to process with your Odystar workflow.

2. Launch the Send to Odystar task.

3. Select the Workflow you want to run.

4. If you selected multiple files:

• select One Single Task to send all the files to a single workflow in Odystar.

• select Separate Tasks to launch a separate Odystar workflow for every selected file.

5. Provide the required public parameters for the different gateways in the workflow.

Note: You can use SmartNames in all the public parameter fields.

6. Click Launch to send the files to the Odystar workflow.

The Send to Odystar task appears in the Task List, where you can see the progress of the Odystar workflow. Note that progress is not displayed in real time.

Note: The files processed by Odystar are returned to Automation Engine as the output of the Send to Odystar task (or as the output of the Send to Odystar workflow step when including the Send to

Odystar ticket in an Automation Engine workflow - see the workflow

example

9.4 Integration with i-cut Suite

The i-cut Automate module in Automation Engine offers similar functionality to i-cut Layout, but in a workflow environment, requiring mininal manual intervention.

It is RIP and device independent.

It consists of four tasks:

• Prepare Graphics for Nesting, to extract graphics contours from graphic files using a cut path.

• Add Parameters for Nesting, to specify nesting parameters for a particular graphic.

• Create Nested Layouts, to nest a set of graphics onto one or more sheets, and create production files.

• Create Tiles, tile very big graphics into smaller graphics to be printed.

See the Reference Guide for a detailed explanation of the tasks' parameters.

9.4.1 i-cut Automate Workflow

You can combine the i-cut Automate tasks into a workflow to fit your needs. For example in the workflow below:

1. The input files are copied to your FileStore.

2. In the Prepare Graphics for Nesting task, a cut path is created from the contour of the graphics on the white background, and the graphics are extracted from their backgrounds.

162

Automation Engine

3. In the Add Parameters for Nesting task, the graphics are set to be repeated to fill the sheet (with the Maximum fill option).

4. The Data Collector makes sure the graphics arrive to the Create Nested Layout task all at once, so they are combined in same set of sheets.

5. The Create Nested Layout task creates the nesting on the substrate and with the parameters you define (margins, fill starting point, gutter, etc.).

6. The production files (print files and cut files), and if desired a nesting report, are created and sent to the location you define.

Tip:

If the Minimum Fill on the sheet isn't reached on the due date, you can for example send the remaining graphics to another Create Nested Layout task with a lower minimum fill percentage (or see Create Nested Layout in the Reference Guide for more options).

9.5 Integration with Enfocus PitStop

You can integrate Enfocus PitStop with Automation Engine, to be able to preflight PDF files from the Pilot.

To preflight a file:

163

Automation Engine

1. Go to Tools > Configure and set up the connection to PitStop (see Preflight Tools in the Reference

Guide for more details).

2. Launch the Preflight via External Application task on your file (see Preflight via External

Application in the Reference Guide for more details).

9.6 Integration with third party applications using Hot

Folders

The Integrate via External Hot Folder task allows you to integrate external prepress applications into your workflow tickets. The only requirement is that the external system works with hot folders.

1. In the Integrate via External Hot Folder ticket, you define the location of the hot folder used by the external application, as well as the Result subfolders in which the external application will output processed jobs (the OK Folder), failed jobs (Error Folder) or jobs that produced warnings

(Warnings Folder).

2. When you process a job with this ticket, Automation Engine copies the files to the external hot folder.

3. The external application picks up the files in its hot folder and processes them. The processed files are saved in the subfolder that matches the processing result: OK, Warning or Error.

4. Automation Engine monitors the OK, Warning and Error folders for any files that have been processed.

5. If it detects a file in the OK folder, Automation Engine copies it to the Output folder defined in the

Integrate via External Hot Folder ticket, and continues its workflow. Depending on your settings,

Error or Warning files might also be copied into the Output folder, or they might be deleted.

164

Automation Engine

165

Automation Engine

Note: In the Error area of the ticket, you can define an amount of time after which the external processing should be considered as failed. To do this, enable the option Error when no result after ...

and define a time period (for example, you could enter one hour, a number of days, or even a specific date).

9.7 Integration with MIS Systems

Automation Engine supports tight integration with your MIS system.

You can:

• Take advantage of all the information the MIS system can hold (for example, you can retrieve customer information, or link MIS jobs to Automation Engine products to better serve your customers).

• Plan and trigger production through MIS to Automation Engine communication (for example, you can trigger job creation in Automation Engine from the MIS, or plan plates production...).

9.7.1 About JDF and MIS Integration

MIS and Automation Engine communicate via JDF/JMF.

You should set up a JDF hot folder, where:

• the MIS will send JDF files that will automatically start tasks that you defined,

• Automation Engine will write the processing result for the MIS.

Creating a JDF Hot Folder

1. Either:

• click the Hot Folders view in the Views bar,

• go to Go > Hot Folders,

• use CTRL + SHIFT + H.

Click the Create New Hot Folder button .

3. In the dialog that opens, select JDF Hot Folder and click OK.

166

Automation Engine

4. In the Select Folder dialog, browse to the folder you want to turn into a Hot Folder (or create a new folder with ) and click OK.

Note: You cannot select folders that are already Hot Folders ( ).

5. In the New Hot Folder dialog, select an Output Folder (where Automation Engine will write the processing result).

167

6. Click OK.

The JDF Hot Folder is now listed in the Pilot’s Hot Folder View.

Automation Engine

168

Automation Engine

10. PDF Normalization in Automation

Engine

This section explains the improvements in Automation Engine 12 with regards to the normalization of PDF documents.

Normalization in Automation Engine 10

In Automation Engine 10 and older versions, PDF files had to be normalized at the start of a workflow before any further processing could take place.

With the release of Automation Engine, 10.1 new PDF processing tasks were introduced that can handle incoming PDF files without the need for normalization. However, these tasks could not process normalized PDF files. On top of this the PDFs produced by these tasks needed to be normalized before they can be handled by other tasks. As a consequence, it was not straightforward to build workflows that used a combination of these tasks.

Improvements from Automation Engine 12 onwards

In Automation Engine 12, the collection of PDF processing tasks that do not require normalization was extended. To avoid that the user needs to carefully consider which tasks require normalized PDF as input when building workflows 2 features were introduced in Automation Engine 12:

• Tasks that do not require normalized PDF (the new ones added in Automation Engine 12 and the ones that were added in Automation Engine 10.1) can now also handle normalized PDF, and keep the files normalized.

• Tasks that require PDF files to be normalized will now do this automatically without the need to introduce explicit normalization tasks in a workflow.

10.1 What Makes a Normalized PDF Special?

Normalized PDFs are to a large extent regular PDF 1.6 files, except in a number of specific areas.

Overview

Normalized PDF differs from regular PDF 1.6 in the following areas:

• External references

• Color space

• Document level metadata

• Object level metadata

External references

A Normalized PDF is not always self-contained. It can refer to images or other PDFs that are not embedded in the PDF itself. Making use of references instead of embedding images and/or graphics can have several advantages in the workflow. The main advantage is that it allows for “late binding” e.g. an image can be color corrected. After the color correction all PDFs that refer to this image will automatically contain the corrected version of the image without the need to open and rewrite

169

Automation Engine all those PDFs. Working with Normalized PDFs with external referenced can also lead to faster processing especially when the Normalized PDF refers to large amounts of external image data.

Although referring to external files is a standard PDF feature (e.g. used in the PDF/X-5), most

PDF applications do not support this. To guarantee that a PDF can be processed correctly by

PDF application (like Adobe Acrobat) it has to be made self-contained (embedding all the referred components like images). A self-contained Normalized PDF is 100% PDF compatible.

Color space

A Normalized PDF can only contain objects in the final printing color space. This final printing color space can have any number of separations but in most cases this will be CMYK and some spot colors. The PDF object model allows objects to be defined in RGB and CIE based color spaces. This is not possible in Normalized PDF. During normalization such objects are color converted to CMYK.

The fact that Normalized PDF can’t contain objects in RGB or CIE based color spaces its biggest limitation. On the positive side it makes the workflow more predictable. It avoids late and often somewhat hidden color conversions e.g. in the RIP that can lead to problems in printing.

Document level metadata

A Normalized PDF contains XMP metadata. The schema of the XMP data is Esko specific, but the specification is public. The XMP metadata serves 2 purposes. It contains info about the file that can be extracted by 3th party applications and used e.g. for quality control or asset management. The

XMP metadata are also used by Esko applications like Automation Engine to retrieve information from a PDF (e.g. the number of separations) in an efficient way.

Object level metadata

A Normalized PDF contains metadata for specific objects like barcodes. Object level metadata are added to allow modification of those objects using an Esko application. Object level metadata are stored using a proprietary mechanism and format.

10.2 Which Tasks Require PDF Normalization?

The following is an exhaustive list of the Automation Engine tasks that require normalization of PDF documents.

The table below lists the tasks that require normalization (Normalized PDF tasks) and the tasks that do not require normalization (PDF tasks). The exact list of tasks available on your Automation Engine server depends on the licenses you have, so some tasks in the list below may not be visible in your

Automation Engine Pilot.

Normalized PDF Tasks

Add Ink Eaters

Check Job Parameters

Check Print Rules (PRC)

Convert CMYK Colors

Convert Colors

Create Design (DesignWizard)

Create PAF/JPG/XML (LinkEdge)

Create Report (ReportMaker)

PDF Tasks

Adjust PDF Screening

Compare PDF

Create PDF File from RunList

Extract Inks

Optimize PDF Document

Optimize PDF Separations

Preflight with Pitstop

Process PDF Spreads

170

Automation Engine

Normalized PDF Tasks

Enrich Black

Export to 3D

Export to ArtPro File

Export to EPS/DCS File

Export to PDF File

Export to PostScript File

Export to VRML File

FastVariants (all tasks)

Optimize and Clean (PSFix)

Outline Fonts

PowerTrapper

Prepare Station

RIP (all tasks)

Step & Repeat (all tasks)

Trap (all tasks)

PDF Tasks

Resize PDF for Output

Resolve OPI

Split Pages

Version PDF

10.3 How do PDF Tasks Work with Normalized PDF

Files?

The example workflow described here takes a 1-up, removes the separation called “Cut” and traps the file. It can be used with both Normalized and regular PDF documents. In this topic, we take a look at how Automation Engine processes a Normalized PDF input file in this workflow containing

PDF tasks.

Task

Optimize PDF

Separations

Task Type

PDF task

Description

The task checks whether the Normalized PDF input file contains any external references to images or other

Normalized PDFs:

• if there are external references, the Optimize PDF

Separations task checks if the modifications it is instructed to make will affect the external references. If any of the external references are affected, the task will first make the Normalized PDF input file self-contained

(by embedding all the external references).

• if there are no external references, or if the external references are not affected by the Optimize PDF

171

Automation Engine

Task

Trap - Prepare

Trap Layer

Task Type

Normalized PDF task

Description

Separations task will process the Normalized PDF directly.

The task also updates the XMP document metadata.

The task traps the Normalized PDF file.

10.4 How Do Normalized PDF Tasks Work With Regular

PDF Files?

In this topic, we take a look at how Automation Engine processes a regular PDF input file in our sample workflow containing a Normalized PDF task.

Task

Optimize PDF

Separations

Trap - Prepare

Trap Layer

Task Type

PDF task

Normalized PDF task

Description

The PDF is processed directly, because Optimize PDF

Separations is a PDF task.

The task detects that the input file is a regular PDF document, and automatically normalizes it. After that, the file is trapped and a self-contained Normalized PDF is produced.

The ticket used for Automatic Normalization can be configured using the Configure window in the

Automation Engine Pilot (choose Tools > Configure and navigate to Processing Preferences >

Automatic Normalization ).

172

Automation Engine

Automation Engine 12 is pre-configured to use the “Normalize PostScript/PDF/Illustrator 8.0 File” ticket called “OnDemand”. From this ticket only the settings in the “Color Management” tab are taken into account. All other settings of the auto normalization are forced to fixed default settings.

For example, automatic normalization will always embed all images.

173

Automation Engine

10.5 PDF Normalization and Step and Repeat

The step and repeat tasks in Automation Engine 12 can handle PDF, Normalized PDF or a mix of both at the input.The resulting output depends on a setting in the step and repeat ticket.

Output formats

Depending on your choice in the Output Format list of the Step & Repeat ticket, the format of the resulting document can be:

• PDFPLA

• a self-contained Normalized PDF

• a regular PDF

174

Automation Engine

PDFPLA

When you choose this option, the output of the step and repeat task will be a PDFPLA file. A PDFPLA is a Normalized PDF with external references to the 1-ups. It can be loaded and modified in Plato.

It can be RIPped directly by FlexRip. To send it to a non-Esko system, the PDFPLA needs to be exported to a PDF using the Export PDF task.

Note:

PDFPLA output can only be generated if all the inputs are Normalized PDFs. The task will fail if a 1up at the input is not normalized on beforehand.

This format is the recommended output format when the primary purpose of the step and repeat file is to send it to FlexRip.

Normalized PDF (embed all)

When you choose this option, the output of the step and repeat task is a self-contained Normalized

PDF. The 1-ups are embedded in the PDF using PDF forms so that the file size remains compact.

The file can not be modified in Plato. It can be RIPped directly by the FlexRip. It can also be sent to a non-Esko system.

Normalized PDF inputs will be embedded in the output. PDF inputs will be auto normalized and then embedded in the output.

175

Automation Engine

This format is recommended when further processing is needed on the output, for example by the Optimize PDF Separations task before sending it to FlexRip.

PDF

When you choose this option, the output of the step and repeat task is a PDF. The 1-ups are embedded in the PDF using PDF forms so that the file size remains compact. The file can not be modified in Plato. FlexRip can not RIP this file directly: it will first automatically normalize the step and repeat file. The file can be sent to a non Esko system.

Normalized PDF inputs will be embedded in the output. PDF inputs will be embedded in the PDF

“as is”.

This format is recommended when the primary purpose of the step and repeat file is to send it to a third-party, non-Esko RIP.

176

Automation Engine

11. Scripting

You can write Scripts (small programs) to automate the execution of certain tasks during a workflow.

Writing and using such scripts is called scripting. You need the Script Runner application to link scripting with your Automation Engine workflows. You can automate actions from Adobe applications

(e.g. Illustrator, Photoshop, InDesign) and third party tools (e.g. Alwan) using Scripts.

Some of the instances where scripting is useful are given below:

• to ensure file format integrity (standardization) for workflow inputs.

• to use standardized PDF as input during the Preflight process.

• to automate Adobe Illustrator, Photoshop, InDesign and InDesign Server via ExtendScript on Mac

Os and Windows.

Supported Script Types

• AppleScript (on Mac OS)

• ShellScript (on Mac OS)

• Batch files (on Windows)

• Windows Script (VBScript, JScript) (on Windows)

• ExtendScript (on Mac OS and Windows)

More info on Scripting :

Getting Started with Scripting

More info on Scripting in workflows:

Use case: Scripting

11.1 Automation Engine Script Runner

The Automation Engine(AE) Script Runner is a standalone AE server component which runs scripts on behalf of AE. You can add customization to your workflow by adding a Run Script task. This task will run on the Automation Engine server while the execution of the script will be done on the

Script Runner application which can be installed on Windows or Macintosh. When you launch the workflow, the following will take place:

177

Automation Engine

1. The Run Script task sends a request to run the specified script.

2. The Script Runner processes the request accordingly and runs the script.

3. The Script Runner sends the results back to the server.

4. The workflow will continue with the outputs from this task.

11.2 Getting Started with Scripting

Scripting helps you customize some steps in your work flows. You can achieve this by adding a Run

Script task to the work flow where you want customization. The Automation Engine will use Script

Runner to run scripts which are stored either locally or on a server. When you launch the workflow in

Automation Engine, the Script Runner runs the script which contains the main function incorporating the inputs from the Run Script task, output folder and some optional script parameters from the Run

Script ticket. The workflow in Automation Engine continues with the contents of the output folder which contains the outputs from the script. To achieve this, you need to do the following steps :

1. Download Automation Engine Script runner. You can download it via the web access to the

Automation Engine Server. Client Apps > Tools .

178

Automation Engine

• On Mac OS, open the ‘dmg’ file after downloading the Script Runner which contains the installer package. Double-click to start the installation.

• On Windows, double-click the downloaded installer to start the installation.

2. Install the Script Runner by following the instructions in the Installshield Wizard/Assistant and make sure it is running in your computer.

• On Windows, open Start > All Programs > Esko > Automation Engine Script Runner >

Preferences .

• On Mac OS, open Applications > Automation Engine Script Runner > Esko > Automation

Engine Script Runner > Script Runner Preferences .

In the Script Runner Preferences window, you can:

• check if the Script Runner is actually running

• start / stop the Script Runner

• enable(disable) Start at login

• view and change the port the Script Runner is communicating with

• view and change the default folders for scripts

179

Automation Engine

3. Configure the Script Runner on your computer. Read more in

Scripts

4. Write and save scripts. You can find sample scripts in the subfolders of /Library/Scripts/Esko on

Mac OS and C:\Esko\bg_data_fastserverscrrunnt_v100\Scripts on Windows.

• You can store the scripts on your computer on a default folder(specific for script type). This is ideal when you are developing and testing a script or when you do not intend to give access to other Script Runners on the network.

Note: The default location : on Mac OS : /Library/Scripts/Esko.

on Windows : C:\Esko\bg_data_fastserverscrrunnt_v100\Scripts.

Automation Engine does not back up these scripts.

• Alternatively, you can store your scripts in the Automation Engine data folder. This option is suitable when you want to make your scripts available to all configured Script Runners.

Note: The default location :

C:\Esko\bg_data_fastserver_v100\Scripts.

Automation Engine backs up these scripts.

5. Run the Script using Run Script task in a workflow. Read more about this in

Run Script

Note: Refer to the Reference Guide for more on Scripting

11.3 Use case: Scripting

Note:

Sample scripts are solely intended to demonstrate techniques for accomplishing common tasks.

Additional script logic and error-handling may need to be added to achieve the desired results in your specific environment.

It is up to the user to verify that his intended use of the offered automation functionality is compliant with any third party license agreement and/or other restrictions applicable to any non-Esko products.

180

Automation Engine

Please read

Getting Started with Scripting

before conducting the steps below.

In this example, we are demonstrating a script which will perform a Photoshop action and produce a JPEG output. The script 'EskoPSDoActionAndSaveasJPG.jsx' is available from the sample scripts subfolder (ExtendScript) in /Library/Scripts/Esko on Mac or C:\Esko

\bg_data_fastserverscrrunnt_v100\Scripts on Windows.

1. You have to save the Set and Action in Photoshop . In this example we are using Default Actions as Set and Molten Lead as Action.

2. You can open the script with ExtendScript Toolkit to edit the script if required. However, in this sample, we do not need to edit the script.

3. Edit the settings of the Run Script task as follows:

181

Automation Engine

182 a) Run on: is the name of the computer where your Automation Engine ScriptRunner is installed.

The name in this example is

ShaletMac

. You can read more about configuring and naming

Script Runner in

Scripts

b) Script Type: choose

ExtendScript

c) Script File: choose

EskoPSDoActionAndSaveasJPG.jsx

d) Script Parameters: Add the name of your Photoshop Action name followed by your Set . In this example,

Molten Lead

;

Default Actions e) Save the task.

4. Launch the task: a) Select the Photoshop file.

b) Right-click the file and browse for the ticket.

c) Click Launch.

You will see that while the script starts to run on the Automation Engine Server, PhotoShop opens, performs the actions, closes and continues the script. The result of this sample script is finally an adjusted jpeg.

Automation Engine

12. Integrating with Third Party

Impositioning Systems

There are new tasks in Automation Engine 12 onwards to accommodate for third party impositioning programs. This gives flexibility in automation due to the source independence. These tasks import or export industry standard file types to or from the Impositions in the Pages and Plates views.

You can check or change (approval) statuses, assign pages and select elements for further processing or output in the Pages and Plates views in Automation Engine.

Note: You can find more info on this in the corresponding chapters of the User Guide.

12.1 Workflows: The bigger picture

You can find a schematic overview of how impositions can be created, processed and exported below. The tasks highlighted in green are new in Automation Engine 12.

You can import populated or unpopulated impositions from applications that produces JDF layout file as its output. Some of the applications that can write a JDF Layout file are Kodak Preps, Litho

Technics Metrix, Ultimate ImpoStrip , Dynagram Inpo2 , Dynagram Dynastrip, Plato and Pandora.

12.2 Importing and Creating Impositions

You can import the JDF Layout and use the Create Imposition from JDF Layout task to bring the

Imposition to the Pages and Plates views in Automation Engine.

If you start with a PDF file or a JDF Runlist, you can use the Create RunList task to create a Runlist in Automation Engine. Subsequently, you can use the Create Imposition from RunList task to create

Imposition from this RunList.

183

Automation Engine

It is possible to separate the creation of a RunList and the creation of an Imposition from that Runlist in time. In some cases printers prefer to let the RunList be approved and corrected before they select the layout and create the Imposition.

You can achieve this by using two workflows.

1. Assemble the RunList and send it for approval.

2. Create the Imposition from the RunList and export it:

Read more about the new importing and creating tasks in the Reference Guide:

Create Imposition from JDF Layout

Create RunList

Create Imposition from RunList

General Remarks

Note: File Compatibility

• JDF layout files: tests have been done with Preps, Metrix, ImpoStrip, InpO2, DynaStrip, Plato and

Pandora.

• PDF files: Normalized as well as non Normalized files can be used in the Imposition workflows.

However, third party rips and workflows do not support external images.

Note: Thumbnails in the Pages and Plates views are only shown when the pages in the files contain thumbnails. If you have no thumbnails in your PDF files, you can speed up the system.You can also save some screen space by hiding the details pane and by switching to list mode.

12.3 Exporting Impositions

You can use Export Imposition to JDF Layout task to send an Impostition or part of an Imposition to another workflow system or to a Rip that is compatible with JDF layout.

• The output is JDF layout containing a JDF runlist.

• You can create a runlist for the Join Pages task using this output. This allows you to create a multipage PDF file to send to your customer for approval.

• It can be used to drive the FlexRip when followed by the Import JDF Layout task.

184

Automation Engine

You can send an Impostition or part of an Imposition to a PDF Rip (e.g. Nexus Rip) using Export

Imposition to PDF task. The output will be a PDF file containing the Imposition.

More info regarding these exporting tasks in:

Export Imposition to JDF Layout

Export Imposition to PDF File

12.4 Workflows with Selection and the Convert Selection tasks.

Page, RunList, Layer, PageSlot, Imposition and Plate are abstract file types that do not correspond directly to a file. They can be used as entities in a workflow to route the elements you want to process through the workflow. For example, you can import an Imposition and preflight all the PDF files referred from that Imposition. The workflow below accepts a JDF Layout as its input, selects the

PDF files referred in the JDF file and waits until all of them pass the preflight check before producing outputs as sheets to a PDF file. You need to convert the Selection to a PDF before Preflight.

Read more about Convert Selection task in

Convert Selection

the Reference Guide.

185

Automation Engine

13. Use Case: Setting up a Packaging

Workflow

13.1 Build a Workflow

You can build workflows from zero or using custom tickets, you can migrate task chains to

Automation Engine workflows, and create nested workflows.

You can use

Smart Names

to use predefined values. You can also choose to have the prepress manager build workflows that operators will use, or let the operators build workflows on the fly while processing files. See

Building Workflows

The following steps will help you build a Workflow like this:

13.1.1 Preflight your file

Preflight via External Application

The Preflight via External Application step allows you to preflight a PDF file by integrating external

(non- Automation Engine) preflight software into Automation Engine.

Attention: To define the preflight settings for Automation Engine go to Tools > Configure and select

Preflight Tools

1. From Start connect to the Preflight via External Application workflow step.

186

Automation Engine

2. Double-click on the workflow step to edit its parameters. For more information go to

Preflight via

External Application

When Preflighting in a workflow, the Preflight via External Application workflow step has four output pins:

187

Automation Engine

Note:

• Preflight OK: your files will go through this pin if the preflight gave an OK status.

• Preflight with Warnings: your files will go through this pin if the preflight gave a warning.

• Preflight with Errors: your files will go through this pin if the preflight gave an error.

• Error: your files will go through this pin in case of a processing error unrelated to the preflight status.

3. Connect each pin to the appropriate workflow step (for example, files which are “OK” or “Warning” can be normalized depending on your preflight setup, while files with “Error” need to be checked by an operator).

188

Wait for Action (Checkpoint)

Use the Wait for Action (Checkpoint) task to make your workflow stop at certain predefined points so that you have time to check and possibly correct something. See

Wait for Action

This Workflow is built so that you can route files based on your expertise. You will get a notification

(To Do List ), when the Preflight detects an error. The processing will be paused until you decide whether to approve the file or not, based on the preflight error report.

1. Add the Wait for Action (Checkpoint) step to your workflow.

2. Double-click the step to open its settings.

3. Create the notification that will be sent: a) choose which user you want to send it to, b) enter a Subject, c) add a Message if desired.

Automation Engine

4. Choose a Due date. Either:

• choose one of the predefined due dates (from Immediate to Next Sunday),

• choose Other... in the Due date list and pick the due date yourself.

5. In Output states, define the output possibilities you want for your checkpoint.

By default, this step has two outputs: Completed and Aborted.

To add an output: a) click Add, b) enter the output’s name.

Add as many outputs as you like.

6. If necessary, use the Move Up and Move Down buttons to display your outputs in a different order.

Note: You can Remove the default outputs if you don’t need them.

7. Click OK to apply your settings.

189

Automation Engine

Tip: After connecting the Output states you can:

• Add an extra Output state to the checkpoint and connect it to the“Preflight via External

Application”step, to preflight your file again.

•

Relaunch

the file from the Task pane or directly in the canvas. Right click and choose Relaunch

Copy or Move File

This task copies or moves the input file or the marked files to a new location. To mark a file, please insert the

Mark

file task in your workflow chain. If you don't want to evaluate an existing file, select the "Fail" task when the file that is to be copied or moved already exists in the output folder. See

Copy Move File

13.1.2 Normalize your File

The Normalize PostScript / PDF / Illustrator 8.0 File generates a Normalized PDF file based on the preflighted file. See

Normalize PostScript / PDF / Illustrator 8.0 File

• Transparencies and Layers check the box to import PDF files as in Scope 3 (and lower). All transparencies and layers will be flattened. If not checked, a normalized PDF file will be created that contains all typical PDF features (like transparencies and layers).

Workflow overview

13.1.3 Trap your file

Trap - Prepare and Create Trap Layer

The trapping process is a safeguard against possible (even likely) fluctuations in the printing process.

Minor discrepancies in registration, slight paper shifting can cause inks to mis-register. See

What is Trapping?

190

Automation Engine

There are three different Trap tasks;

Trap – Create Trap Layer

: This task traps the input file according to the settings specified in the Trap

Color Pairs file associated with the input file. The output of this task is a trapped Normalized PDF file.

This task contains only the output options of the Trap task. All other trapping parameters are stored in the TCP file located in the same folder as the input file.

Trap – Prepare and Create Trap Layer

: this step selects candidate trap color pairs and executes the trapping. The trapping areas are added in a separate layer on top of the original job.

Trap – Prepare Trap Pairs

: This scans through the job and suggests a list of candidate trap color pairs.

Export Trapped File to PDF

Export your Normalized PDF to generic PDF for storage or approval. See

Export to PDF File

Tip:

• To define the name and location of the output file that will be generated, use SmartNames.

• You can send the output file via mail.

• You can use PDF as SoftProof.

Workflow Overview

191

Automation Engine

13.1.4 View your file

Prepare for Viewer

The Prepare for Viewer task prepares view data for the Automation Engine Viewer. This view data will help the Viewer to quickly open the file (the Viewer will use the prepared View Data instead of asking the server to make or stream it). See

Prepare for Viewer.

Hold for Viewing

Choose a decision maker with experience to approve the trapped file. See

Wait for Action

. The

Automation Engine Viewer is a powerful integrated Viewer and QA tool. The Automation Engine

Viewer offers:

• Reliability: Showing the data in a correct way. At best in the same way the RIP/ Proofer will see them.

• Detail: Unlimited zoom, high detail measuring, measuring traps and exact distances (die objects).

• Speed: Opening files swiftly, even when it concerns large files. Fast zooming.

• See

Automation Engine Viewer.

Workflow Overview

192

Automation Engine

Tip: You could add an extra Output state, ”Send to Proof” to the checkpoint, connecting to

Proof(FlexProof)

to print HardProof.

13.1.5 Generate Step & Repeat

Mark

Use this to tag files that you will need to select later in the workflow (with the Select workflow control). The file will be tagged as "Label" and after approved in Hold for Viewing, the Select will pickup the original file.

• Give the tag a name.

Select

Use this ticket to select files that you have tagged earlier in the workflow (with the Mark workflow control).

• Enter the tag of the file.

193

Automation Engine

For an example see

Mark and Select.

Step & Repeat Tabular

This Workflow Step executes all Step and Repeat parameters (number of one-ups vertically and horizontally, gap between one-ups, alignment, SmartMarks...) after which the server will output the sheet layout. The ticket's input fields also accept SQL queries, so that information stored in a database can be used to drive the sheet layout creation. See

Step & Repeat Tabular.

Workflow Overview

13.1.6 Create Report

Create Report (ReportMaker)

The

ReportMaker

task is used to automate the creation of design print cards (in French: fiche technique, in German: Drueck Karten).

The idea is that you generate reports containing all kind of information: file name, used inks, name of the operator, an image of the file. All this information is defined in a report template, then this template

194

Automation Engine

13 is used to generate a specific report. For more information about templates, see

ReportMaker

Templates

Note: You need PackEdge 3.0 or higher to make a ReportMaker template.

Export Report to PDF

Export to PDF

makes it possible to specify different settings, for example PDF version, Color

Management…

Tip: You can define the File Name and the, Output location, of the report file that will be generated, by using SmartNames.

Upload via FTP

Upload via FTP is an administration task which allows you to send files to a server. You need an FTP account on that server. For details or how to connect to an FTP server, see

Upload via FTP

Tip:

• To interact with customers you can also use steps likePublish on Web and Create WebCenter

Project.

Workflow Overview

195

Automation Engine

13.2 Use Shuttle in the Workflow

13.2.1 What is Shuttle

Shuttle is a small stand-alone application that enables you to submit files to Automation Engine tasks or workflows, and monitor their progress. You can use Shuttle to connect to several servers. The

Shuttle functionality is also integrated in ArtPro, Neo, PackEdge, Plato, FastImpose and in Adobe

Illustrator as a DeskPack plug-in. You can download Shuttle from EskoArtwork's Download Center

(

http://download.artwork-systems.com/

). For more information about Shuttle see the Shuttle User

Guide.

Set up Shuttle for Automation Engine

To use Shuttle and submit files to your Automation Engine workflow, you need to set up your server, your Shuttle client, and make sure they can exchange files via a shared folder.

Workflow Server Setup

Automation Engine’s Configure tool. See Automation Engine Setup for Shuttle, Automation Engine

User Guide.

Shuttle Client Setup

Set up your Shuttle client in the applications you use. See Shuttle Clients Setup, Automation Engine

User Guide.

Shared Folder Setup

You also need to make sure that the relevant servers shared folders are mounted on the Shuttle clients machines, with the appropriate Read and Write permissions. For Automation Engine, the shared folder is either an Automation Engine Container, or an Upload Folder you set up in Configure.

See Automation Engine Setup for Shuttle, Automation Engine User Guide.

13.2.2 What are Public Parameters

Operators or an administrator of the Automation Engine workflow determines which Public

Parameters can be defined for submitting files through Shuttle. A common use case is to avoid mistakes by allowing only a choice of predefined values. Public Parameters reduce the need or predefined tasks. The owner of the ticket can easily change values before submitting new files.

13.2.3 Making Your Tickets Public

With Shuttle, you can submit files to any Automation Engine task, task chain or workflow that has a custom ticket. To do this, you need to make the ticket public. You can either:

• Select the Public option when creating the ticket.

196

Automation Engine

• In the Ticket view, right-click your ticket and select Public Ticket.

Note: Public Tickets have a mark in the Public column.

13.2.4 Using Public Parameters

Public parameters are ticket parameters that operators can define for submitting files through Shuttle.

For each public parameter, you can either:

• enter a list of predefined values the operator will choose from,

• let the operator enter a value himself.

Making a Parameter Public

Attention: You need to define which parameters are public before files are submitted to your workflow.

In the ticket containing the parameter to make public:

1. Right-click the parameter and select Make Parameter Public.

2. Right-click it again and select Modify Public Parameter...

3. In the Modify Public Parameter dialog that opens: a) If necessary, change the way the parameter will be called in Shuttle in Prompt as.

b) Choose either:

197

Automation Engine

• Allow the user to set the value if you want Shuttle users to be able to freely enter a value for that parameter.

• Let the user select a predefined value if you want Shuttle users to choose from a list of values that you define.

198

If that parameter already has a list of values to choose from in the Ticket, they will be displayed here. You can Add or Remove values.

Note: Shuttle operators will see (and choose from) the Predefined Settings but not the associated Values.

4. Don’t forget to save your ticket.

Automation Engine

This is how your public parameter will look to Shuttle operators:

If you chose Allow the user to set the value

If you chose Let the user select a predefined value

Managing Public Parameters in Your Ticket

Once you have made parameters public in your ticket, you can have an overview of your public parameters and edit them at the ticket level.

1. In your ticket, go to Advanced > Manage Public Parameters...

The Manage Public Parameters dialog that opens contains all of your ticket’s public parameters.

199

Automation Engine

200

The left pane shows all parameters that can be made public for that ticket (the ones you have made public are greyed out).

The right pane shows the parameters you have made public, with their settings (predefined values, etc.).

Automation Engine

2. You can:

• drag parameters from left to right to make them public;

• click a public parameter’s cross if you don’t want it to be public anymore;

• rearrange the order of your public parameters (drag them up or down);

• change public parameters’ settings (Prompt as, Predefined Settings, etc.);

• group public parameters under a header (click Add Group, click to edit the header, and drag parameters from the left);

Using Presets to Simplify Operators’ Choices

You can use presets to minimize the amount of public parameters your operators have to choose from, and make it simpler for them.

201

Automation Engine

In the Manage Public Parameters dialog:

1. Click the Add Preset button.

2. Enter what your operators will see: a) in Prompt as, enter the name to give the preset parameter in Shuttle, b) enter the values that operators will choose from (replacing

Type a value here

Click Add if you need to add extra values.

202

3. Drag parameters from the dialog’s left pane into the preset.

You can drag as many parameters as you want. They will appear under each value (here both under

Offset

and

Dry Offset

Automation Engine

4. Define the parameters values for each preset value.

For example, define normal trapping, 50% opacity and object dependant end caps for Offset, and reverse trapping, 100% opacity and round end caps for Dry Offset.

5. Don’t forget to save your ticket.

This is how your preset will look to Shuttle operators:

SmartNames in Public Parameters

You can use SmartNames in your public parameters (for parameters taking SmartNames as input).

In Shuttle, use square brackets around SmartNames when submitting a file with public parameters.

203

Automation Engine

13.2.5 Public Parameters in Sample Workflow: Packaging

When choosing which parameters to make public you can keep have in mind end production, different customers, workflow capability etc. Define the parameters so that you can change the production file without having to change the workflow ticket.

204

Automation Engine

13.2.6 Launching Files into a Workflow

Launching Files from Shuttle Standalone

1. To assign a Job ID and / or Job Part ID to the files to process in your workflow, go to Window

> Context and fill in the Job ID and / or Job Part ID.

205

Automation Engine

Do this when:

• you want to add your file(s) to an Automation Engine job,

Note: If the file you are launching is already located in an Automation Engine job, it will automatically be processed within that job’s context (you don’t need to enter the Job ID).

2. Open the Launch window using:

• File > New Launch Window... ,

• Option + Command + N on Mac or Alt + Control + N on PC.

3. Select the Workflow you want to launch on your file.

• For Automation Engine workflows, you will see public tickets.

Note:

You can open several Launch windows, and select a different workflow in each.

If you quit and restart Shuttle, your Launch windows will be remembered.

4. Launch your file in one of the following ways:

• Drag and drop your file on the Drop Files Here arrow.

• Click the Launch... button and browse to the file you want to launch.

• Go to File > Launch... and browse to the file you want to launch.