Workflow template branching

Many similar projects might require small variations in workflow. You can configure project templates to use different workflows that are based on user input instead of creating separate templates. Use this feature to simplify your organization's template collection.

For example, a project to organize a tradeshow contains an attribute called "Handout" with different options for handouts in the booth. The options are brochure, booklet, demonstration DVD, and 3D piece. The workflow tasks that are required to create each handout are different, although the rest of the steps for organizing the tradeshow are the same.

In this scenario, all the workflows contain a stage that is called "Create handout." You can use template branching to select the workflow for a print object when the user selects brochure or booklet. You might make both brochure and booklet go to a default workflow for a print handout. Then, you can branch the workflow to customize one workflow template for the demonstration DVD and a third template for the 3D piece.

Workflow template branching occurs only when a project is created.

You can build workflow template branching based on the following types of form and campaign attributes.

  • Single-select
  • Single-select database
  • Yes/No

In this example, you build the template branching based on the single-select database attribute "Handout." The values for this attribute include brochure, booklet, demonstration DVD, and 3D piece.