Task Node Settings

Setting up tasks in process templates

Each task node used in the process template has different settings to administer the functionality needed to execute the task once it is used in a project. The settings drive the behavior for each task and may vary from type to type. See process templates for information on how templates are set up.

What are task nodes?

The process template is created by selecting one or more task nodes, including tasks, milestones, and decisions to create a workflow  template that will meet specific business needs. For example, to create a template that contains a review cycle, you would include tasks for Upload File for Approval, Review, and Approval. Projects created from these templates, will always contain the same tasks used to create the template.

The following lists and describes the task nodes available to create a process template.

Standard Task

These are tasks you accomplish and complete outside of BLUE. Examples would be the project kickoff meeting, calling a supplier, or printing a file.

Standard tasks also support automation capability, which executes a script when a task performer tries to complete a data entry Standard task. The script validates the data and only allows the task to complete if the validation is successful.

Note: Automation is an advanced feature and may not be available in your system.

To set up a Standard task, enter the desired information for the following fields. All values are saved automatically and will be validated when the process template is saved. Below is a description for each field.

Field
Description
Name
Enter a name that best describes the task and what it will be used for.
Type
This will describe the type of task being used. This is a system field and contains non-editable text.
Swimlane
This defines what group resource will be used for this task. You can create one or more swimlanes by clicking on “Create Swimlane” or use an existing one. When using a swimlane, you can define who the default user will be for that group.
Duration
Define the number of days allotted for this task. These are used as a base duration, and can be adjusted in projects created from this template.
Allow Delegation
If checked, allows task owners in the project to be able to delegate their tasks to other members of their group.
Notify Subscribers
If checked, allows project owners to add subscribers to this task in the project, so on completion of the task, the recipients will be notified that it was completed. An optional message can be added to accompany the email notification. This message cannot be changed in the project.
Automation Script (JS)
Add a custom validation script that will be executed when the task performer tries to complete a data entry Standard task. The task will only be allowed to complete if the validation is successful. Otherwise, the task performer sees an error message indicating what the problem is.
Note: Automation is an advanced feature and may not be available in your system.
Project Attributes
Lists the attribute fields that were selected at the project level. These cannot be removed from a task, but you can select which ones to show or hide and which ones can be edited.
Task Attributes
Lists the attribute fields that were selected for this task. You can add attribute fields, remove them, or sort them in the desired order.

Upload Reference Files

This task requires you to upload a file to BLUE. This is usually a reference file or supporting document that does not need to be routed for review and approval. This file can be accessed by any user who is involved with the project. You may also attach existing files to a project as a reference.

To set up an Upload Reference Files task, enter the desired information for the following fields:

Field
Description
Name
Enter a name that best describes the task and what it will be used for.
Type
This will describe the type of task being used. This is a system field and contains non-editable text.
Swimlane
This defines what group resource will be used for this task. You can create one or more swimlanes by clicking on “Create Swimlane” or use an existing one. When using a swimlane, you can define who the default user will be for that group.
Duration
Define the number of days designated for this type of task. These are used as a base duration, and can be adjusted in projects created from this template.
Allow Delegation
If checked, allows task owners in the project to be able to delegate their tasks to other members of their group.
Notify Subscribers
If checked, allows project owners to add subscribers to this task in the project, so on completion of the task, the recipients will be notified that it was completed. An optional message can be added to accompany the email notification. This message cannot be changed in the project.
Reference File Visibility
The “Allow files to be visible in all tasks” checkbox allows administrators to decide if the files uploaded using this task will be allowed throughout the project or not. See Reference Files for rules and information on controlling who can view reference files.
Project Attributes
Lists the attribute fields that were selected at the project level. These cannot be removed from a task, but you can select which ones to show or hide and which ones can be edited.
Task Attributes
Lists the attribute fields that were selected for this task. You can add attribute fields, remove them, or sort them in the desired order.

Automation

The Automation node is a task within the workflow that allows for custom JavaScript code to be executed when the task is active or becomes in progress. See Automation Node for specific information on setting up the automation scripts.

To set up an Automation task, enter the desired information for the following fields:

