Project Flow
1. Using Sanplex by Role
1.1. Administrator
1.1.1 Manage Departments
2. Introduction of Sanplex features
2.1. Core Management Framework
2.1.1 Program
2.1.2 Project
2.1.3 Product
2.1.4 Execution
2.1.5 Management Models
2.2. Dashboard
2.2.1 Getting Started with Tutorials
2.2.2 Quick Add
2.2.3 Notification Center
2.2.4 Effort Tracking
2.2.5 Dashboard - Project and Execution
2.2.6 Dashboard - My Work, Contribution, and Recents
2.2.7 Dashboard - Approval
2.2.8 Contacts
2.3. Program
2.3.1 Program List
2.3.2 Program Kanban
2.3.3 Create Program
2.3.4 Create Sub-Programs
2.3.5 Project Charter Management
2.4. Product
2.4.1 Create Product
2.4.2 Manage Modules
2.4.3 Multi-Branch and Multi-Platform Management
2.4.4 Manage Plans
2.4.5 Manage Stories
2.4.6 Story Reviews
2.4.7 Story Status and Phase
2.4.8 Create Releases
2.4.9 Track Progress
2.4.10 Epics and Multi-Level Stories
2.5. Project
2.5.1 Scrum Project
2.5.2. Waterfall Project
2.5.2.1 Manage Project Phases
2.5.2.2 Project Design
2.5.2.3 Project Matrix
2.5.2.4 Project Reports and Earned Value Management
2.5.2.5 Project Baselines
2.5.2.6 Project Change
2.5.3. Kanban Project
2.5.3.1 Set Up Kanban Projects
2.5.3.2 Configure Kanban Boards
2.5.3.3 Use Kanban Boards
2.5.4 Hybrid Agile Project
2.5.5 Hybrid Waterfall Project
2.5.6. Project Settings
2.5.6.1 Project Setup
2.5.6.2 Project Executions
2.5.6.3 Project Requirements
2.5.6.4 Project Builds
2.5.6.5 Project Tests
2.5.6.6 Project Docs
2.5.6.7 Project Releases
2.5.6.8 Project Reports
2.5.6.9 Project Risks
2.5.6.10 Project Issues
2.5.6.11 Project Opportunities
2.5.6.12 Project Deliverables
2.5.6.13 Project Reviews
2.5.6.14 Project Process
2.5.6.15 Deliverables
2.5.6.16 Quality Assurance
2.5.6.17 Project-specific Workflow Management
2.5.7 Project Templates
2.6. Execution
2.6.1 Product Planning and Task Breakdown
2.6.2 Task Assignment and Daily Tracking
2.6.3 Build Creation and Test Requests
2.6.4 Bug Confirmation and Resolution
2.6.5 Execution Kanban Boards
2.7. Testing
2.7.1 Write Test Cases
2.7.2 Execute Test Cases
2.7.3 Bug Submission and Reports
2.7.4 Verify and Close Bugs
2.7.5 Test Case Scenes
2.7.6 Submit a Test Request
2.7.7 Test Report
2.8. Agent
2.8.1 Conversation
2.8.2 Sanplex Agents
2.8.3 General Agents
2.8.4 Skill Management
2.8.5 AI Knowledge Library
2.8.6 Models
2.8.7 ZAI Service Installation
2.8.8 ZAI Service Control Panel
2.8.9 ZAI Configuration
2.9. Kanban
2.9.1 Kanban Spaces
2.9.2 Kanban Regions
2.9.3 Kanban Cards
2.10. Company
2.10.1 View Team Members and Work Information
2.10.2 View Recent Company Activity
2.10.3 View and Edit Company Information
2.11. Feedback
2.11.1 Configure, Create, and Review Feedback
2.11.2 Process Feedback and Send Notifications
2.11.3 Tickets
2.12. Admin Settings
2.12.1. System Settings
2.12.1.1 Mode
2.12.1.2 Backup
2.12.1.3 Trash
2.12.1.4 License
2.12.1.5 Security
2.12.1.6 Cron Job
2.12.1.7 Time Zone
2.12.1.8 Rebuild Index
2.12.1.9 LDAP
2.12.1.10 Table Engine
2.12.2 Feature Options
2.12.3. Users Management
2.12.3.1 Set Departments and Edit Company Profile
2.12.3.2 Manage Users
2.12.3.3 Set Permisions
2.12.4. Feature Configuration
2.12.4.1 Dashboard
2.12.4.2 Product
2.12.4.3 Project
2.12.4.4 Execution
2.12.4.5 Test
2.12.4.6 Kanban
2.12.4.7 Feedback
2.12.4.8 Tickets
2.12.4.9 User
2.12.4.10 Relations (Standard Version)
2.12.4.11 Meaturement
2.12.5 Migrate Jira Data to Sanplex
2.12.6 Jira to Sanplex Migration Mapping
2.12.7 Migrate Confluence Data to Sanplex
2.12.8. Agent Configuration
2.13. Asset Library (Premium)
2.13.1 Asset Library Management (Premium)

