Skip to main content

[Workflow Builder - GCW] Configuring a Workflow for Flat Cards

Anastasiia Zbrozhek avatar
Written by Anastasiia Zbrozhek
Updated over a week ago

This guide will help you understand how to configure and test a complete workflow for flat products, from batching items and setting imposition templates to defining production steps like printing and cutting. You’ll also learn how to send imposed files to an SFTP server and publish your workflow so it can be used in production.


Setting Up the Workflow for Flat Products

Begin by editing a workflow under a flat product model. If you haven’t already created one, you’ll need to do that first.

Batching Items

Batching defines how incoming order items are grouped before moving to production.

  • Batch Release Options: You can release a batch by:

    • Time

    • Date

    • Count (e.g. release after one item, which we’ll use in this example)

    • A combination of time and count

  • Advanced Batch Settings:

    • Use quantity from the context to control batching based on item quantity.

    • Define batch criteria using context-based parameters, such as:

      • client_items_id (e.g. for flat cards by client)

      • spine_size (e.g. for photo books)

      • Any other context attribute relevant to your use case

Once set, switch to test mode to generate context data and proceed with configuration.


Configuring Imposition Templates

Next, add the Imposition Templates activity to define how your items are laid out for production.

  • You can select values directly from context or hard code them. Example parameters:

    • Sheet width and height: either hardcoded or from context

    • Substrate: e.g. paper_type

    • Format: e.g. paper_size

    • Dispatch date, size, and count: use context values

    • URL and quantity: select from the available context data

    • Bleed: set from context or default to a fixed value (e.g. 0)

Once parameters are set, save the configuration and test again to ensure the imposition is successful. You’ll then be able to preview the imposed file by following the link generated from this step.


Sending Files to SFTP

After successful imposition, it’s time to send the output to an SFTP location for production.

  • Choose file upload type:

    • Single file or multiple files

  • Select the correct URL: Ensure it's the one from the imposition context field.

  • Define the filename:

    • Leave blank to use the system-generated name (e.g. starts with W00)

    • Customize with unique values like order ID (e.g. flat_product/{id})

You’ll see a preview of the resulting SFTP file path in the right panel. Save parameters and re-run in test mode to validate the setup.


Adding Production Steps

Now, configure the Production steps such as printing and cutting.

Printing Configuration

  • Set to Sheet Fed

  • Example setup:

    • Printer: Indigo 12000

    • Sheet size: 12x18

    • Image area (IA): Set as required for that sheet

Cutting Configuration

  • Use a Guillotine type machine

  • Example setup: 3DMX, set cut index to 2

The activity index controls the execution order:

  • Printing (set to 1)

  • Cutting (set to 2)

Run another test to validate the entire workflow.


Finalizing and Publishing the Workflow

Once all test runs are successful:

  • Save your workflow

  • Click Publish to make it live

  • You’ll see the status change to Live

Important: In the Production Details section under Parts and Attributes, ensure you’ve selected the correct workflow using the workflow config button.


FAQ

Can I hard code all parameters in imposition setup?
Yes, but using context values is recommended for flexibility and automation.

What happens if I don’t assign a custom filename for SFTP uploads?
The system will automatically generate one, typically starting with W00.

What if my workflow doesn’t run successfully in test mode?
Check if all required parameters are filled and ensure context values are properly defined.

Can I reuse this workflow for other product types?
No, workflows are tied to the product model, so you’ll need a separate configuration for other models.


📝 Not what you needed?

Help us improve this article, send us an email to [email protected] — please include the article title.

Did this answer your question?