automation engine user guide - product documentation - esko · adobe illustrator (using the...

Automation Engine

User Guide

Automation Engine

ii

Contents

1. About Automation Engine........................................................................................................................................................5

1.1 Copyright Notice................................................................................................................................................................5

1.2 Getting Help.........................................................................................................................................................................7

2. What is Automation Engine.................................................................................................................................................... 8

2.1 The Automation Engine Pilot......................................................................................................................................10

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

2.1.2 Views....................................................................................................................................................................... 11

2.2 Data Management in Automation Engine............................................................................................................. 12

2.2.1 Containers............................................................................................................................................................. 13

2.2.2 Jobs......................................................................................................................................................................... 13

2.3 Files Processing in Automation Engine..................................................................................................................14

2.3.1 Tasks........................................................................................................................................................................14

2.3.2 Task Chains.......................................................................................................................................................... 15

2.3.3 Workflows.............................................................................................................................................................. 15

2.3.4 Tickets.....................................................................................................................................................................15

3. Getting Started with Automation Engine........................................................................................................................17

3.1 Starting Automation Engine........................................................................................................................................17

3.1.1 Starting the Automation Engine Server.....................................................................................................17

3.1.2 Starting the Pilot.................................................................................................................................................18

3.2 Performing Basic Configuration................................................................................................................................ 19

3.2.1 Creating Users.....................................................................................................................................................19

3.2.2 Defining User Access Rights.........................................................................................................................19

3.2.3 Configuring Output Devices...........................................................................................................................21

3.3 Uploading Files using the Pilot................................................................................................................................. 23

3.4 Launching a Task on a File.........................................................................................................................................24

3.5 Checking the Status of the Task.............................................................................................................................. 25

3.6 Checking the Result in the Viewer...........................................................................................................................26

3.7 Relaunching the Task.................................................................................................................................................... 28

3.8 Generating Output.......................................................................................................................................................... 28

4. Uploading Files to Automation Engine............................................................................................................................29

4.1 Uploading Files using the Pilot................................................................................................................................. 29

4.2 Uploading Files from a FTP Server......................................................................................................................... 29

4.3 Using Hot Folders to Upload and Process Files................................................................................................30

4.3.1 About Hot Folders............................................................................................................................................. 31

4.3.2 Creating a Task Hot Folder............................................................................................................................31

4.3.3 Modifying Hot Folder Settings......................................................................................................................39

4.3.4 Updating Your Task Hot Folders..................................................................................................................40

Contents

iii

4.4 Using Shuttle to Upload and Process Files......................................................................................................... 41

4.4.1 What is Shuttle?................................................................................................................................................. 41

4.4.2 Shuttle Setup....................................................................................................................................................... 42

4.4.3 Launching Files from Shuttle Standalone.................................................................................................48

4.4.4 Launching Files from ArtPro.......................................................................................................................... 50

4.4.5 Launching Files from PackEdge or Plato................................................................................................. 54

4.4.6 Launching Files from FastImpose............................................................................................................... 55

4.4.7 Launching Files from Neo...............................................................................................................................57

4.4.8 Launching Files from the Shuttle Plug-in................................................................................................. 57

5. Running Tasks on Files.......................................................................................................................................................... 60

5.1 Creating a Task Ticket.................................................................................................................................................. 60

5.1.1 Creating a Custom Ticket from the Tickets View..................................................................................60

5.1.2 Creating a Custom Ticket when Working with Files.............................................................................60

5.1.3 Using Public Parameters.................................................................................................................................62

5.1.4 Using SmartNames............................................................................................................................................70

5.2 Launching a Task on a File.........................................................................................................................................72

5.3 Checking the Status of the Task.............................................................................................................................. 75

5.4 Relaunching the Task.................................................................................................................................................... 76

6. Running Workflows on Files................................................................................................................................................ 77

6.1 Building Workflows.........................................................................................................................................................77

6.1.1 Building a Workflow from Zero.....................................................................................................................77

6.1.2 Building a Workflow using Custom Tickets.............................................................................................81

6.1.3 Reusing a Task Chain Ticket to Build a Workflow................................................................................ 82

6.1.4 Nested Workflows.............................................................................................................................................. 86

6.1.5 Using Routing in Your Workflow.................................................................................................................. 93

6.1.6 Using Public Parameters.............................................................................................................................. 102

6.1.7 Adding Sticky Notes to Your Workflow...................................................................................................111

6.1.8 Checking All the Workflow's Parameters...............................................................................................112

6.2 Using Workflows........................................................................................................................................................... 113

6.2.1 Launching a Workflow on a File................................................................................................................ 113

6.2.2 Building a Workflow and Launching it on a File on the Fly.............................................................115

6.2.3 Pausing or Cancelling Your Workflow..................................................................................................... 116

6.3 Checking the Workflow's Processing Status.....................................................................................................117

6.4 Re-launching Your Workflow with Different Settings......................................................................................119

7. Viewing Files in the Automation Engine Viewer....................................................................................................... 120

7.1 About the Viewer.......................................................................................................................................................... 120

7.2 Checking the Result in the Viewer........................................................................................................................ 121

7.3 Comparing Files............................................................................................................................................................ 123

8. Integration with Other Applications................................................................................................................................126

8.1 Integration with WebCenter......................................................................................................................................126

8.1.1 WebCenter Setup.............................................................................................................................................126

Automation Engine

iv

8.1.2 Automation Engine Setup.............................................................................................................................134

8.1.3 Sending an Imposition from Automation Engine to WebCenter....................................................136

8.1.4 Approving the Imposition in WebCenter.................................................................................................141

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

8.1.6 Overruling the WebCenter Approval.........................................................................................................150

8.2 Integration with Nexus............................................................................................................................................... 151

8.2.1 Setup on the Nexus Side.............................................................................................................................152

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

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

8.3 Integration with Odystar............................................................................................................................................ 155

8.3.1 Setup on the Odystar Side..........................................................................................................................156

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

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

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

8.4.1 i-cut Automate Workflow.............................................................................................................................. 162

8.5 Integration with Enfocus PitStop........................................................................................................................... 163

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

8.7 Integration with MIS Systems................................................................................................................................. 166

8.7.1 About JDF and MIS Integration.................................................................................................................166

9. Use Case: Setting up a Packaging Workflow............................................................................................................169

9.1 Build a Workflow...........................................................................................................................................................169

9.1.1 Preflight your file.............................................................................................................................................. 169

9.1.2 Normalize your File......................................................................................................................................... 173

9.1.3 Trap your file......................................................................................................................................................173

9.1.4 View your file..................................................................................................................................................... 175

9.1.5 Generate Step & Repeat...............................................................................................................................176

9.1.6 Create Report....................................................................................................................................................177

9.2 Use Shuttle in the Workflow.................................................................................................................................... 179

9.2.1 What is Shuttle................................................................................................................................................. 179

9.2.2 What are Public Parameters....................................................................................................................... 179

9.2.3 Making Your Tickets Public......................................................................................................................... 179

9.2.4 Using Public Parameters.............................................................................................................................. 180

9.2.5 Public Parameters in Sample Workflow: Packaging..........................................................................187

9.2.6 Launching Files into a Workflow................................................................................................................188

1Automation Engine

5

1. About Automation Engine

Maximizing Productivity

Automation Engine doesn't only enable you to keep track of your files throughout your workflow, italso 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 ofprepress-related actions.

Integrating with your Existing Systems

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

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 Windowsmachine in your network, so all your operators can view files, get information or launch processingtasks as needed.

Growing with You

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

From a background assistant to Adobe® Illustrator® to a central prepress server to a complete serverplatform linking to your administrative systems, Automation Engine can grow with you to let youhandle 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

© Copyright 2012 Esko Software BVBA, Gent, Belgium

All rights reserved. This material, information and instructions for use contained herein are theproperty of Esko Software BVBA. The material, information and instructions are provided on an AS ISbasis 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 representationsregarding the use, or the results of the use of the software or the information contained herein. Esko

#

1Automation Engine

6

Software BVBA shall not be liable for any direct, indirect, consequential or incidental damages arisingout 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 fromtime 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 othermeans 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 othertrademarks or registered trademarks are the property of their respective owners. Pantone is a whollyowned 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.

Portions of this software are copyright © 1996-2002 The FreeType Project (www.freetype.org). Allrights reserved.

Portions of this software are copyright 2006 Feeling Software, copyright 2005-2006 Autodesk MediaEntertainment.

Portions of this software are copyright ©1998-2003 Daniel Veillard. All rights reserved.

Portions of this software are copyright ©1999-2006 The Botan Project. All rights reserved.

Part of the software embedded in this product is gSOAP software. Portions created by gSOAP areCopyright ©2001-2004 Robert A. van Engelen, Genivia inc. All rights reserved.

Portions of this software are copyright ©1998-2008 The OpenSSL Project and ©1995-1998 EricYoung ([email protected]). All rights reserved.

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 ortrademarks 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 UnitedStates and other countries.

SolidWorks is a registered trademark of SolidWorks Corporation.

Portions of this software are owned by Spatial Corp. 1986 2003. All Rights Reserved.

JDF and the JDF logo are trademarks of the CIP4 Organisation. Copyright 2001 The InternationalCooperation for the Integration of Processes in Prepress, Press and Postpress (CIP4). All rightsreserved.

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 SunMicrosystems in the U.S. and other countries.

Part of this software uses technology by BestTM Color Technology (EFI). EFI and Bestcolor areregistered 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:

1Automation Engine

7

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 toHelp > Shortcuts...

2Automation Engine

8

2. What is Automation Engine

Automation Engine Architecture

Automation Engine is a client/server workflow software, running on Mac and PC. This means thatone machine runs the Automation Engine server, to which you can connect from all Mac and PCmachines 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 ondifferent machines over the network (using containers).

2Automation Engine

9

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), andWorkflows (more powerful and flexible grouping of tasks, that can take complete care of the file frominput to output).