Field
Description
Name
Enter a name that best describes the task and what it will be used for. The length of the automation task name must not exceed 255 characters.
Type
This will describe the type of task being used. This is a system field and contains non-editable text.
Notify Subscribers
If checked, allows project owners to add subscribers to this task in the project, so on completion of the task, the recipients will be notified that it was completed. An optional message can be added to accompany the email notification. This message cannot be changed in the project.
Automation Script
Editing this field allows the user to add in custom script to have the system execute a set of commands when the automation task is in progress.
Send Error Email To
 In this section, you can define who will get email notifications when the automation task has been executed and errors occur.
On Error
This section, you can choose what the system should do in the workflow if the automation task fails to execute, or an error occurs.
Project Attributes
Lists the attribute fields that were selected at the project level. Here you can select which ones to show or hide on this task.
Task Attributes
Lists the attribute fields that were selected at the task level. You can add attribute fields to be used for the selected task.

System Decision

The System Decision node allows you to skip a task or sub-process within the workflow by using expressions to determine the transition (True or False) to follow. See System Decision node for specific information on setting up the decision expressions.

To set up a system decision, enter the desired information for the following fields:

Field
Description
Name
Enter a name that best describes the task and what it will be used for.
Type
This will describe the type of task being used. This is a system field and contains non-editable text.
Decision Expression
Editing this field allows the user to add in custom script to have the system execute a set of commands when the automation task is in progress. See System Decision node.
Project Attributes
Lists the attribute fields that were selected at the project level. Here you can select which ones to show or hide on this task.
Task Attributes
Lists the attribute fields that were selected at the task level. You can add attribute fields to be used for the selected task.

Milestone

These are markers for milestone events in the project. Milestones can be placed at any level of the project schedule. These tasks do not have task owners and are reached automatically by the workflow’s progression.

To set up a milestone, enter the desired information for the following fields:

Field
Description
Name
Enter a name that best describes the task and what it will be used for.
Type
This will describe the type of task being used. This is a system field and contains non-editable text.
Notify Subscribers
If checked, allows project owners to add subscribers to this task in the project, so on completion of the task, the recipients will be notified that it was completed. An optional message can be added to accompany the email notification. This message cannot be changed in the project.
Project Attributes
Lists the attribute fields that were selected at the project level. These cannot be removed from a task, but you can select which ones to show or hide and which ones can be edited.
Task Attributes
Lists the attribute fields that were selected for this task. You can add attribute fields, remove them, or sort them in the desired order.

Complete Form

Forms provide a way for users to enter and view attribute fields in a format that closely resembles the order and arrangement of data in legacy systems or physical paper forms. A form may be configured as a simple data entry task, or it may be configured to save the form as a reference file or as approval candidate within a workflow. See Form Administration for more information about setting up forms, and Form Task Nodes for more information about configuring Complete Form task nodes.

To set up a complete form task, enter the desired information for the following fields:

Field
Description
Name
Enter a name that best describes the task and what it will be used for.
Type
This will describe the type of task being used. This is a system field and contains non-editable text.
Swimlane
This defines what group resource will be used for this task. You can create one or more swimlanes by clicking on “Create Swimlane” or use an existing one. When using a swimlane, you can define who the default user will be for that group.
Duration
Define the number of days designated for this type of task. These are used as a base duration, and can be adjusted in projects created from this template.
Form
Select an existing form to use for this task. See Form Administration for more information about setting up forms.
Form Name Expresssion
A name expression can be defined to automatically name the completed form. See Auto Naming for more information about defining auto form name expression.
Allow Delegation
If checked, allows task owners in the project to be able to delegate their tasks to other members of their group.
Notify Subscribers
If checked, allows project owners to add subscribers to this task in the project, so on completion of the task, the recipients will be notified that it was completed. An optional message can be added to accompany the email notification. This message cannot be changed in the project.
Save form as…
Select an option for the completed form to be saved in the project as the approval candidate or a reference file.
– Save form as reference file: choose the File Type and status for the Uploaded state.
– Save form as approval candidate: choose the File Type, and statuses for the Approved, Rejected, Terminated, and Submitted states, and enter the Approval Candidate Id.
Choose None if this will just be a data entry form task.
Project Attributes
Lists the attribute fields that were selected at the project level. These cannot be removed from a task, but you can select which ones to show or hide and which ones can be edited.
Task Attributes
Lists the attribute fields that were selected for this task. You can add attribute fields, remove them, or sort them in the desired order.

