Skip to main content

Style Guide V2: Production Triggers

How to configure automated production triggers in Style Guide V2.

Written by Jameson

Production Type Triggers enable you to automate when production types become active based on the completion of other Productions in your Workflow. This powerful feature is essential for creating AI-powered Generative Workflows, while also improving traditional sequential production scenarios.

πŸ—£οΈ Tip: Triggers are the enhanced successor to Derived Workflows. If you're currently using Derived Workflows, consider migrating to Production Type Triggers for enhanced flexibility and visibility.


Feature Overview

Production Type Triggers allow you to configure one production type to automatically activate when another production type reaches a specific Workflow step. This creates dependencies between production types, ensuring work happens in the correct sequence.
​

Use Scenarios

Utilizing triggers has a wide variety of use cases as unique as each studio's needs. However, we have highlighted two example scenarios and their setup details below.

Scenario

Details

AI Content Generation

Shoot assets as Flats, then automatically generate Virtual Model imagery using AI.
​
​Source PT: Flats

Triggered PT: AI On Model

Trigger: Final Selection completes for Flats

Pass Through Assets: Yes, Flats assets used as AI input

Fixed Sequential Shooting

Require Mannequin photography before On-Model photography begins.

Source PT: Mannequin

Triggered PT: On Model

Trigger: Final Selection completes for Mannequin

Pass Through Assets: No, different images needed for each

Setup & Configuration

To get started, head to Production β†’ Style Guides β†’ then, in a new or existing Style Guide, head into the Production Type tab that you would like to be triggered.

Within the Production Type, navigate to the Trigger tab.

Task Initiation

Under Task Initiation, you will be able to select a Trigger Type from a drop-down menu. There will be two available options to select from.

Trigger Type

Behavior

On Product Creation

By default, this is set for all Production Types within a Style Guide. Having this trigger type selected aligns with the typical expected behavior for productions.

When a Product is imported into the system and assigned to the Style Guide, the Production Type will be enabled automatically.

Step of Specific Production Type

The triggered Production Type stays in Backlog until the trigger fires.
​
When this type is selected, further configuration options will become available. ↓

β†ͺ Source Production Type

Choose which production type should act as the trigger.

  • Dropdown shows all non-text production types from your Style Guide

πŸ“ Note: Only one source production type can be selected per trigger.

β†ͺ Step

Choose which workflow step(s) in the source production type will fire the trigger:

  • Steps are dynamically populated from the source production type's workflow

  • Multiple selections supported

⚠️ Important: A configured trigger always fires as long as the source work unit is active and eventually completes. Scenarios where the trigger should be conditional are better served using Conditional Rules.

Multi-Step Selection

When multiple Workflow steps are selected in the β†ͺ Step section, the trigger is fired based on a set logic.

  1. Multiple steps selected: Trigger fires when the first selected step completes; other steps will have no effect on the triggered production.
    ​

  2. All steps bypassed/skipped: Trigger still fires when the source work unit is fully complete (Asset Delivery = Done).

Pass Through Assets

Once Task Initiation has been configured, you will see an additional Assets section with a pass-through toggle. This toggle controls whether to pass assets from the source production type into the triggered one.

πŸ—£οΈ Tip: This is particularly useful in conjunction with Generative Workflows, where the generative step gets the photography assets without a redundant manual Capture step and passes them through to be used in Cloud Automation.

Toggle

Behavior

Pass Through Assets: Off

By default, the pass-through is disabled.

The triggered production type still fires, but the Capture step remains manual.

Pass Through Assets: On

Associated assets are cloned into the triggered production type, and the Capture step is auto-completed.

β†ͺ Positions

Select which photography positions from the source production to pass through using a checkbox matrix.

Pass Through Notes

βš™οΈ Pass Through + Final Selection: Even when assets are passed through, and Capture is auto-completed, Final Selection is not auto-completed. Final Selection will still be required in the triggered production's Workflow.

βš™οΈ Missing Source Image: If a selected position has no image in the source production, the system skips it and proceeds with whatever assets are available. It does not block the trigger.

Trigger Behavior

Production Visibility

Triggered production types are visible in the Products and Production tabs from the moment the product is created. They sit in a new Backlog status until the trigger fires, then move to To-Do once triggered.

While a production type is in Backlog, it cannot be worked on in Capture. The Capture interface (Kelvin, VPI, etc.) will show an error when attempting to start.

Capture only becomes available once the trigger fires, or once a user manually triggers the production with Start Without Trigger.

Start Without Trigger

The Start Without Trigger action allows you to manually activate a triggered production without waiting for the source production to complete its trigger step.

Click the 3-dot menu β†’ Select Start Without Trigger β†’ The production will immediately move from Backlog to To-Do.

βš™οΈ Pass Through Handling: If Pass Through Assets is enabled, the system will attempt to clone currently available assets from the source. If no source assets are available yet, the capture step will remain manual for the trigger production.

Source Step Reset

Triggers are one-time events. Once fired, the triggered production proceeds independently. For cases where the source production type's trigger step is reset after the triggered work unit has already been activated, the triggered production will not be affected.

Did this answer your question?