This article provides a comprehensive guide on using the Get KSF Configuration activity in Workflow Builder, which allows users to dynamically retrieve color profiles for apparel printing machines from their Machine Park. This modern approach simplifies configuration management and enhances scalability.
Overview
The Get KSF Configuration activity in the Workflow Builder allows you to dynamically retrieve the correct color profile (KSF file) for your apparel printing machine directly from your Machine Park. This replaces the previous approach of hardcoding color profiles in complex JavaScript, making configurations easier to manage and scale.
Prerequisites
Before using this activity in a workflow, ensure that your color profiles (KSF configurations) are set up in your Machine Park:
Navigate to your Machine Park.
Select your machine (e.g., a Kornit/corvette machine like Atlas).
Click Edit to view or manage configurations.
You can have multiple configurations per machine — for example, one for light garments and one for dark garments.
For each configuration, you can:
Upload the KSF/XML data directly, or
Edit the configuration data inline in XML format.
Tip: Keeping your configurations up to date in the Machine Park means you never need to update individual workflows — changes propagate automatically.
Setting Up the Activity in Workflow Builder
Step 1: Add the Activity
Drop the Get KSF Configuration activity into your workflow at the appropriate step in your apparel printing flow.
Step 2: Set the Product UID (Required)
The Product UID field tells the machine which product the configuration should apply to.
This value should be sourced dynamically from workflow context (e.g., a context variable like
productUID).Example:
de_gcsb_apparel_with...(a UID representing a specific apparel model).
Search for the product UID in your context variables using the search by UID option to find the correct value.
Step 3: Select the Machine (Required)
Use the Machine dropdown to select the machine this configuration applies to.
Example: Select Atlas for a Kornit Atlas machine.
This ensures the correct KSF file is pulled from the Machine Park for that specific device.
Step 4: Add Template Variables (Optional)
You can pass additional key-value pairs to be included in the output XML:
Template Variable | Value |
|
|
|
|
Click + Add row to add as many variables as needed.
These values will be injected into the KSF XML output as additional parameters.
This feature is optional but is commonly requested by partners who need to pass custom settings through the workflow.
How It Works
When the workflow runs, the Get KSF Configuration activity:
Uses the Product UID to identify the correct product.
Looks up the matching KSF configuration in the Machine Park for the selected machine.
Outputs an XML file containing the color profile and any additional template variables you provided.
The resulting XML (e.g., a table AtlasZipperHoodie with its settings) is then available for downstream activities in the workflow.
Benefits
Centralized management — Update color profiles in one place (Machine Park) instead of editing multiple workflows.
Scalable — Supports multiple configurations per machine (e.g., light vs. dark garments).
Flexible — Pass custom key-value parameters at the workflow level when needed.
No JavaScript required — Eliminates the need for complex, hard-to-maintain scripts.