2Automation Engine

10

Files and Jobs in Automation Engine

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

Depending on how you want to work with Automation Engine, you can link your jobs to customerproducts, 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’scollaborative 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 actionis 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:

2Automation Engine

11

•Containers : this shows all the data that Automation Engine can access, in the differentContainers. 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 onlyaccessible in defined workflows. For more information, see Views.

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

4.The Create Job button allows you to create a job.

5. The New Task button allows you to select a Ticket from the list. The New Workflow button opensthe workflow editor and allows you to build a new workflow. For more information see Runningtasks on files and Running workflows on files.

The contents of the central panes depends 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 themto 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 willhave 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 moreinformation.

To Do List

The To Do List view lists all actions that need user intervention. For more information, see The ToDo 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.

Products

The Product view shows the production files associated with your jobs, and allows you to reuse thosefiles 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. SeeWorking with Proofs.

2Automation Engine

12

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 witha job. It also includes advanced features for managing plates for jobs with multiple versions. SeeWorking with Plates.

CDI

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

Tasks

The Tasks view shows the current state of processing: the running tasks, the tasks waiting forexecution 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 youto 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 themilestones 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 foldersdefined for a job (in Last used job mode). It offers all the necessary tools to create and manage hotfolders. See About Hot Folders.

Tickets

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

Jobs

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

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 threemodes:

2Automation Engine

13

•Containers : this shows all the data that Automation Engine can access, in the differentContainers. 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 canaccess. 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 installedon.

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 AutomationEngine.

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

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

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

2Automation Engine

14

Job Metadata

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

Job Automation

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

For more information about Jobs, 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 BackStageworkflows), 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...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).

2Automation Engine

15

Task Progress

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

2.3.2 Task Chains

Old BackStage workflows are still supported in Automation Engine (just as in BackStage), but arenow 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 (seeReusing 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.

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 ProcessFiles).

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. Youcannot overwrite or delete default tickets.

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

2Automation Engine

16

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 waysto make a ticket public (see Making Your Ticket Public in the User Guide).

Public tickets have a mark in the Public column.

Note: Depending on your access rights, you may only see public tickets, and public parametersinside the tickets.

3Automation Engine

17

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 theserver 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 theAutomation 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 admininstrationtasks for the Automation Engine server.

3Automation Engine

18

For more information on working with the server, seeServer 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:

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

3Automation Engine

19

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 tocreate that user.