Select Base Artwork from Library

This task allows a user to select one file from the library to use as a base artwork file for a new file that will be routed for approval. Depending on the template settings for this task, the user attaching the base artwork may be able to make annotations to indicate what changes are needed for the new artwork file.

You can also add some Review tasks after the Select Base Artwork from Library task, before the cycle, so that multiple reviewers can markup the base artwork.

See Tasks for more information on executing a Select Base Artwork from Library task.

To set up a Select Base Artwork from Library task, enter the desired information for the following fields:

Field
Description
Name
Enter a name that best describes the task and what it will be used for.
Type
This will describe the type of task being used. This is a system field and contains non-editable text.
Swimlane
This defines what group resource will be used for this task. You can create one or more swimlanes by clicking on “Create Swimlane” or use an existing one. When using a swimlane, you can define who the default user will be for that group.
Duration
Define the number of days designated for this type of task. These are used as a base duration, and can be adjusted in projects created from this template.
Approval Candidate ID
Enter a unique ID for the approval process of the approval file. The same ID must be used in all tasks of the same approval process, including the Select Base Artwork from Library task and base artwork Review tasks.
Allow Delegation
If checked, allows task owners in the project to be able to delegate their tasks to other members of their group.
Notify Subscribers
If checked, allows project owners to add subscribers to this task in the project, so on completion of the task, the recipients will be notified that it was completed. An optional message can be added to accompany the email notification. This message cannot be changed in the project.
Allow Annotations
If checked, the task owner will be able to add annotations to the base artwork file.
Allowed File Types
Select one or more system file types that can be used to search for and select files from the library.
Project Attributes
Lists the attribute fields that were selected at the project level. These cannot be removed from a task, but you can select which ones to show or hide and which ones can be edited.
Task Attributes
Lists the attribute fields that were selected for this task. You can add attribute fields, remove them, or sort them in the desired order.

Base Artwork Review

Multiple review tasks can be configured before an approval cycle, with an Approval Candidate Id that matches the preceding Select Base Artwork (SBA) node, allowing multiple users to annotate the base artwork file. Or, if your template is set up to automatically create sub-processes (ASPG), you could add some base artwork Review tasks before the approval cycle. When a Review task is added before the cycle, the assigned reviewers will be able to review and markup the base artwork file.

Base artwork Review tasks are supported in five types of workflows:

– One single SBA task in a project

– Multiple SBA tasks in a project with different Approval Candidate IDs

– One SBA task providing a base artwork for multiple sub-processes

–  An SBA task with the base artwork file from the generated ASPG sub-process

–  An ASPG sub-process without an SBA task

See the Review task configuration below for task node settings.

Upload File for Approval

This task requires you to upload a file for review and / or approval. After uploading a file, the submitter marks the task as complete in BLUE.

To set up an Upload File for Approval task, enter the desired information for the following fields:

Field
Description
Name
Enter a name that best describes the task and what it will be used for.
Type
This will describe the type of task being used. This is a system field and contains non-editable text.
Swimlane
This defines what group resource will be used for this task. You can create one or more swimlanes by clicking on “Create Swimlane” or use an existing one. When using a swimlane, you can define who the default user will be for that group.
Duration
Define the number of days designated for this type of task. These are used as a base duration, and can be adjusted in projects created from this template.
Approval Candidate ID
Enter a unique ID for the approval process of the approval file. The same ID must be used in all tasks of the same approval process, as well as the Select Base Artwork from Library and base artwork Review tasks.
Allow Delegation
If checked, allows task owners in the project to be able to delegate their tasks to other members of their group.
Allow Cross Sub-Process Comparison
If checked, task owners who are uploading or reviewing the approval file can compare it with approval files from other sub-processes with same approval candidate ID.
See Cross Sub-Process Comparison.
Notify Subscribers
If checked, allows project owners to add subscribers to this task in the project, so on completion of the task, the recipients will be notified that it was completed. An optional message can be added to accompany the email notification. This message cannot be changed in the project.
Project Attributes
Lists the attribute fields that were selected at the project level. These cannot be removed from a task, but you can select which ones to show or hide and which ones can be edited.
Task Attributes
Lists the attribute fields that were selected for this task. You can add attribute fields, remove them, or sort them in the desired order.

