Project-specific Workflow Management

2026-03-29 18:24:39
Sanplex Content
17
Last edited by WANG JING on 2026-03-29 18:24:39
Share links
Summary : This section explains how to enable and configure project-specific workflows so teams can tailor workflow behavior for individual projects without changing global workflow settings.

Feature Overview

Building on global project workflow management, Project-specific Workflow Management allows teams to configure, adjust, and run a dedicated workflow for an individual project.


This feature supports project-level workflow customization, making it easier to align the workflow with the actual needs of a specific project. It improves flexibility, control, and responsiveness during execution. With project-level workflow visibility, stage tracking, and on-the-fly adjustments, teams can manage projects in a more refined and lean way.

Use Cases

  • Project-specific workflow setup: For projects with unique requirements or delivery models, teams can customize the standard workflow for that specific project to better support industry-specific, customer-specific, or delivery-specific needs.

1. Project-specific Workflow

Project-specific workflow management is available under Project > Settings > Project Workflow.

It is disabled by default after a project is created.

Note: Enabling project-specific workflow management is irreversible, so it should be used with care. Kanban projects do not support this feature.

The Project Workflow configured under a project applies only to the current project. It is not visible in the project creation page or in the global workflow configuration area.

图1

2. What You Can Configure in Project Workflow

Different project workflow types include different project-related objects and workflows:

  • Product-based project includes: Project, Release, Execution, Task, and workflows that belong to the project or execution.
  • Project-based project includes: Business Requirement, User Requirement, Development Requirement, Release, Plan, Ticket, Feedback, Test Run, Test Case, Bug, Build, Execution, Project, Task, and workflows that belong to the project or execution.
  • Project without iterations includes: Project, Build, Task, and workflows that belong to the project.
  • Project-based project without iterations includes: Business Requirement, User Requirement, Development Requirement, Release, Ticket, Feedback, Test Run, Test Case, Bug, Build, Project, Task, and workflows that belong to the project.

Important notes

  • In the workflow template, each object workflow supports Design, Enable, and Disable actions.
  • You can open Design only after setting a workflow, such as the Plan workflow, to Custom in the template. Once it is marked as custom, you can modify its fields, actions, labels, and other workflow settings. Changes made in a custom workflow affect only the current template and do not affect the general workflow or other templates. Setting a workflow to Custom is irreversible.
  • Enable and Disable actions in the template apply only to the current template.
  • Built-in workflows in the template cannot be disabled.
  • Only workflow objects that belong to a Product, Project, or Execution are included in the template, and they must be enabled in the template before they can be used.
  • Click Design to edit the workflow.

In Sanplex Premium, Project Workflow also supports additional configuration options such as Feature Switches, Process Definitions, Quality Assurance, Deliverable Types, and Review Workflows. These options are available under Admin > Project Workflow.

图2

Write a Comment
Comment will be posted after it is reviewed.