Step 3: Create Workflow Template (Enterprise Plan)

The workflow template decides how a project moves from start to finish: the tasks in the project, who works on each task, how long each task takes, and where the project goes after each action, such as Approve or Reject. The Create Workflow Template step opens when you select Next in Step 2: Create Form Template (Enterprise Plan).

Note: The process for creating a workflow template varies depending on the user’s plan. This article focuses on creating a workflow template in the Enterprise Plan. For details on creating a workflow template in the Growth Plan, refer to Step 2: Create Workflow Template (Growth Plan).

This article covers project templates without Copy Manager. To create a project template with Copy Manager, refer to Configure Project Template with Copy Manager.

01. Workflow Template Selection - Choose Your Template Creation Method

ManageArtworks offers two convenient ways to build your workflow template:

  • Create New Workflow Template: Select this option to design a workflow from scratch for unique project workflows, tailoring it specifically to your process.
  • Copy and Create Workflow Template: Select this option to save time by modifying an existing workflow template. This is ideal for leveraging familiar structures for similar workflows.

02. Pictorial View Reference

The Pictorial View, displayed alongside the task list, provides a visual representation of the workflow. It uses color-coded indicators to help users quickly understand task status and overall project flow during runtime.

To understand how the pictorial view appears to end users and the meaning of each color code, refer to the Pictorial View Reference section.

In the Admin module, the pictorial view updates in real time as tasks are added or modified in the workflow template.

To close the pictorial view, select the Close (βœ•) icon.

03. Build Your Workflow (Create New Workflow Template Method)

1. Create a New Workflow Template

  1. Select Create New Workflow Template.
  2. Select the edit icon next to the workflow template placeholder name and enter a descriptive name (e.g., Artwork Approval) for your workflow template.

2. Configure the Start Activity

  1. Select the Edit button in the action column associated with the Start activity. This is where you define who can initiate the project using this template. The Start activity contains four tabs for customization:
    • Task Information
    • Actions
    • Validation
    • Instructions.
Note: Only users assigned to the Start activity can access the template and initiate the project. By default, the user who creates the template is automatically assigned to the Start activity.

 

Task Information Tab

This tab allows you to assign users and configure optional security settings.

  1. Users: Assign the task to specific users, teams, form fields, or users from previous tasks. Refer to the "Task Assignment Options" section for detailed instructions on assigning users.
  2. E-Signature (Optional): Enable an additional layer of security requiring users to enter their password to confirm their identity before initiating the project.

 

Actions Tab

Use this tab to configure how users initiate the project and define what happens afterward.

  1. Action 1 Name: Enter the desired label for the button users will click to initiate the project (e.g., "Initiate New Request")
  2. Action 1 Status: Specify the outcome or status displayed in the audit log after the project is initiated (e.g., "Initiated").
  3. Goes to: Choose the next workflow step after the Start activity is completed. By default, the system will move to the initial task in your sequence. If no other task types have been added, this field will be blank, and you can leave it as is. Upon adding tasks to the workflow, the initial task in your sequence will be automatically populated here.

 

Validation Tab (Optional)

  1. This tab allows you to set restrictions similar to normal and decision tasks. Refer to step 5. Validation Tab section to know more this tab.

Instructions Tab (Optional)

  1. Add clear instructions to guide users on initiating the project.

3. Save Start Activity

  1. Once the Start activity has been configured as desired, select Save to apply the configurations.

4. Add Tasks to Your Workflow

  1. You can add tasks to your workflow in two ways:
    1. Using the Plus Icon: Select the + icon next to an existing task and choose the desired task type. The selected task will be inserted immediately after the task where you clicked the icon.


       
    2. Using the Add a Task Button: Select Add a Task at the top right and select the task type you want to add.