Review

This task displays the file that was uploaded for review. Reviewers add comments and mark the task as complete in online proofing.

There are two ways in which the Review task can be added to a workflow:

– Before the cycle – allowing review of the base artwork (either the ASPG or SBA file).
– Inside the cycle – allowing review of the approval candidate.

The location of the task determine which type of file is under review.

To set up a review task, enter the desired information for the following fields:

Field
Description
Name
Enter a name that best describes the task and what it will be used for.
Type
This will describe the type of task being used. This is a system field and contains non-editable text.
Swimlane
This defines what group resource will be used for this task. You can create one or more swimlanes by clicking on “Create Swimlane” or use an existing one. When using a swimlane, you can define who the default user will be for that group.
Duration
Define the number of days designated for this type of task. These are used as a base duration, and can be adjusted in projects created from this template.
Approval Candidate ID
Enter a unique ID for the approval process of the approval file. The same ID must be used in all tasks of the same approval process, including the Select Base Artwork from Library task and base artwork Review tasks.
Allow Delegation
If checked, allows task owners in the project to be able to delegate their tasks to other members of their group.
Allow Cross Sub-Process Comparison
If checked, task owners who are uploading or reviewing the approval file can compare it with approval files from other sub-processes with same approval candidate ID.
See Cross Sub-Process Comparison.
Note: When the Review task is before the cycle and is used for reviewing the base artwork, this setting will have no effect.
Notify Subscribers
If checked, allows project owners to add subscribers to this task in the project, so on completion of the task, the recipients will be notified that it was completed. An optional message can be added to accompany the email notification. This message cannot be changed in the project.
Enable Annotation Status
Note: This template option is only available when the system has configured annotations states.
For a gatekeeper review task, this setting allows this reviewer to set a status for annotations. Whether or not every annotation must have a status is a configurable option.
– Off: the user cannot set annotation statuses, but will be able to see them if they were set in another task.
– On and Warn: the user can set annotation statuses in this task; the system will warn the user if they try to complete the task and some annotations do not have a status but allow them to continue.

– On and Enforce: the user can set annotation statuses in this task; the user must set an annotation status for every annotation in order to complete their task.
Project Attributes
Lists the attribute fields that were selected at the project level. These cannot be removed from a task, but you can select which ones to show or hide and which ones can be edited.
Task Attributes
Lists the attribute fields that were selected for this task. You can add attribute fields, remove them, or sort them in the desired order.

Approval

This task displays the file that was uploaded for review and approval. Approvers add comments and make a decision to approve or reject the file in online proofing.

The Approval task must be located inside the cycle, allowing review of the approval candidate.

To set up an approval task, enter the desired information for the following fields:

Field
Description
Name
Enter a name that best describes the task and what it will be used for.
Type
This will describe the type of task being used. This is a system field and contains non-editable text.
Swimlane
This defines what group resource will be used for this task. You can create one or more swimlanes by clicking on “Create Swimlane” or use an existing one. When using a swimlane, you can define who the default user will be for that group.
Duration
Define the number of days designated for this type of task. These are used as a base duration, and can be adjusted in projects created from this template.
Approval Candidate ID
Enter a unique ID for the approval process of the approval file. The same ID must be used in all tasks of the same approval process, including the Select Base Artwork from Library task and base artwork Review tasks.
Allow Delegation
If checked, allows task owners in the project to be able to delegate their tasks to other members of their group.
Allow Cross Sub-Process Comparison
If checked, task owners who are uploading or reviewing the approval file can compare it with approval files from other sub-processes with same approval candidate ID. See Cross Sub-Process Comparison.
Notify Subscribers
If checked, allows project owners to add subscribers to this task in the project, so on completion of the task, the recipients will be notified that it was completed. An optional message can be added to accompany the email notification. This message cannot be changed in the project.
Enable Annotation Status
Note: This template option is only available when the system has configured annotations states.
For a gatekeeper approval task, this setting allows this approver to set a status for annotations. Whether or not every annotation must have a status is a configurable option.
– Off: the user cannot set annotation statuses, but will be able to see them if they were set in another task.
– On and Warn: the user can set annotation statuses in this task; the system will warn the user if they try to complete the task and some annotations do not have a status but allow them to continue.
– On and Enforce: the user can set annotation statuses in this task; the user must set an annotation status for every annotation in order to complete the task.
Project Attributes
Lists the attribute fields that were selected at the project level. These cannot be removed from a task, but you can select which ones to show or hide and which ones can be edited.
Task Attributes
Lists the attribute fields that were selected for this task. You can add attribute fields, remove them, or sort them in the desired order.