Some changes to that user can then no longer be made through the Automation Engine Pilot, butneed 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 inAutomation Engine.

• To give access rights to a single user:

a) in the Users window, double the user you want to give access rights to,

3Automation Engine

20

b) in the Access Rights tab of the Properties window, check the access rights you want thisuser to have.

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

• 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.

3Automation Engine

21

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.

3Automation Engine

22

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.

3Automation Engine

23

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 seeits 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 theorder they enter the RIP),

• choose 2 to have the RIP handle two files at once (the files may not be ripped in the orderthey 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 yourfile.

2. Go to File > Upload...

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

3Automation Engine

24

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 viaJDF/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 listedabove 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 chooseeither a Default ticket, or a custom ticket (saved under a different name) if you have alreadycreated one.

5. Click OK.

This opens the task’s ticket.

3Automation Engine

25

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 Overviewin 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 Checkthe 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’sTasks 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:

3Automation Engine

26

• : starting•

: success•

: warning•

: failure•

: processing cancelled

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

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, seeSupported File Types in the Reference Manual.

In the Files view, do one of the following:

• Click the word View next to your file.

• Right-click your file and select View...• Select your file and go to File > View .

3Automation Engine

27

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

3Automation Engine

28

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 OutputDevices).

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 configuredyour output device.

4Automation Engine

29

4. Uploading Files to Automation Engine

You can work with files that are already stored in your containers, or upload new files to AutomationEngine. You can upload files from the Pilot, using Hot Folders or with the Shuttle application andplug-in.

4.1 Uploading Files using the Pilot

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

2. Go to File > Upload...

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

4.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 Uploadfrom FTP Site...This opens the Upload from FTP Site dialog, where you can enter the details necessary for theFTP 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 existson 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 selectingASCII.

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

If your system is behind a firewall that blocks incoming FTP server connections, select Passiveto 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 askyour 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 (selectRemove remote data after transfer).

4Automation Engine

30

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

8. When you are done, click Connect.

4.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),

4Automation Engine

31

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

4.3.1 About Hot Folders

A Hot Folder is a special folder monitored by Automation Engine. When you drop a file into the HotFolder, 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 Enginelaunches 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 associatedwith the JDF Hot Folder.

See Creating a JDF Hot Folder.

4.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.

2.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.

4Automation Engine

32

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 beprocessed 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.

4Automation Engine

33

The Hot Folder is now listed in the Pilot's Hot Folders View. You can see information about theHot 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.

4Automation Engine

34

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

4Automation Engine

35

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.

4Automation Engine

36

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

Tip: Use this with a specific Inactive time (for example 08:00 AM to 05:00 PM, so the files areonly 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 theprocessing 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 andclick OK.This opens that workflow in the workflow editor window.

4Automation Engine

37

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 (inone workflow) instead of individually.

Tip: Use this with a specific Inactive time (for example 08:00 AM to 05:00 PM, so the files areonly 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 theprocessing 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.

4Automation Engine

38

2. Click Add...

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

4. In the Select Task Type and Settings dialog, enter the settings for the task(s), or for each workflowstep, 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:

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

4Automation Engine

39

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 startthe 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.

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

4.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.

4Automation Engine

40

Tip: You can export the task ticket used for your Hot Folder, to be able to use it throughoutAutomation Engine. Use the Export Ticket... button and give the ticket a different name.

4.3.4 Updating Your Task Hot Folders

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

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

You don't need to make new Hot Folders as your old Hot Folders will keep on working, but theadvantages 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 jobfolder (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.

4Automation Engine

41

You can also use Ctrl + C (on PC) or Command + C (on Mac).d) Close the old Hot Folder setup window.

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 31.

4.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.

4.4.1 What is Shuttle?

Shuttle is a small stand-alone application that enables you to submit files to Automation Engine tasksor workflows, Odystar canvases, and Nexus workflows, and monitor their progress. You can useShuttle to connect to several servers.

4Automation Engine

42

The Shuttle functionality is also integrated in ArtPro, Neo, PackEdge, Plato, FastImpose and in AdobeIllustrator as a DeskPack plug-in.

4.4.2 Shuttle Setup

Automation Engine Setup for Shuttle

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

2. Select Shuttle in the left pane.

4Automation Engine

43

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

Note: By default this is port 5182, but if this port is already used by other processes, you shouldenter 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 Shuttleplug-in, that will always upload files to the DeskPackContainer).

4Automation Engine

44

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 makefrequent 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 Shuttleclients.

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 workflowthat 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.

4Automation Engine

45

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

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

Shuttle Clients Connecting to Any Server

Shuttle Standalone, the Shuttle plug-in, and the Shuttle clients in ArtPro, Neo and FastImposeStandalone can connect to a number of Odystar, Nexus and Automation Engine servers.

1. Launch your application.

2. Open the Preferences.

In... go to...

Shuttle Standalone • 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 ArtPro > Preferences... or use Command + K

Neo Neo > Preferences... or use Command + ,(comma)

FastImpose Standalone Tools > Shuttle Preferences...

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

4Automation Engine

46

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 youuse to login 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 systemadministrator.