Task Types

  • Normal Task: Use this for standard workflow activities such as uploading deliverables or completing defined steps. This is the most commonly used task type.
  • Decision Task: Use this when the task involves approvals, rejections, or decision-making that determines the next path in the workflow.
  • Email Activity: Use this to send custom emails upon task completion to participants who are not part of the workflow task. This allows runtime configuration of email recipients.
    • By default, the system sends automated emails (such as task assignment, rejection, and completion notifications) to task participants. You can also configure custom email alerts for additional participants (for example, sending completion notifications to managers) using the Customize Email Alerts option.
    • However, emails configured through Customize Email Alerts do not allow modifying recipients at runtime. To enable this flexibility, use Email Activity, where task participants or initiators can update email recipients during execution.
  • Add a Fork: Use this to create parallel tasks that run simultaneously. Each branch can contain either a Normal Task or a Decision Task, enabling concurrent workflow execution.
    • Forks can also be used to add child templates, allowing the project to split into multiple sub-projects based on the number of components.
    • Note: The Project Split option within the Fork menu is available only when the Multi-Level Approval Flow (Project and Component) is selected during Approval Flow configuration.

5. Configure a Normal Task

  1. Once you select Normal Task type from the menu, you will be presented with four tabs for customization:
    • Task Information
    • Actions
    • Validation
    • Instructions.
       

Task Information Tab

  1. Configure the following fields to define the task:
    • Activity Name: Enter a clear and descriptive name for the task (for example, Artwork Upload).
    • All or Anyone: Specify whether all assigned users must complete the task or if any one of the assigned users can complete it.
    • User: Assign the task to specific users, teams, form fields, or users from previous tasks. For more details, refer to the "Task Assignment Options" section.
    • Duration (Days): Define the number of days allocated to complete the task.
    • E-Signature (Optional): Enable this option to require users to reconfirm their identity by entering their password before completing the task.
    • Allow Participants for: Define which tabs can be accessed and modified by task participants during the task runtime. These permissions apply only while the task is active and do not extend before or after task completion.
      • Edit Project Info: Allows participants to add or modify project details in the Request Info tab.
      • Edit Components: Allows participants to add or modify component details in the Components tab.
      • Edit Files: Allows participants to upload or modify files in the Files tab.
      • Edit Stakeholder: Allows participants to modify task participants in the Task tab.

 

Task Assignment Options

You can assign tasks using the following options:

  • Users: Assign the task to specific individual users.
  • Teams: Assign the task to a group of users based on team attributes and collections.
  • Form Fields: Dynamically assign users based on values selected in form fields during project run time.
  • Task: Assign the task to users who were part of a previous task in the workflow.

You can configure any combination of these options. If multiple options are selected, the task will be assigned to all users derived from the selected configurations.

Notes: 

  • For the Start activity, task assignment is limited to Users and Teams only.
  • During project execution, participants can modify assignments only for Users and Teams. Assignments based on Form Fields and Task can be configured only in the Admin module.
    • To modify Form Field–based or Task-based assignments, the template must be updated and republished.
  • If Anyone is selected under All users or Anyone, the task will be completed when any one assigned user takes action.
    To ensure all assigned users complete the task, select All under All users or Anyone.

To configure task assignment:

  1. Select the User Settings icon. A Select Participants will appear.



     
  2. Add Users:
    Assign tasks to specific users:
    1. Select the Add Users drop-down menu.
    2. Select the desired users from the list.
      Note: By default, the user creating the template will be added.
    3. To remove a selected user(s), select the Close icon next to their name.
    4. To remove all the selected users, select Clear All.


       
  3. Add Teams:
    Assign tasks to entire teams (e.g., marketing, legal):
    1. Select the Team Attribute drop-down menu and select the desired attribute from the list (e.g., Department).
    2. Select the Collection drop-down menu and choose the relevant team from the list (e.g., Legal).
    3. To remove a selected team, select the Close icon next to the added team's name.
    4. To remove all the selected teams, select Clear All.


       
    5. Allow User Selection (Optional):
      • When enabled, users must select specific users from the selected team(s) before initiating the project.
      • When disabled, the task will be assigned to all available team members associated with the selected team(s) once project initiated.
  4. Add Form Fields:
    Assign tasks based on form field inputs:
    1. Select the Add Form Fields drop-down menu.
    2. Select the relevant form field from the list (e.g., Brand Name).
      Note: Only form fields included in the form template will appear in the list.
    3. For example, if "Brand A" is selected during project run time, the task will automatically be assigned to users linked with "Brand A."
    4. To remove a selected form field, select the Close icon next to the added form field name.
    5. To remove all the selected form fields, select Clear All.


       
  5. Add Task:
    Assign tasks to users based on previous task assignments:
    1. Select the Add Task drop-down menu.
    2. Select the desired previous task from the list.
      Note: Task assignments using this option are restricted to previously defined tasks.
    3. The task will be assigned to all users associated with the selected task.
    4. To remove a selected task, select the Close icon next to the added task.
    5. To remove all the selected tasks, select Clear All.


       
  6. After configuring the task assignment, select Save to finalize the user assignment settings.

 