Auto Transfer to Library

Having an Auto Transfer to Library node in a process template means that when projects are executed with this task in its workflow, the file that is approved in the process will be automatically transferred to the BLUE asset library. This will ensure that the approved file is stored in the library and is available to users who will need to access the file. This automated task can be used to transfer an approved artwork, or a set of Packshots to the Asset Library.

You can add the ATTL node from the left Tasks panel in the process template. In a typical process, the ATTL node is likely to be the last step in the workflow, after the file’s approval step.

Here is a workflow that transfers approved artwork to the Asset Library:

Here is a workflow that transfers Packshots to the Asset Library:

 

To set up an Auto Transfer to Library task, enter the desired information for the following fields:

Field
Description
Name
Enter a name that best describes the task and what it will be used for.
Type
This will describe the type of task being used. This is a system field and contains non-editable text.
Approval Candidate ID
Enter the Approval candidate ID for the file that you would like to transfer to the Asset Library, which can either be the Artwork Approval Candidate Id or the Packshots Approval Candidate Id.
The Auto Transfer to Library node needs to be associate with an approval file. When transferring approved artwork, the approval candidate ID must be the same as the one for the file being approved, so this Id should match the one used in the approval cycle tasks (Upload File for Approval, Review, Approval). When transferring Packshots, this Id should match the Id used on the Create Packshots node.
In both cases, the same approval candidate ID must be used for all tasks within the same approval process.
Notify Subscribers
If selected, allows project owners to add subscribers to this task in the project, so on completion of the task, the recipients will be notified that it was completed. An optional message can be added to accompany the email notification. This message cannot be changed in the project.
Asset Library Location Expression
The expression required to indicate an asset library location is based on Velocity Template Language. Entering an expression here will indicate to the system where to transfer a file once it is approved. See Velocity Template Language for examples of expressions.
Base Artwork Location
The base artwork location option works in conjunction with the Select base artwork task and the auto sub-process generator. If the workflow contains a base artwork file, then the Auto Transfer to Library task will automatically transfer the newly approved file to the location of the selected base artwork.
Version File
To indicate that the artwork file being transferred should become a new version of an existing file in the location folder, select the Version File checkbox. This will ensure that on completion of the approval process, when the approval file is transferred to the indicated location, if a file of the same name is found, then the new file will become the next numerical version. For example, if there is a version 1 of “Softgels-75ct.pdf,” then the new file will be a version 2.
If you do not want the new file to become the version of another file, or if it will be a new version 1, then do not check the Version File checkbox. This will ensure that the new file is always a new file in the indicated location, regardless of its name.
This option is available for transferring approved artwork to the Asset Library. It is not supported when transferring Packshots to the Asset Library (and will be disabled when the task is configured to transfer Packshots).
Project Attributes
Lists the attribute fields that were selected at the project level. These cannot be removed from a task, but you can select which ones to show or hide and which ones can be edited.
Task Attributes
Lists the attribute fields that were selected for this task. You can add attribute fields, remove them, or sort them in the desired order.

Manual Transfer to Library

Having a Manual Transfer to Library node in a process template means that when projects are executed with this task in its workflow, a task owner can choose where the approved file will be stored in the BLUE asset library or if it will be versioned.

