Getting Started: Workflows Overview

This article is designed to showcase our workflow capabilities and management of workflows within organizations of all sizes, from simple projects to complex, multi-layered processes.

Overview of Workflows

Our software is designed to accommodate the most complex workflows, allowing users to define, maintain, and modify them directly within the user interface.

User Accessibility: Any user with the appropriate permissions can adjust workflows.
No Developer Needed: Workflow modifications can be done without requiring developer assistance

Workflow Structure in Proceve

Primary & Sub-Workflow Capabilities

Our software allows for the creation of a primary workflow with multiple sub-workflows. This structure allows for:

Multi-level Workflows: Ideal for complex pro with many moving parts.
Unlimited Nesting: Although most users may only need one or two levels, Proceve supports unlimited depth for those who require it.

Stages

Each sub-workflow is composed of stages that can be:

Linear: Progressing from one stage to another in a set order. (Stage A- Stage B- Stage C- Stage D)
Non-linear: Allowing flexible transitions where stages can be revisited or bypassed as necessary. (Stage A- Stage C- Stage D- Stage B)

Stage Transitions and Permissions

Customizable Stage Transitions

Within Proceve, users can customize transitions within a workflow. Transitions between stages can be defined with either:

Connections: Specify which stages are connected.
Actions: Specific actions are triggered when moving from one stage to another.
Permissions: Set restrictions requiring specific roles or entitlements to perform stage transitions. This ensures that only authorized users can advance a workflow if needed

Stage vs. Status

Distinction Between Stages and Statuses

Proceve distinguishes between the stage of an item within a workflow and its status:

Stages: Represent steps within a workflow.
Statuses: Indicate the condition or state of an artifact, independent of its stage.

This separation prevents confusion and allows for more accurate workflow management.

Status Categories

Statuses in Proceve are grouped into four main categories:

Progress: On time, overdue, completed, no estimate, etc.
Activity: Queued, in progress, paused, interrupted, archived, etc.
Dependency: None, blocked, blocking, etc.
Other: Other relevant miscellaneous statuses that may apply.

Progress example: An item in the “To-Do” stage could be “On Time” initially but become “Overdue” if its deadline passes, even though the stage hasn’t changed.

Activity example: Working on a task, but a higher priority task comes along, causing the status to change to Paused or Interrupted, even though the stage hasn’t changed.

Dependency example: If another task is dependent on this workflow, it can become blocked, and the status will reflect that.

Example of Workflow Implementation

Complex Workflow Example

In this section, we’ll explore an example of a complex software workflow within Proceve

Subprocesses:

The workflow comprises four distinct subprocesses:

Requirements: Defines and approves requirements.
Implementation: Focuses on task artifacts to implement the requirements.
Testing: Ensures the implemented tasks meet the required standards.
Operations: Handles deployment and ongoing operations.

Process Structure:

Each subprocess includes its own stages, with branching, looping back, and cross-linkages available for users.

For example, approving a requirement could automatically:

Create a task for its implementation.
Generate a placeholder test to validate the requirement.
Set up a task to write the necessary test.

Cross-linkage:

The workflow allows complex interactions, such as initiating the testing process once the implementation is deployed to the test environment.

Flexibility of Workflows:

While Proceve supports this high level of complexity, it also caters to simpler, linear workflows.

Whether you’re managing a straightforward or intricate process, Proceve accommodates your needs, ensuring scalability from small projects to large enterprises.