Actions Tab

Use this tab to configure the labels and outcomes of the action button(s) for the task.

  1. Action 1 Name: Define the label for the button that users click to complete the task (for example, Submit).
  2. Action 1 Status: Specify the status of the task after the action is performed (for example, Submitted). This status is recorded in the audit log.
  3. Goes to: Select the next step in the workflow after this action is completed. If no subsequent tasks are available, this field will remain emptyβ€”leave it unchanged. Once additional tasks are added, the immediate next task in the workflow is automatically selected by default.

 

Validation Tab

Use this tab to configure validations that must be satisfied before a task can be completed.

  1. Component Form Validation: Ensures that the task cannot be completed unless at least one component is added in the Components tab.
    Note: This option is not available for Multi-Level Approval Flow (Project and Component). It is applicable only when a single-level approval flow is selected. In Multi-Level Approval Flow, component validation is handled automatically by the system before the project is split into child components. Ensure that the Edit Components option is enabled under the Task Information tab to use this feature.
    1. To enable this validation, select the Component Form Validation checkbox.


       
  2. Fill checklist: 
    Enable or disable checklists for the task.



    1. To activate the checklist feature, select the Fill Checklist checkbox. Once enabled, configure the following options:
      1. Apply Checklist For: Select the associated drop-down menu and select the asset type to which the checklist applies. Checklist items will appear only for the selected asset type.
        Note: Checklists are associated with file types. If the configured file type is not uploaded in the task, the checklist will not appear. To ensure checklist availability, configure the same file type as a Required File for the task.
         
      2. Select Checklist Group: Select the associated drop-down menu and select one or more checklist groups. Only the checklist items from the selected group(s) will be available during the task.
        Note: To configure the checklists group, refer to Create Checklist Group.
  3. User Confirmation: Enables a confirmation pop-up when users attempt to complete the task. This allows users to provide a summary or comments related to task completion, which will be recorded in the Comments tab of the project.
    Note: For Normal Tasks, even if the confirmation pop-up is enabled, users can complete the task without entering comments in the pop-up.
    1. To enable user confirmation pop-up, select the Confirmation popup enabled checkbox.


       
  4. File Validation: Define file-related validations required for task completion.
    Note: Ensure that participants have permission to edit files in the Task Information tab to use this feature.



    1. Required Files: 
      Specify file types that must be uploaded before completing the task. Task submission is blocked until all required files are uploaded. For example, if a task requires "Packaging Artwork" and "Dieline" files, you could choose these as mandatory file types.
      • Select the associated drop-down menu and select the required file types (e.g., "Packaging Artwork" and "Dieline").
      • Users will receive a warning message if they attempt to submit the task without uploading these mandatory file types during run time.
      • Submission will be blocked until the required files are uploaded.


         
    2. Optional File Types to Upload or Update: 
      Allow users to upload additional, non-mandatory files. If not uploaded, a warning is shown, but users can still proceed. 
      • Select the drop-down menu to select optional file types (e.g., "3D Model" or "KLD").
      • Uploading any of the selected optional file types will not trigger a warning. If the user attempts to submit the task without uploading any selected optional files, a warning message will appear. However, users can still proceed with submission by dismissing the warning.


         
  5. Mandatory field validations: 
    Set mandatory fields users must complete before moving to the next activity. 
    Note: Ensure that participants have permission to edit project info in the Task Information tab.
    1. Select Add Field and choose the required form fields.
    2. Choose the desired form fields from the list. These will appear under "Mandatory field validations."
      Note: Only fields included in the form template will be available for selection.
    3. To remove the added form fields from mandatory list, simply select the delete icon available next to the field name.
      Note: Mandatory fields defined in the Start Activity or previous activities are carried forward and cannot be removed in the current activity.


 

Instructions Tab (Optional)

  1. Add clear instructions to guide users on completing the task.

6. Save Normal Task

  1. Select the Save button to add the task.