Note: The Manual Transfer To Library task is used in conjunction with the Approval Task, as the transfer task only moves approved files.

To set up a Manual Transfer to Library task, enter the desired information for the following fields:

Field
Description
Name
Enter a name that best describes the task and what it will be used for.
Type
This will describe the type of task being used. This is a system field and contains non-editable text.
Swimlane
This defines what group resource will be used for this task. You can create one or more swimlanes by clicking on “Create Swimlane” or use an existing one. When using a swimlane, you can define who the default user will be for that group.
Duration
Define the number of days designated for this type of task. These are used as a base duration, and can be adjusted in projects created from this template.
Approval Candidate ID
Enter a unique ID for the approval process of the approval file. The same ID must be used in all tasks of the same approval process.
Allow Delegation
If checked, allows task owners in the project to be able to delegate their tasks to other members of their group.
Notify Subscribers
If checked, allows project owners to add subscribers to this task in the project, so on completion of the task, the recipients will be notified that it was completed. An optional message can be added to accompany the email notification. This message cannot be changed in the project.
Lock Attributes
If checked, this will prevent the end user from being able to enter or modify attribute values for the asset.
If unchecked, the user will be allowed to enter or modify the values of attribute fields for the asset.  Values of matching attribute fields known to the task will be mapped to corresponding asset fields as default values.  If the end user changes the values for the asset, the updated values will only be reflected in asset metadata.
Allowed Asset Library Folder and File types
Select one or more system folder or file types that can be used to search for and select folders and files from the library. This limits the Folders and/or File Types available to the end user to choose as a target for the transfer task.
Project Attributes
Lists the attribute fields that were selected at the project level. These cannot be removed from a task, but you can select which ones to show or hide and which ones can be edited.
Task Attributes
Lists the attribute fields that were selected for this task. You can add attribute fields, remove them, or sort them in the desired order.

Auto Transfer to MediaBeacon

In order to use the Auto Transfer to MediaBeacon node, a back-end connection must be established between BLUE and MediaBeacon.

Having an Auto Transfer to MediaBeacon node in a process template means that when projects are executed with this task in its workflow, the file that is approved in the process will be automatically transferred to the MediaBeacon library.

Best practice is to manage artwork files in BLUE and send a copy of the file to MediaBeacon to provide additional access. For example, you could add an Auto Transfer to Library task after the Auto Transfer to MediaBeacon task. This will ensure that the approved file is stored in both libraries and is available to users who will need to access the file.

Note: There can only be one Auto Transfer to MediaBeacon node associated with an approval candidate.

Transferring Attributes to MediaBeacon

Similar to ATTL, all attribute fields which are visible to the ATMB task will attempt to be transferred. If the fields exist within MediaBeacon and have been configured properly, then the values will be transferred.

Attribute values within MediaBeacon are managed separately from BLUE. In most cases, if the value doesn’t exist in MediaBeacon when the file is transferred, it will be added.

Ask your system administrator for more information about transferring attribute fields and instructions on how to set these up for use with this task.

To set up an Auto Transfer to MediaBeacon task, enter the desired information for the following fields:

Field
Description
Name
Enter a name that best describes the task and what it will be used for.
Type
This will describe the type of task being used. This is a system field and contains non-editable text.
Approval Candidate ID
As part of the approval process, the ATMB node will need to associate itself with the approval file. The approval candidate ID must be the same as the one the file being approved, so this should match the one used in the tasks in the approval process (upload for approval, review, approval).
Notify Subscribers
If checked, allows project owners to add subscribers to this task in the project, so on completion of the task, the recipients will be notified that it was completed. An optional message can be added to accompany the email notification. This message cannot be changed in the project.
Location
The expression required to indicate an asset library location.
The transfer will work with or without a preceding or trailing slash.
For example, both of these would be successful:
artwork/2019/Blue Daily/
/artwork/2019/Blue Daily
See Velocity Template Language for more information, including examples.
Auto Create Folders in Location
Whether or not to automatically create the folder in the MediaBeacon Asset Library if it does not exist yet.
This setting is specific to this task node, allowing for a folder to be automatically created within MediaBeacon based on the generated value provided. When this checkbox is NOT checked, it will work similar to Auto Transfer to Library, and provide an error message if the folder cannot be created.
Project Attributes
Lists the attribute fields that were selected at the project level. These cannot be removed from a task, but you can select which ones to show or hide and which ones can be edited.
Task Attributes
Lists the attribute fields that were selected for this task. You can add attribute fields, remove them, or sort them in the desired order.