Process

2026-09-22 11:14:48
Kelsea Zhang
1
Last edited by Kelsea Zhang on 2026-10-15 14:26:35
Share links
Summary: This guide explains Process Definition in Sanplex, including its use cases, the built-in process categories, how to manage processes and activities, tailoring settings, and how processes and activities are handled after upgrading from an earlier version.

I. Overview

Project process management is an important way for organizations to standardize and optimize project execution. By defining standard organization-level processes and tailoring processes within projects, it enables flexible adaptation and continuous improvement of the project development process.

Flow administrators can define organization-level project processes and activities in the Admin area, according to the company’s requirements for project process standardization.

When different business units or product lines have significantly different processes, they can define separate organization-level processes and activities to meet their own standardization requirements.

For project flows based on the Agile, Waterfall, and IPD models, the system provides three sets of built-in organization-level processes and activities, so that flow administrators can adjust the built-in data instead of configuring everything from scratch.

After processes and activities have been configured with this feature, project managers can tailor the organization-level processes and activities according to the actual situation of a project.

II. Use Cases

In their project R&D activities, organizations usually establish a standardized system of processes, methods, tools, and templates for consistent management, higher efficiency, project quality, and external audits, so that all projects have unified guidance and reference.

  • Promoting best practices and continuous improvement: Organizations want to accumulate and share best practices so that the overall R&D capability of the organization keeps improving.
  • Quality assurance and internal audits: Standardized process definitions provide a clear basis for quality assurance and process audits, ensuring process compliance and project quality.
  • Responding to customers or external audits: When working with customers or undergoing external audits, such as a CMMI maturity assessment, organizations can demonstrate their process capability and management maturity.

III. Operations

1. Access and Switches

  • Go to Admin > Project Flow, open a project flow, and then manage processes under the Process menu.
  • System-level feature switch: under Admin > Feature Options, the Process switch controls the process feature for all project flows.
  • Flow-level feature switch: under Admin > Project Flow > Feature Switch, the Process switch controls the process feature for the current project flow only.

2. Process Category Management

  • The system provides three built-in process categories: Project Management, Engineering Implementation, and Supporting Processes.
  • On the process category maintenance page, you can add, delete, edit, and reorder categories.

Manage process modeles

3. Process Management

1) Viewing processes:

  • Each category includes built-in generic project processes. For example, the Project Management category includes processes such as Project Initiation, Project Planning, Project Monitoring, and Risk Management.
  • You can view the processes under all categories, or only the processes under one category.

Project - All processes

2) Maintaining processes:

You can add, batch add, edit, batch edit, and delete processes, and you can reorder them.

Process Actions

3) Adding a single process or batch creating processes:

Batch create processes

4) Editing a single process or batch editing processes:

Batch edit processes

4. Activity Management

1) Viewing activities:

  • Each process includes the key activities of that process. For example, the Risk Management process includes activities such as Risk Identification, Risk Assessment, and Risk Monitoring.
  • You can view the activities of all processes, or only the activities of one process.

Activities

2) Maintaining activities:

You can add, batch add, edit, batch edit, and delete activities, and you can reorder them.

Actions for activities

3) Adding a single activity or batch creating activities:

Batch create activities

4) Adding a single activity or batch editing activities:

Batch edit activities

5. Tailoring Settings

  • Tailorable: a process or activity can be tailored in an actual project only when it is set as tailorable; otherwise it must be carried out.
  • Tailoring rule: describes the situations in which the item can be tailored out, that is, when it does not apply and will not be carried out.

6. Handling After Upgrading from an Earlier Version

  • The document list is no longer displayed in Process Definition in the Admin area, but the tailoring results of documents in previous projects are still displayed correctly.
  • Admin-area processes and activities that have tailoring results in a project are still displayed as they were before the upgrade.
  • If an Admin-area process or activity has been tailored in a project, the process or activity is still displayed as it was before the upgrade.
  • If an Admin-area process or activity has not been tailored in a project, the new built-in process or activity is displayed after the upgrade.
Write a Comment
Comment will be posted after it is reviewed.