5. To connect to a server not broadcasting over the Bonjour network (Automation Engine servers ornon-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.

4Automation Engine

47

Note:

When connecting to an Automation Engine server, enter the port you defined in Configure (seeAutomation 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 setup a serverconnection with the Server Connection Assistant, you will see this connection in bold in the Shuttleplug-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 toremove this connection from the Shuttle plug-in.

See the Adobe Illustrator Client documentation for more information on the Server ConnectionAssistant.

Shuttle Clients Connecting only to Automation Engine

The Shuttle clients in PackEdge, Plato and FastImpose Server can only connect to one AutomationEngine 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 ...

4Automation Engine

48

Tip:

If you are running an Automation Engine Pilot on the same computer, or another Shuttleclient connecting to it (either PackEdge, Plato or FastImpose Server), you can select Loginautomatically 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 needto log in when starting PackEdge / Plato / FastImpose Server.

4. Restart your application.

4.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 willautomatically 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.

4Automation Engine

49

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.

4Automation Engine

50

Note:

For more information on public parameters, see:

• Using Public Parameters,

4.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.

4Automation Engine

51

4Automation Engine

52

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

If your workflow is... you can launch the fileas...

with...

an Automation Engineworkflow acceptingNormalized PDF files asinput

Normalized PDF either Normalized PDFor Normalized PDF(embedded)

an Automation Engineworkflow accepting PDFfiles as input

PDF any of the available PDFflavors

an Automation Engineworkflow accepting ArtProfiles as input

ArtPro with the included images(TIFF, EPS...) or without(only the ArtPro and theArtPro 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 JobID and/or Job Part ID.

4Automation Engine

53

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 fillin 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.

4Automation Engine

54

7. Click the Launch button.

4.4.5 Launching Files from PackEdge or Plato

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

1. Go to File > Launch Workflow...


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


Note: For more information on public parameters, see Using Public Parameters.

4Automation Engine

55

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

Tip:

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

1.

Go to Window > Toolbars > Shuttle to open the Shuttle palette. 2. Drag it into your application’s toolbar.3.

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

4.4.6 Launching Files from FastImpose

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



4Automation Engine

56

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 manualfor more information).



4Automation Engine

57


4.4.7 Launching Files from Neo




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



Note: If you want to go back to the default parameters values after changing them, use the ResetTo Defaults button.


4.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.

4Automation Engine

58

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 refinethe 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 JobSub ID.

4Automation Engine

59

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, sothat 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 JobSub ID will be filled automatically.

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


6. Click Launch to launch your file.

5Automation Engine

60

5. Running Tasks on Files

5.1 Creating a Task Ticket

5.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.

5.1.2 Creating a Custom Ticket when Working with Files

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

5Automation Engine

61

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).

5Automation Engine

62

Note:

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

• 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.

5.1.3 Using Public Parameters

Public parameters are ticket parameters that operators can define when submitting files throughShuttle.

For each public parameter, you can either:

5Automation Engine

63

• 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 valuefor that parameter.

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

5Automation Engine

64

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

Note: Shuttle operators will see (and choose from) the Predefined Settings but not theassociated 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 theoperator 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 predefinedvalue

Managing Public Parameters in Your Ticket

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

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

5Automation Engine

65

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 havemade public are greyed out).

5Automation Engine

66

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, anddrag parameters from the left);

• use presets to simplify operators’ choices (see Using Presets to Simplify Operators’ Choices).

5Automation Engine

67

Using Presets to Simplify Operators’ Choices

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

For example, you want operators to use different trapping settings for printing with offset or dryoffset. You can define those trapping settings in a preset, so that operators will only have to choosebetween 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 bothunder Offset and Dry Offset).

5Automation Engine

68

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.


This is how your preset will look to Shuttle operators:



You can either:

5Automation Engine

69





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.

5Automation Engine

70

5.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 nameof 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 greenand 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 rememberit, and reduces errors.

5Automation Engine

71

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.

5Automation Engine

72

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 insertSmartNames in it.

5.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 viaJDF/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) accessright (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.

5Automation Engine

73

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

5. If:

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

5Automation Engine

74

• 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 theticket. You don't need to fill in any settings.

• You chose Launch with and you don't have the Tickets: Show All Tickets and theirParameters (Public and other) access right, the task is launched on the file as soon as youselected 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 thepublic parameters). Click Launch when you are done.

5Automation Engine

75

Note: For a description of all of the ticket's settings for each task, see The Tasks: an Overviewin the Reference Guide.

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

5.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’sTasks pane. You can see the Tasks pane in the Files, Product or Tasks views.


• : starting

5Automation Engine

76

•: success

•: warning

•: failure

•: processing cancelled

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

Note: Depending on your access rights, you may only see the public parameters.

5.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.

6Automation Engine

77

6. Running Workflows on Files

6.1 Building Workflows

You can build workflows from zero or using custom tickets, you can migrate task chains toAutomation Engine workflows, and create nested workflows.

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

6.1.1 Building a Workflow from Zero

1.

Click in the Tickets view to open the workflow editor.

The workflow editor window only contains two steps by default ( and ).

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

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

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

6Automation Engine

78

You will still be able to see the original name (the task type or workflow control type) by hoveringon 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 witha green tube.

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

6Automation Engine

79

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.

6Automation Engine

80

6Automation Engine

81

6. Save your workflow using either:

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

6.1.2 Building a Workflow using Custom Tickets

1.

Click in the Tickets view to open the workflow editor.

2.

Click the tickets button in the workflow editor’s toolbar to open the Ticket Browser pop-up.

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 notbe 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 (youcan see an arrow next to the ticket name).

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

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

5. Connect your steps with one another.

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

6Automation Engine

82

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 NestedWorkflows).

6. Save your workflow using either:

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

6.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 canpreserve 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.

6Automation Engine

83

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.

6Automation Engine

84

Note:

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