Create Packshots

The Create Packshots workflow requires advanced configuration and will be configured by your BLUE system administrator. Here is a high level summary of the supported options.

 

Field Description
Name

 Enter a descriptive task name, for example:

“Create Packshots” or “Create and Route Packshots”.
Type Create Packshots
Notify Subscribers Select this check checkbox to enable subscriber notifications that will be sent out when this task is completed. Enter an optional subscriber message.
Artwork Approval Candidate Id Enter the Approval Candidate Id that was used for the corresponding regular Artwork Approval cycle.
Structure File Type This dropdown contains all active Types in the system. Select the Packshot Structure File type that will be used for this task.
Packshots Approval Candidate Id Enter a unique Packshots Approval Candidate Id that will be used for the Packshots Approval Cycle and its associated Auto Transfer to Library task.
Save Packshots Report As…

This setting determines whether or not a Packshot report will be created.

Approval Candidate (best practice)

  • The Packshots report is created and is accessible from the Create Packshots task details panel, whether there is a Packshots approval cycle or not.
  • Choose this option when there is a Packshots approval cycle or if the report is needed for traceability purposes.
  • After choosing this option, fill in the file type and status mappings.

None

  • The Packshots report will never be created.
  • Choose this option if there is no Packshot approval cycle and the report is not needed for traceability purposes.
  •  The file type and status mappings are not needed.
File Type This drop down contains all active types in the system. Select the file Type for the Packshots report and final Packshots.
Approved Map the approved Packshots status to a BLUE status.
Rejected Map the rejected Packshots status to a BLUE status.
Terminated Map the terminated Packshots status to a BLUE status.
Submitted Map the submitted Packshots status to a BLUE status.
Send Error Email To: Select the users who will be notified if there is an error when creating the Packshots.
On Error Choose whether to suspend the sub-process or the project if there is an error creating the Packshots.
Attributes This task has, at a minimum, these fields extended to it:

  • Packshot Definition Set
  • At least one Structure File Identifier that will be used to identify the product, such as Dieline Number, and retrieve the Structure File from the Asset Library
  • Alignment fields (if the artwork will ALWAYS be created using Esko’s standards, these may be omitted on the template).
    • Artwork Box
    • Artwork Anchor
    • CAD Orientation
    • CAD Anchor
    • Offset X Coordinates
    • Offset Y Coordinates

Approval Decision

The Approval Decision node will progress the workflow, depending on whether an approval candidate was approved or rejected. The node recognizes that if the approval file is rejected, it will return to the Upload file for Approval task, and if it is approved, the workflow will progress to the next sequential task.

To set up an Approval Decision node, enter the desired information for the following fields:

Name
Enter a name that best describes the task and what it will be used for.
Type
This will describe the type of task being used. This is a system field and contains non-editable text.
Approval Candidate ID
Enter a unique ID for the approval process of the approval file. The same ID must be used in all tasks of the same approval process.
Project Attributes
Lists the attribute fields that were selected at the project level. These cannot be removed from a task, but you can select which ones to show or hide and which ones can be edited.
Task Attributes
Lists the attribute fields that were selected for this task. You can add attribute fields, remove them, or sort them in the desired order.

Guardrails

Decision Nodes

When using two or more decision nodes in your template, including a system decision or approval decision, it is important that these do not overlap each other. Each decision node must point back directly to another node, such as the Upload for Approval node, without it crossing the other decision node. Doing so, may cause the template setup to break, remove transitions, or not validate and save.

If the template is saved with decision nodes overlapping, but with errors, this will cause projects that are created from that template to not progress forward. If you encounter a project created from a template like this, contact your administrator.