This article provides a comprehensive guide on how to set up machine configuration profiles, such as KSF settings for Kornit printers or XML configurations for Brother GTX, within the Machine Park. It explains the process of assigning these profiles to specific customer product variants using a priority-based rule system, ensuring that production jobs are sent to the correct machine with the appropriate settings automatically.
Overview
Machine configuration profiles enable you to store printer-specific settings (KSF files, XML configs, or other formats) for each machine in your Machine Park. These profiles can then be assigned to customer product variants through a rule-based matching system found in the Machine Configuration tab of a customer product.
When an order is placed, the workflow identifies the correct machine and retrieves the corresponding configuration profile based on variant attributes such as color, size, or product name, automatically populating the configuration file with the correct values before sending it to the machine's hot folder.
End-to-End Setup Flow
The complete setup consists of three stages:
Stage | Where | What You Do |
1 | Machine Park → Edit Machine → Configuration tab | Upload or paste machine config profiles (KSF/XML files) against each machine. |
2 | Customer Products → Machine Configuration tab | Create rules that assign configs to variants based on product-level, group, or exact-match conditions. |
3 | Workflow Builder → Get Configuration activity | The workflow retrieves the matched config and passes template variables into the XML/KSF file at execution time. |
Stage 1: Add Configuration Profiles in Machine Park
Configuration profiles are stored at the machine level, with each profile containing the printer-specific settings file (e.g., a KSF file for Kornit Atlas or an XML file for Brother GTX).
Steps
Navigate to Machine Park and select your machine (e.g., Kornit Atlas).
Open the Edit Machine page and go to the Configuration tab.
Click Add New Config.
Fill in the config details:
Field | Description |
Name | A descriptive name for the profile (e.g., "Atlas Zipper Hoodie Dark" or "GTX Light Config"). |
Description | Optional description to help identify the profile's purpose. |
Type | The file format of the config. Currently, XML is supported; JSON and other formats will be added in the future. |
Config Content | Paste the XML/KSF content directly, or upload an existing file from your machine. |
Save the config. Repeat for each configuration profile your machine requires.
📝 Machine configs are generic settings stored at the machine level — they are not limited to KSF files. You can store any machine-specific configuration data here.
Stage 2: Assign Configs to Customer Product Variants
After creating configuration profiles, you can assign them to customer product variants using rules. These rules determine which config is applied based on variant attributes like color, size, or the base product itself.
Navigate to the Machine Configuration Tab
Go to Customer Products and open the product you want to configure.
Go to the Machine Configuration tab.
Select the machine you want to configure (e.g., Kornit Atlas). Config profiles are machine-specific, so you must select the machine first.
Understanding Rule Types
Rules operate on a priority-based system. When an order is received, the system evaluates all rules from highest priority to lowest and applies the first matching rule. There are three rule types:
Rule Type | Matching Behavior | When to Use |
Product Level | Matches all variants under the customer product. Condition is set to the base attribute only. | You want the same config applied to every variant of this product. |
Group | Matches variants that share a specific attribute value (e.g., all variants where Color = Navy). | You want to apply a config to a subset of variants based on one or more shared attributes. |
Exact Match (Variant) | Matches one specific variant by requiring values for all variant options. | You need a unique config for a single specific variant (e.g., Navy / XL / Cotton). |
Creating Rules
Example 1: Product-Level Rule (Apply to All Variants)
Click Add Rule.
Select the configuration profile (e.g., "Atlas Zipper Hoodie Dark").
Set rule type to Product Level. The condition will automatically include only the base attribute.
Click Save Rule. The rule appears in the list with Priority 1.
Example 2: Group Rule (Apply to a Subset of Variants)
Click Add Rule.
Select the configuration profile (e.g., "Atlas Zipper Hoodie Light").
Set rule type to Group.
Select a variant option (e.g., Color) and one or more values (e.g., Navy). You can select multiple values to avoid creating duplicate rules.
Click Save Rule. The rule is created with a higher priority than the existing product-level rule.
ℹ️ You can select multiple values for the same variant option in a single rule. For example, if both Navy and Black need the same config, add both values to one rule instead of creating two separate rules.
Example 3: Exact Match Rule (Apply to One Specific Variant)
Follow the same steps as above, but select Exact Match (Variant) as the rule type. You will need to provide values for all variant options (e.g., Color = Navy, Size = XL, Fabric = Cotton). Only this exact combination will match the rule.
Managing Rules
Edit rules: Click on an existing rule to update its config assignment, conditions, or values.
Remove rules: Delete any rule that is no longer needed.
Priority ordering: Rules with higher priority win when multiple rules could match the same variant. New rules are automatically assigned the highest priority.
Stage 3: Using Configs in the Workflow
Once machine configs are assigned to customer product variants, the Workflow Builder retrieves and applies them during order execution.
How It Works
When an order is placed, the workflow resolves the correct product based on the order request (customer product name + variant options).
The machine is selected in the workflow (e.g., Kornit Atlas).
The Get Configuration activity retrieves the matching config profile based on the variant's rule assignment.
Template Variables
Configuration files (XML/KSF) often contain dynamic variables — placeholders that are replaced with actual values at execution time. For example, a KSF file might include variables for platen size, print resolution, or garment color that change per order.
In the Get Configuration activity, you specify these as key-value pairs:
Variable Name | Description | Example Value |
platen_size | The platen size for the garment | 16x18 |
print_resolution | DPI resolution for the print | 1200 |
garment_color_type | Whether the garment is dark or light | dark |
When the activity executes, these values replace the corresponding placeholders in the XML/KSF file, producing a complete machine-ready configuration that is then sent to the machine's hot folder.
🔧 You can add multiple template variables per configuration. Each variable maps to a placeholder in your XML/KSF file and is dynamically substituted during workflow execution.
How Priority Matching Works
When an order arrives, the system evaluates rules in priority order (highest number first). The first rule whose conditions match the incoming variant is selected.
Example: Suppose you have three rules for the same machine:
Priority | Rule Type | Condition | Config |
3 | Exact Match | Color = Navy, Size = XL | Navy XL Special Config |
2 | Group | Color = Navy | Atlas Light Config |
1 | Product Level | All variants | Atlas Dark Config |
An order for Navy / XL matches Rule 3 (exact match), so "Navy XL Special Config" is used. An order for Navy / M matches Rule 2 (group), so "Atlas Light Config" is used. An order for Black / L falls through to Rule 1 (product-level), so "Atlas Dark Config" is used.
FAQ
Can I use this for non-apparel products?
Currently, this feature is available for apparel customer products using the new apparel product model. Support for additional product types may be added in the future.
What file formats are supported for configs?
XML is currently the supported format. JSON and other formats are planned for future releases.
Can I assign configs from multiple machines to the same customer product?
Yes. On the Machine Configuration tab, select a different machine to manage its rules independently. Each machine has its own set of rules and profiles.
What happens if no rule matches a variant?
If no rule matches, the workflow will not have a machine config for that variant. Ensure you have at least a product-level rule as a fallback to cover all variants.
Can I assign the same config to multiple variant option values?
Yes. When creating a Group rule, you can select multiple values for a variant option (e.g., Color = Navy and Black) in a single rule. This avoids creating duplicate rules for the same configuration.