• The steps are detached so you can optimize your workflow construction (the workflow editorenables 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 redfor three seconds, then disappear. You should replace them with the corresponding workflowcontrols (for example, replace Mark File by Mark). See Workflow Controls and DeprecatedSteps.

6Automation Engine

85

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.

6Automation Engine

86

5. Save your workflow.

6.1.4 Nested Workflows

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

You can then integrate this subworkflow as it is (with its settings etc.) in other workflows, creatingnested 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:

6Automation Engine

87

Here is the nested workflow:

6Automation Engine

88

with the first subworkflow:

6Automation Engine

89

and the second subworkflow:

6Automation Engine

90

Building a Nested Workflow

To add a subworkflow into your workflow:

1.

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

6Automation Engine

91

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

2. Double-click the workflow step.

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

6Automation Engine

92

The indication shows you this is a subworkflow.

3. Build your 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.

4.Click your main workflow to go back to it (click in the example).

5. Save your workflow.

Note: You can nest several layers of subworkflows.

6Automation Engine

93

6.1.5 Using Routing in Your Workflow

The workflow routes files automatically to OK, Warning or Error outputs depending on theirprocessing 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 workflowsteps.

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

Note: When a step’s output pin is connected to several other steps, Automation Engine willautomatically 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 theoutputs of the workflow step in your main workflow.

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

6Automation Engine

94

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

This means that:

• files sent to the One Up step of your subworkflow will go through the One Up output in your mainworkflow (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 mainworkflow (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:

1.

Add the Wait for Action (Checkpoint) step to your workflow.

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

6Automation Engine

95

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.

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:

6Automation Engine

96

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 bythe 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 theappropriate step.

6Automation Engine

97

Operators will be able to route files gone through the Checkpoint from the Pilot’s Tasks pane, theworkflow 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 Checkpointstep (and close the To-Do).

In the Workflow Editor

In the workflow editor, the operator will see User intervention needed as the file status and theCheckpoint step will jump up and down.

6Automation Engine

98

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...

6Automation Engine

99

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 inShuttle (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 showsthe workflow steps.

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

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.

6Automation Engine

100

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.b)

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.

6Automation Engine

101

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

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

6Automation Engine

102

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.


Public parameters are ticket parameters that operators can define when submitting files throughShuttle.




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







6Automation Engine

103







6Automation Engine

104


Managing Public Parameters in Your Workflow

Once you have made parameters public in your workflow steps’ tickets, you can have an overviewof 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 publicparameters, sorted by workflow step.

6Automation Engine

105

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 (predefinedvalues, etc.).

2. You can:

6Automation Engine

106

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


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

• use presets to simplify operators’ choices (see Using Presets to Simplify Operators’ Choices).



6Automation Engine

107









6Automation Engine

108





Checking All the Workflow's Public Parameters Values

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

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

6Automation Engine

109

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 publicparameter values, sorted by workflow step.

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

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



You can either:



6Automation Engine

110






6Automation Engine

111

6.1.7 Adding Sticky Notes to Your Workflow

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

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

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 .

6Automation Engine

112

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

6.1.8 Checking All the Workflow's Parameters

You can use the Parameter Inspector to quickly go over all your parameters, without having to gointo 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 / workflowcontrol 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 62 for details on how to use public parameters.

5. Close the Parameter Inspector when you are done.

6Automation Engine

113

6.2 Using Workflows

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

6.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 orvia 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) accessright (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 forthe workflow.

2. Select the workflow ticket to use.

• If you have launched workflows previously, the most recent workflow tickets you used arelisted 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.

6Automation Engine

114

Tip: Workflow tickets have Workflow as task type. You can use the search field in the SelectTicket 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 selectedthe 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 theirParameters (Public and other) access right, the workflow is launched on the file as soon asyou 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 thepublic parameters). Click the Launch button when you are done.

6Automation Engine

115

You can monitor the workflow's progress in the Files View's Task pane or in the Tasks View. SeeChecking the Workflow's Processing Status on page 117.

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

6.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 performsit.

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

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

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

2.

Click to open the workflow editor.

6Automation Engine

116

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 aWorkflow using Custom Tickets, Reusing a Task Chain Ticket to Build a Workflow, Building aNested 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 notsaved in the ticket.

4.

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 ).

6.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.

6Automation Engine

117

6.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’sTasks pane. You can see the Tasks pane in the Files, Product or Tasks views.


• : 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 workfloweditor.

6Automation Engine

118

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 yourworkflow step’s output.

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

6Automation Engine

119

You can also:

•Open a processed file in the Tasks view: right-click the file (if it is still being processed) or thestep 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 Showin Files View.

• Check all public parameter values used in this workflow: go to Advanced > Modify PublicParameter 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

.

6.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 workfloweditor.

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

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

3.

Click Launch .

7Automation Engine

120

7. Viewing Files in the Automation EngineViewer

7.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 graphicproduction data.

It can be launched directly from within the Automation Engine Pilot, on any Macintosh or WindowsPC in your network. Anywhere you can install and log on to an Automation Engine Pilot you can startthe 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 asecond Automation Engine Pilot (Pilot - File menu - New window) and opening a file in the AutomationEngine Viewer from there.

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

What does the Viewer offer you?

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

• 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 inopening very large files quickly. That is why the Automation Engine Viewer offers 2 view modes: withor without Prepared View Data.

• In case you do not prepare View Data, the server will stream the data to the Automation EngineViewer. When a large file has to be opened or compared or when the server is very busy, a delaycan 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 preparedView Data instantly. Zooming in will of course require object data streaming from the server, butthen for a smaller area.

For more information about creating View Data, see Prepare for Viewer (in the Automation EngineReference Manual).

7Automation Engine

121

7.2 Checking the Result in the Viewer

The Automation Engine Viewer can open different file types (PDF, AI, PSD...). For a full list, seeSupported File Types in the Reference Manual.

In the Files view, do one of the following:

• Click the word View next to your file.

• Right-click your file and select View...• Select your file and go to File > View .

7Automation Engine

122

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

7Automation Engine

123

7.3 Comparing Files

The Automation Engine Viewer is not only a powerful viewing tool, but also holds a strong comparetool. It is an ideal way to compare two files and have a close look at the differences, if needed perseparation, including changes in images (internal or referenced images).

7Automation Engine

124

While comparing you can use other tools like for example "view separations in separate windows",measure, (de)select, rotate, etc...

7Automation Engine

125

8Automation Engine

126

8. Integration with Other Applications

8.1 Integration with WebCenter

With the Approval Workflow, you can send documents to be approved from Automation Engine toWebCenter, 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 andminimum error.

8.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 createnew WebCenter Projects (already containing your Approvers) as needed, directly from AutomationEngine.

Note: Alternatively, you can set up a WebCenter Project with Approvers in WebCenter, and sendyour impositions to it from Automation Engine. But then you will only be able to create new Projectsfrom 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 a 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 hername, or the group name, from the Project Manager list.

• If desired, enter a description in the Description field.• To make the Project active, leave the Status as Active.

8Automation Engine

127

• To specify an optional due date, click the calendar control at the end of the Due On field andselect the desired due date. To set the due time, click the drop-down list box to the right ofthe calendar control.

Note: This is not the Approval Due Date. You will set the Approval Due Date when settingthe Approval Cycle.

• To use a custom thumbnail, click Specify New Thumbnail and enter the complete path andfilename in the associated field or Browse for it. To use the default thumbnail, leave that choiceselected.

6. Click Finish.

The Project is created.

8Automation Engine

128

Adding Members to a Project

1. Once the project is created, click the Invite members link.

This shows a list of the current WebCenter members.

2. Select the users or groups to add as members and click Continue.

8Automation Engine

129

3. Set the members’ permissions as desired. For Approval tasks, members need at least Viewpermissions (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.

8Automation Engine

130

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 approvethe document before it gets the approved status, or

• whether the approval of a single group member (select the group entry labeled as one ofgroup) 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 Approvers.

8Automation Engine

131

2. Click Add / Delete Approvers.

3. From the Project Members list, select the individual users or the groups you want to add.

Tip: Use Ctrl+Click to select multiple members.

4. Click the >> button to add the selected members to the Approvers list.

8Automation Engine

132

Note: The Project Manager is not automatically made an Approval User and must be explicitlyadded to the list of Approvers.

5. Click Change to add the selected Approvers to the Project.

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.

8Automation Engine

133

c) Go back to your Project page.

2. In the Project Actions menu on the right, click Save as Template.

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 andfilename in the associated field or Browse for it. To use the default thumbnail, leave that choiceselected.

8Automation Engine

134

4. Click Finish.

The Template is created.

8.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).