7. Configure a Decision Task

  1. Once you select Decision Task type from the menu, you will be presented with four tabs for customization:
    • Task Information
    • Actions
    • Validation
    • Instructions
       

Task Information Tab

  1. Configure the following fields to define the task:
    • Activity Name: Enter a clear and descriptive name for the task (for example, Artwork Approval).
    • All or Anyone: Specify whether all assigned users must complete the task or if any one of the assigned users can complete it.
    • User: Assign the task to specific users, teams, form fields, or users from previous tasks. For more details, refer to the "Task Assignment Options" section.
    • Duration (Days): Define the number of days allocated to complete the task.
    • E-Signature (Optional): Enable this option to require users to reconfirm their identity by entering their password before completing the task.
    • Allow Participants for: Define which tabs can be accessed and modified by task participants during the task runtime. These permissions apply only while the task is active and do not extend before or after task completion.
      • Edit Project Info: Allows participants to add or modify project details in the Request Info tab.
      • Edit Components: Allows participants to add or modify component details in the Components tab.
      • Edit Files: Allows participants to upload or modify files in the Files tab.
      • Edit Stakeholder: Allows participants to modify task participants in the Task tab.

 

Action Tab

Use this tab to configure the labels and outcomes of the action button(s) for the task. Typically, a decision task includes two default actions such as Approve and Reject. You can also add up to two additional custom actions if required.

  1. Action 1 Name: Define the label for the first decision button (for example, Approve).
  2. Action 1 Status: Specify the outcome recorded when this action is selected (for example, Approved). This status is captured in the audit log.
  3. Goes to: Select the next step in the workflow when Action 1 is chosen. You can route the workflow to any task, either before or after the current task.
  4. Action 2 Name: Define the label for the second decision button (for example, Reject).
  5. Action 2 Status: Define the status that should be recorded when Action 2 is selected (e.g., "Rejected"). This will also be captured in the audit log.
  6. Goes to: Select the next workflow step when Action 2 is chosen. You can route to any task as required.


     
  7. Track Asset Version: Enforces validation to ensure that a new file version is uploaded before submission or resubmission.
    1. For example, in a rejection scenario, if this option is enabled, users must upload an updated file before resubmitting the task. The system will prevent submission if the file is not updated.
    2. Note:
      1. The Required Files configuration must be enabled for this feature to work.
      2. Configure required files in the relevant task based on the scenario:
        • For a Reject flow, configure required files in the previous task and enable Track Asset Version in the current task.
        • For an Approve flow, configure required files in the next task and enable Track Asset Version in the current task.
  8. To add more actions (Optional):
    1. Select Add More Actions to add additional action buttons. These can be configured in the same way as Action 1 and Action 2.
      Note: You can add a maximum of two additional actions. Only the additional actions can be deletedβ€”not the default two actions.


       
  9. Default Action: Select the default action the system should take if the task is skipped. By default, this is set to Action 1. During runtime, the system will automatically proceed based on this setting.
    Note: This option is primarily used for backend processing or automation scenarios.

 

Validation Tab

Use this tab to configure validations that must be satisfied before a task can be completed.

  1. Component Form Validation: Ensures that the task cannot be completed unless at least one component is added in the Components tab.
    Note: This option is not available for Multi-Level Approval Flow (Project and Component). It is applicable only when a single-level approval flow is selected. In Multi-Level Approval Flow, component validation is handled automatically by the system before the project is split into child components. Ensure that the Edit Components option is enabled under the Task Information tab to use this feature.
    1. To enable this validation, select the Component Form Validation checkbox.


       
  2. Fill checklist: 
    Enable or disable checklists for the task.
    1. To activate the checklist feature, select the Fill Checklist checkbox. Once enabled, configure the following options:
      1. Apply Checklist For: Select the associated drop-down menu and select the asset type to which the checklist applies. Checklist items will appear only for the selected asset type.
        Note: Checklists are associated with file types. If the configured file type is not uploaded in the task, the checklist will not appear. To ensure checklist availability, configure the same file type as a Required File for the task.
         
      2. Select Checklist Group: Select the associated drop-down menu and select one or more checklist groups. Only the checklist items from the selected group(s) will be available during the task.
        Note: To configure the checklists group, refer to Create Checklist Group.
    2. Checklist Strict Validation (available only for Decision task): Enable this option to enforce validations based on checklists. This feature prevents the user from approving the task if any checklist item marked as No in runtime.
  3. Refer to step 5. Validation Tab to configure remaining settings.

 

