WorkFlow Execution Management

Published workflows can be triggered to generate active Execution Instances. Every execution instance runs independently, empowering you to track the completion status of individual nodes and engage in control operations—such as pause, resume, or termination.

Start Execution

1. Navigate to the Start WorkFlow Execution module.
2. In the left-side start form, specify the following details:
   • Release Version (Required): Select the workflow publication snapshot to instantiate.
   • Owner/Initiator (Optional): Assign the responsible officer for this execution instance.
   • Carbon Copy (CC) List (Optional): Provide personnel to be notified about flow milestones.
3. Click Start WorkFlow. The system will consequently:
   • Forge a new execution instance.
   • Automatically finalize the "Start Event" node.
   • Advance the business process to its first "Activity" node.

The right-side panel shows recent execution instances. Operators can quickly reuse a recent instance's release and owner settings as a template for the next launch.

Tip

Upon a successful launch, you will immediately see the newly instantiated instance recorded in your active list.

Handle Process Activities

As the execution converges on an activity node, the designated operator must address the duties within the Handle WorkFlow Execution module:

• User Task: Operators are demanded to open the embedded form views to finish data submission/approval processes manually.
• Service Task: The backend service autonomously conducts programmed actions.

Upon fulfilling the requirements, the system securely escalates the process toward the subsequent node mapping.

Gateway Logic

When the process workflow reaches a Gateway node:

• Exclusive Gateway: Picks exactly one outbound route hinging off the provided Branch Key logic. Only the branch matching the evaluation token will become active.
• Parallel Gateway: Stimulates all outgoing branches simultaneously, splitting into parallel execution streams.

Branch Key and Conditional Routing

• For exclusive gateways the runtime uses a branch_key value carried by the incoming token to decide which outbound path to take.
• Designers can set a Branch Key string on each connection line from the canvas Properties Panel. This value is persisted with the model and used during execution to match routing conditions.

Life-cycle Control Interventions

Select exactly one running execution instance in the management list. The page provides an icon action bar for the following control operations:

Button	Icon	Functionality	Implication
Pause	⏸	Pause	Temporarily halts progression. All active nodes retain their state but suspend further advancements.
Resume	▶	Resume	Thaws out a paused flow back into a running state.
Terminate	✕	Terminate	Permanently aborts the flow. Induces an irrecoverable terminus.
Complete	✓	Advance Hand-off	Manually brands the execution instance as finished.

Note

The control actions require single selection. If multiple rows are selected, the page will ask you to keep only one execution instance selected before continuing.

Attention

The Terminate intervention is uncompromising and irreversible. Once terminated, that discrete execution instance halts permanently and cannot be re-activated.

Execution State Lexicon

Status	Notation
Ongoing	The flow is running healthily, possessing active nodes awaiting resolution.
Completed	Flow achieved an End Event, or was comprehensively completed manually.
Paused	Manually halted, awaiting resumption commands.
Terminated	Aborted either through deliberate administration or system fatal error.

Transitional Mechanics

Ongoing → Completed    (End Event touched or manually completed)
Ongoing → Paused       (Manual suspension)
Ongoing → Terminated   (Manual termination)
Paused  → Ongoing      (Manual resumption)
Paused  → Terminated   (Termination while in deep suspension)

Note

Completed and Terminated act as absolute end-states (sinks). Execution instances bearing these statuses cannot undergo additional state transformations.