8Automation Engine

135

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 AreaNetwork:

• 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 AreaNetwork to be able to use the page list approval feature in WebCenter.

8Automation Engine

136

• 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’sName and Password specified in WebCenter by the WebCenter administrator.

6. Use the Check Connection button to check that your Automation Engine server is now connectedto your Webcenter server.

7. If you plan to send individual documents as well as impositions to your WebCenter server, fill inthe parameters in the Connect to JDF Processor area.

• To connect via Hot Folders, select Hot Folders and define an Upload Folder and a DownloadFolder.

• To connect through JMF, select JMF. The URL of your JDF Processor is filled in by default.

Note: You can use the Check button to check that the JMF connection is successful.

8. In the left panel, select the WebCenter connection you have just set up and click on it to renameit. You can also use File > Rename or F12 (on Windows).

9. Go to File > Save to save your WebCenter connection. You can also use Ctrl + S on Windowsor Command + S on Mac.

Note: To remove a WebCenter connection, select it in the left panel and go to File > Delete oruse the Delete key.

8.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.

8Automation Engine

137

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 theDetails 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.

8Automation Engine

138

Sending the Imposition to WebCenter

If your imposition contains several books, you must send the books one by one to WebCenter. Eachbook 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 > PrepareImposition 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.

8Automation Engine

139

Note: You can also send your imposition to a Project already existing in WebCenter. In thatcase, you don’t need to enter a Project Template. Note that this Project must have Approversdefined in WebCenter.

c) If you want to send your imposition to a subfolder in the project, enter that Folder’s name. Ifthis 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 inWebCenter. 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 anEncrypted password or SmartNames.

8Automation Engine

140

4. Modify the settings of the Approval tab:

a) Enable Start the Approval Cycle.b) Select a Due date and time.

8Automation Engine

141

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 fromWebCenter, and view the approval results in Automation Engine.

For more information, see the WebCenter manual.

8.1.4 Approving the Imposition in WebCenter

In WebCenter 7.1, you can:

• Approve / reject documents sent from Odystar, Nexus or Automation Engine as regulardocuments (see Approving a Document).

• Approve / reject documents FastImpose impositions added to the Pages View in AutomationEngine 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 Engineare recognized as Page Lists in WebCenter. Multipage files uploaded from within WebCenter, or fromOdystar, Nexus, or even other Automation Engine documents will never be treated as Page Lists.Instead, they are considered regular multipage PDF documents.

8Automation Engine

142

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 ForceApprove / Force Reject it if you need to overrule the approval status granted by the approvalusers.

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 anApproval 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.

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 versionof the page will be shown showing the choice you picked. Only a Pending status allows futurechanges.

If desired, you can add a comment in the Comment field. Submitted approvals and commentsare 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 imposedbooks or magazines. As such they are an important tool for commercial printers.

8Automation Engine

143

Page Lists are uploaded from a Automation Engine production server using the Pages View in theAutomation Engine Pilot.

Note: Only FastImpose impositions that have been added to the Pages View in Automation Engineare recognized as Page Lists in WebCenter. Multipage files uploaded from within WebCenter, or fromOdystar, 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 Listname 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 WebCenteras an approver, then navigate to the document (Page List) to approve, in the project created fromAutomation 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 moreinformation, 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 thePage List.

b) In the Approval area in the sidebar on the right of the Viewer window, select the appropriateapproval state (Approved, Rejected, Pending) from the list.

The Approval dialog opens in which you can add approval comments.

8Automation Engine

144

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 (usingApply 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.

d) Enter your comments, provide your password if required and click Commit.

8Automation Engine

145

• 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.

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.

8Automation Engine

146

a) Enter your comments, provide your password if required and click Commit.

8.1.5 Checking the Approval Results in Automation Engine

• To view the status of documents in a WebCenter Approval Cycle in Automation Engine, you canuse 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:

• In the Proofs View:

8Automation Engine

147

Note:

When you try to expose a sheet that contains a rejected page, you will get an error in theExpose task and an error status in the Plates View.

If you really need to expose the sheet anyway, you can overrule the WebCenter approval statusfrom 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 canuse SmartNames.

Important: Make sure this matches the Project Name of the project you created (or used) whensending your imposition from Automation Engine to WebCenter. See Sending the Imposition toWebCenter.

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 buttonto save it.

8Automation Engine

148

Once it is saved, you will be able to return to this configuration using the Load from Configurationbutton after any unwanted change.

7. Click the Show Documents button to view the documents in your WebCenter project.

8Automation Engine

149

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 allapprovers.

Note: The imposition layout can be approved even if some of its pages arerejected.