Instructions Tab (Optional)

  1. If necessary, use this tab to provide clear and detailed instructions to guide users in completing the task.

8. Save Decision Task

  1. Select the Save button to add the task.

9. Configure Email Activity

Use this option to send custom emails upon task completion to recipients who are not part of the workflow task. It also allows runtime configuration of email recipients.

Configuring an email activity involves two steps:

  1. Configure the Email Activity within the workflow template.
  2. Configure the email content using a Custom Email Template.
Note: If an email activity is not configured with a custom email template, the activity will still be auto-completed during runtime, but no email will be sent.

Once Email Activity is selected, the following tabs are available for configuration:

  • Task Information
  • Actions
     

Task Information Tab

  • Activity Name: Enter a clear and descriptive name for the email activity.
  • Users: Assign the task to specific users, teams, form fields, or users from previous tasks. For more details, refer to the "Task Assignment Options" section.
    • Custom Mail ID: Specify additional email addresses manually. This allows sending emails to recipients who are not part of the system user list.


 

Actions Tab

  • Goes To: Select the next step in the workflow after the email activity is triggered.

Note: 

  • Email Activity is an auto-complete task. Users are not required to perform any action.
  • Project participants can modify recipients before the email activity is triggered.
  • Once triggered, the system sends the email and automatically moves to the next task.

10. Save Email Activity

  1. Select the Save button to add the email activity.

Note: 

  • After configuring the email activity, proceed with completing the workflow template.
  • To configure the email content, refer to the section on Custom Email Template Configuration.

11. Configure Fork(s)

When you select Add a Fork from the Add a Task menu, an Add a Fork pop-up will appear. Forks allow you to create parallel tasks that run simultaneously, similar to branches splitting from a single point.

  1. Key Features of Forks:
    1. Parallel Branches:
      • The number of branches you add to the fork determines the number of parallel activities.
      • For instance, if you require three parallel activities, you must add three branches, with one task assigned to each branch.
      • Within each branch, you can add multiple tasks. However, tasks inside a branch are executed sequentially.
      • Only the branches execute in parallel. If you need three tasks to start simultaneously, you must create three branches, each with one task.
    2. Add Run-Time Branch Based on Data (Child Templates): 
      • This feature allows you to dynamically split a project into multiple sub-projects based on the components added.
      • This option is available only if you selected Multi-Level Approval Flow (Project and Component) when creating the project template.
      • If enabled, the project will split into multiple sub-projects based on the components, with tasks defined in a selected child template.
      • Otherwise, this option will not appear in the Add a Fork menu.

Add Parallel Tasks

  1. If you prefer to add only parallel tasks:
    1. Enter the number of branches you need in the No. of Branches field.
    2. Click Add Branch to create the specified branches.


       
  2. Configuring Branches:
    1. Each branch allows you to add tasks.
    2. To add a task to a branch, click + plus icon in the Action column associated with the desired branch and select the task type:
      • For Normal Tasks, refer to the Configure a Normal Task.
      • For Decision Tasks, refer to the Configure a Decision Task.
        Note: For tasks added to the branches, the default next task is set to the Join (Fork Join). If you have added additional tasks within a branch, ensure you configure the next task according to your project requirements.


         
  3. You can customize the placeholder names for forks and branches to align with your project requirements.

Configure Fork Join

For every fork added to a template, a Join (Fork Join) is automatically included at the end of the fork. The Join ensures that the workflow progresses to the next step only after all the branches of the fork have been completed. Its behavior depends on how the Join is configured.

By default, the Join is set to move forward to the next task available in the template once all branches are completed. However, you can modify this configuration to meet specific project requirements. 

Steps to Configure Fork Join

  1. Edit the Join
    1. Click the Edit button associated with the Join.
    2. The Task Information tab will appear for customization.


       
  2. Task Information Tab Configuration
    • Action 1: Define the label for the decision button that users click to complete the task (e.g., Approve).
    • Status 1: Specify the status displayed in the audit log after the task is completed (e.g., Artwork Approved).
    • Next Task: Select the next step in the workflow after the fork is completed. By default, the next task in the template is selected.