the page has been approved by all approvers, but it may have changed theimposition layout, which needs to be checked (for example for a new pagereplacing 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 atleast one approver.

8Automation Engine

150

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.

8.1.6 Overruling the WebCenter Approval

After your imposition has been approved or rejected in WebCenter, you can still overrule the approvalstatus 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 impositiondocument.

2. You can either:

•

Select a page of your document and use the and buttons in the View’s toolbarto approve/reject the document without entering a comment.

• 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.

8Automation Engine

151

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.

8.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 allowsyou to bring both Automation Engine and Nexus workflows in line, running them from within a singlecontrolling 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 Nexusserver.

8Automation Engine

152

Any public parameters that have been defined in the Nexus workflow (NeXML) will show up on theSend to Nexus ticket in Automation Engine. In addition, these public parameters are SmartName-enabled, 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 theirresulting files back to Automation Engine.

Behind the scenes, Automation Engine and Nexus communicate via the SOAP protocol, exchangingfiles and notifying each of other of their progress.

NeXML

Setting up public parameters in Nexus requires knowledge of NeXML. Please refer to the NeXMLManual for more information.

8.2.1 Setup on the Nexus Side

To enable the Automation Engine Pilot to launch Nexus workflows, you must perform a number ofsetup 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 onthe 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 canaccess, is ignored by the Automation Engine Pilot. As a result, Automation Engine Pilot operatorsautomatically 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 isselected.

Only Hot Folders that have Show in Shuttle enabled are published to the Nexus SOAP server andbecome 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.

8Automation Engine

153

Your Nexus workflow is now available for use with the Automation Engine Pilot.

8.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 inyour favorite web browser: http://NexusServerName:5182.

8.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 Nexusticket.

Additional integration features allow you to check the progress of the workflow in the AutomationEngine 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 Nexusworkflow (One Single Task).

• the bottom section of the ticket dialog contains fields for the public parameters for the workflowyou selected. These parameters can be different for every Nexus workflow (they are defined usingNeXML).

8Automation Engine

154

Note: You can also manage your Nexus workflow's public parameters (not one by one but as agroup) 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.

8Automation Engine

155

The Send to Nexus task appears in the Task List, where you can see the progress of the Nexusworkflow. 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 toNexus 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 chooseGo To Job in Nexus Manager to view the job in Nexus Manager (this command is only availableon Mac OS).

• In Nexus Manager, double-click the Copy to BackStage activity to view the job in the AutomationEngine Pilot.

Note: In order to jump from the Nexus Manager 9.0 to the Automation Engine Pilot, you mustconnect to Nexus Manager with a blank user name and the password awsnexus.

8.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 allowsyou to bring both Automation Engine and Odystar workflows in line, running them from within a singlecontrolling 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 Odystarserver. You can use the Send to Odystar ticket as a single task or as part of a more completeAutomation Engine workflow.

Any public parameters that have been defined in the Odystar workflow will show up in the Send toOdystar 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 resultingfiles back to Automation Engine.

Behind the scenes, Automation Engine and Odystar exchange files and notify each of other of theirprogress.

Example

• The Automation Engine workflow (top) sends the files to Odystar for additional processing beforeoutputting them to a proofer.

• The Odystar workflow (bottom) applies PrePress changes to the files before copying them backto Automation Engine, where they go through the rest of the workflow (Proof step).

8Automation Engine

156

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 toOdystar),

• re-normalize the files you get back from Odystar (add a Normalize PostScript / PDF / Illustrator8.0 File step after Send to Odystar).

8.3.1 Setup on the Odystar Side

To enable the Automation Engine Pilot to launch Odystar workflows, you must perform a number ofsetup 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.

8Automation Engine

157

Note: Make sure you have Read and Write permissions for those mounted volumes from yourOdystar 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 Softwarefolder.

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 forcommunication 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 shouldenter 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.

8Automation Engine

158

7. Make sure you add a Copy File gateway, with the Copy Back To Automation Engine modeselected, at the end of your workflow.

8Automation Engine

159

Your Odystar workflow is now available for use from the Automation Engine Pilot.

8.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.

8Automation Engine

160

Note: You can also test whether the Odystar Hub is online by browsing to the following url in yourfavorite web browser: http://OdystarServerNameorAddress:5182.

8.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 Odystarticket. 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 youselect in the Pilot (Separate Tasks), or whether you want to send all the selected files to oneOdystar workflow (One Single Task).

• the bottom section of the ticket dialog contains fields for the public parameters for the workflowyou selected. These parameters can be different for every Odystar workflow (they are defined inthe Inspector).

Note: You can also manage your Odystar workflow’s public parameters (not one by one but asa group) in your task ticket. See Managing Public Parameters in Your Ticket.

8Automation Engine

161

8Automation Engine

162

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 Odystarworkflow. 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 Sendto Odystar task (or as the output of the Send to Odystar workflow step when including the Send toOdystar ticket in an Automation Engine workflow - see the workflow example).

8.4 Integration with i-cut Suite

The i-cut Automate module in Automation Engine offers similar functionality to i-cut Layout, but in aworkflow 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.

8.4.1 i-cut Automate Workflow

You can combine the i-cut Automate tasks into a workflow to fit your needs. For example in theworkflow 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.

8Automation Engine

163

3. In the Add Parameters for Nesting task, the graphics are set to be repeated to fill the sheet (withthe 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 youdefine (margins, fill starting point, gutter, etc.).

6. The production files (print files and cut files), and if desired a nesting report, are created and sentto the location you define.

Tip:

If the Minimum Fill on the sheet isn't reached on the due date, you can for example send theremaining graphics to another Create Nested Layout task with a lower minimum fill percentage (orsee Create Nested Layout in the Reference Guide for more options).

8.5 Integration with Enfocus PitStop

You can integrate Enfocus PitStop with Automation Engine, to be able to preflight PDF files fromthe Pilot.

To preflight a file:

8Automation Engine

164

1. Go to Tools > Configure and set up the connection to PitStop (see Preflight Tools in the ReferenceGuide for more details).

2. Launch the Preflight via External Application task on your file (see Preflight via ExternalApplication in the Reference Guide for more details).

8.6 Integration with third party applications using HotFolders

The Integrate via External Hot Folder task allows you to integrate external prepress applications intoyour 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 bythe external application, as well as the Result subfolders in which the external application willoutput 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 hotfolder.

3. The external application picks up the files in its hot folder and processes them. The processedfiles 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 beenprocessed.

5. If it detects a file in the OK folder, Automation Engine copies it to the Output folder defined in theIntegrate 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.

8Automation Engine

165

8Automation Engine

166

Note: In the Error area of the ticket, you can define an amount of time after which the externalprocessing 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 specificdate).