Default Behavior for Forks

  • If a fork contains only normal task(s), the default configuration of the Join is sufficient.
    • Normal tasks are submit-based, meaning there are no rejections.
    • Once all tasks across all branches are completed, the workflow automatically progresses to the next stage.

Handling Decision Tasks in Forks

If the fork contains decision task(s), you may need to configure the Required Action 2 option to handle scenarios where branches are rejected. The default Join configuration will not work in such cases, as it can only move forward or backward without distinction.

To address this limitation, enable Required Action 2.

Configuring Required Action 2

  1. Enable Required Action 2
    1. Toggle on the Required Action 2 option to access additional configuration properties.
  2. Additional Properties
    • Action 2: Define the label for the decision button that users click for rejection (e.g., Reject from Join).
    • Status 2: Specify the status displayed in the audit log after rejection (e.g., Fork Rejected).
    • Previous Task: Select the workflow step the process should return to in case of rejection. By default, the previous task in the template is selected.
    • Rules for Action 1: Specify conditions for moving forward with Action 1.
      • All decision tasks in the fork will be listed here.
        Note: Only the last decision tasks from each branch within the fork will be listed here.
      • For each decision task, select the desired outcome (e.g., Approve) that must be met for the workflow to move forward.
      • For example, if a fork contains three decision tasks, you want to configure the Join to proceed only if all three are approved. Then select Approve for all three decision tasks.
      • For any other outcomes (e.g., rejection), the system defaults to Action 2.

Save the Join Configuration

  1. Click the Save button to save the join configuration.

Example: Handling Rejections

  • Scenario: A fork contains multiple branches with decision tasks. If one or more branches are rejected, the workflow should return to a previous step instead of moving forward.
    • Use Action 2 to define the rejection flow.
    • Configure rules under Action 1 to ensure the Join only moves forward if all required tasks are approved.
    • By configuring each Join task of the fork appropriately, you can tailor the workflow to meet your project's requirements, ensuring smooth progression for both approvals and rejections.

Add Run-Time Branch Based on Data (Available only with Multi-Level Approval Flow (Project and Component))

  1. If you want your project to split into multiple sub-projects based on the components added, select the checkbox for Add Run-Time Branch Based on Data.
  2. Use the Select Template drop-down menu to choose the desired child template from the list of active workflow templates.
  3. Click Save to apply the child template.


     
  4. Child Template Functionality:
    • The project splits into multiple sub-projects only while the child template is active, based on the components added.
    • Tasks before and after the child template remain part of the main project.
    • The project resumes as the main workflow once the child template's tasks are completed.

12. Add More Task

  1. Repeat steps 4-9 to add more tasks as needed, connect them logically with the workflow template.

13. End Activity

  1. The End activity is automatically added, marking the workflow completion.

14. Configure Additional Details

  1. To configure the additional details, click the settings icon next to the Add a Task button:
    • Template Description: Add a helpful description for your template.
    • Project Number Prefix: Assign unique prefixes based on the template used.
    • File Publish Status: Set the default status for files completed with this workflow (e.g., Approved).

04: Build Your Workflow (Copy and Create Workflow Template Method)

  1. Select an Existing Template:
    1. Choose Copy and Create Workflow Template.
    2. Click Select Workflow Template and choose the template you'd like to modify.


       
  2. Customize the Workflow:
    1. Enter a descriptive name for the new template (e.g., Artwork Approval v2).
    2. Modify tasks as needed:
      • Delete tasks: Click the delete icon associated with the task and confirm deletion.
      • Add tasks: Follow the same steps as in Step 03.4. for adding Normal, Decision or Fork tasks.
  3. Refine Settings (Optional):
    1. Click the Settings icon to configure additional details:
      • Template Description: Provide a helpful overview of the template's purpose.
      • Project Number Prefix: Assign unique prefixes for organization.
      • File Publish Status: Set the default status for completed files (e.g., Approved).

05. Proceed to Publish Template

  1. Once your workflow is configured, click Next at the bottom right to move on to publishing your project template. If you still need to edit the form, click Back and adjust it as needed before publishing.

Step 4: Publish Template