8.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 retrievecustomer information, or link MIS jobs to Automation Engine products to better serve yourcustomers).

• Plan and trigger production through MIS to Automation Engine communication (for example, youcan trigger job creation in Automation Engine from the MIS, or plan plates production...).

8.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.

2.Click the Create New Hot Folder button .

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

8Automation Engine

167

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 theprocessing result).

8Automation Engine

168

6. Click OK.

The JDF Hot Folder is now listed in the Pilot’s Hot Folder View.

9Automation Engine

169

9. Use Case: Setting up a PackagingWorkflow

9.1 Build a Workflow

You can build workflows from zero or using custom tickets, you can migrate task chains toAutomation Engine workflows, and create nested workflows.

You can use Smart Names to use predefined values. You can also choose to have the prepressmanager build workflows that operators will use, or let the operators build workflows on the fly whileprocessing files. See Building Workflows

The following steps will help you build a Workflow like this:

9.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 selectPreflight Tools

1. From Start connect to the Preflight via External Application workflow step.

9Automation Engine

170

2. Double-click on the workflow step to edit its parameters. For more information go to Preflight viaExternal Application.

When Preflighting in a workflow, the Preflight via External Application workflow step has fouroutput pins:

9Automation Engine

171

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 checkedby an operator).

Wait for Action (Checkpoint)

Use the Wait for Action (Checkpoint) task to make your workflow stop at certain predefined pointsso 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 decidewhether 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.

9Automation Engine

172

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.

9Automation Engine

173

Tip: After connecting the Output states you can:

• Add an extra Output state to the checkpoint and connect it to the“Preflight via ExternalApplication”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, pleaseinsert the Mark file task in your workflow chain. If you don't want to evaluate an existing file, selectthe "Fail" task when the file that is to be copied or moved already exists in the output folder. SeeCopy Move File

9.1.2 Normalize your File

The Normalize PostScript / PDF / Illustrator 8.0 File generates a Normalized PDF file based on thepreflighted 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). Alltransparencies and layers will be flattened. If not checked, a normalized PDF file will be createdthat contains all typical PDF features (like transparencies and layers).

Workflow overview

9.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 Whatis Trapping?

9Automation Engine

174

There are three different Trap tasks;

Trap – Create Trap Layer: This task traps the input file according to the settings specified in the TrapColor 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 storedin 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 thetrapping. 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

9Automation Engine

175

9.1.4 View your file

Prepare for Viewer

The Prepare for Viewer task prepares view data for the Automation Engine Viewer. This view datawill help the Viewer to quickly open the file (the Viewer will use the prepared View Data instead ofasking 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. TheAutomation Engine Viewer is a powerful integrated Viewer and QA tool. The Automation EngineViewer offers:

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

• 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

9Automation Engine

176

Tip: You could add an extra Output state, ”Send to Proof” to the checkpoint, connecting toProof(FlexProof) to print HardProof.

9.1.5 Generate Step & Repeat

Mark

Use this to tag files that you will need to select later in the workflow (with the Select workflowcontrol). The file will be tagged as "Label" and after approved in Hold for Viewing, the Select willpickup 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 Markworkflow control).

• Enter the tag of the file.

9Automation Engine

177

For an example see Mark and Select.

Step & Repeat Tabular

This Workflow Step executes all Step and Repeat parameters (number of one-ups vertically andhorizontally, gap between one-ups, alignment, SmartMarks...) after which the server will output thesheet layout. The ticket's input fields also accept SQL queries, so that information stored in adatabase can be used to drive the sheet layout creation. See Step & Repeat Tabular.

Workflow Overview

9.1.6 Create Report

Create Report (ReportMaker)

The ReportMaker task is used to automate the creation of design print cards (in French: fichetechnique, in German: Drueck Karten).

The idea is that you generate reports containing all kind of information: file name, used inks, name ofthe operator, an image of the file. All this information is defined in a report template, then this template

9Automation Engine

178

is used to generate a specific report. For more information about templates, see ReportMakerTemplates.

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, ColorManagement…

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 FTPaccount 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 WebCenterProject.

Workflow Overview

9Automation Engine

179

9.2 Use Shuttle in the Workflow

9.2.1 What is Shuttle

Shuttle is a small stand-alone application that enables you to submit files to Automation Engine tasksor workflows, and monitor their progress. You can use Shuttle to connect to several servers. TheShuttle functionality is also integrated in ArtPro, Neo, PackEdge, Plato, FastImpose and in AdobeIllustrator 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 UserGuide.

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 EngineUser Guide.

Shuttle Client Setup

Set up your Shuttle client in the applications you use. See Shuttle Clients Setup, Automation EngineUser Guide.

Shared Folder Setup

You also need to make sure that the relevant servers shared folders are mounted on the Shuttleclients machines, with the appropriate Read and Write permissions. For Automation Engine, theshared 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.

9.2.2 What are Public Parameters

Operators or an administrator of the Automation Engine workflow determines which PublicParameters can be defined for submitting files through Shuttle. A common use case is to avoidmistakes by allowing only a choice of predefined values. Public Parameters reduce the need orpredefined tasks. The owner of the ticket can easily change values before submitting new files.

9.2.3 Making Your Tickets Public

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


#

9Automation Engine

180

• In the Ticket view, right-click your ticket and select Public Ticket.

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


Public parameters are ticket parameters that operators can define for submitting files through Shuttle.




Attention: You need to define which parameters are public before files are submitted to yourworkflow.






9Automation Engine

181







9Automation Engine

182



Managing Public Parameters in Your Ticket

Once you have made parameters public in your ticket, you can have an overview of your publicparameters 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.

9Automation Engine

183

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

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

9Automation Engine

184

2. You can:

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


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



9Automation Engine

185









9Automation Engine

186








9Automation Engine

187

9.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 theproduction file without having to change the workflow ticket.

9Automation Engine

188

9.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.

9Automation Engine

189

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 willautomatically 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.• Use Command + S (on Mac).

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

9Automation Engine

190

Note:



Launching Files from PackEdge

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



9Automation Engine

191



Note: For more information on public parameters, see Using Public Parameters.


9Automation Engine

192

Tip:

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

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

2. Drag it into your application’s toolbar.3.

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