Workflows
Class diagram
TODO — Image not available in archive
Title: Workflows Architecture Diagram
File: /doc/design/uml/workflows.png
What this image shows:
Architectural diagram illustrating the Exponential CMS workflow system. Shows how workflow events are defined, how they attach to operations (e.g., content publish, content remove, user register), and how the workflow engine processes events through statuses: FETCH, RUN, DELAY, DONE.
Replacement instructions:
Screenshot or redraw from the Exponential 3.1 admin interface: Admin > Setup > Workflows. Save as /doc/design/uml/workflows.png
See /sdk/missing.html for the full list of missing images.
State diagram
TODO — Image not available in archive
Title: Workflow State Machine Diagram
File: /doc/design/uml/workflows_state.png
What this image shows:
State machine / sequence diagram showing the lifecycle of a workflow event: from initial trigger through FETCH (data collection), RUN (execution), optional DELAY (waiting for asynchronous events), and final DONE state. Illustrates the event processing loop and how delayed events are re-queued.
Replacement instructions:
Redraw as a state diagram based on the workflow documentation. Save as /doc/design/uml/workflows_state.png
See /sdk/missing.html for the full list of missing images.
Database diagram
TODO — Image not available in archive
Title: Image: workflows_db.png
File: /doc/images/workflows_db.png
What this image shows:
Image from original ez.no documentation. Context: c="/doc/design/uml/workflows.png"/>
State diagram [image markup removed]
Database diagram [image markup removed]
Workf
Replacement instructions:
Locate original source and save as /doc/images/workflows_db.png
See /sdk/missing.html for the full list of missing images.
Workflows are triggered by the runTrigger function.
The code may look like this: (like in 'content/edit.php')
if ( $Module->isCurrentAction( 'publish' ) )
{
$workflowParameters = array( 'contentobject' => $object,
'session' => $currentSession,
'user' => $currentUser
);
if ( eZTrigger::runTrigger( 'content', 'publish', 'before' , $workflowParameters) == 'done' )
{
$object->publish();
eZTrigger::runTrigger( 'content', 'publish', 'after', $workflowParameters);
}
}
Here is how the runTrigger function should work:
- Find out if there is a workflow connected to this function
- Find out if there is already started a workflow process for the same event.
- If so start the next event
- If not create new workflow process and start it
If to look to the publish process. Multiplesor workflow looks to parameters and decide what workflow to run next if
need it. And shows user a page saying for instance that the object is sent for approval.
Example of Publish workflow
TODO — Image not available in archive
Title: Content Publish Workflow Screenshot (Admin UI)
File: /doc/images/publish.png
What this image shows:
Screenshot of the Exponential admin interface showing the content publishing workflow step, where a content object is awaiting approval or being published through a configured publish workflow event.
Replacement instructions:
Configure a publish workflow in Exponential 3.1, trigger it, screenshot the admin approval/publish step. Save as /doc/images/publish.png
See /sdk/missing.html for the full list of missing images.
Example of Checkout workflow
TODO — Image not available in archive
Title: E-Commerce Checkout Process Screenshot
File: /doc/images/checkout.png
What this image shows:
Screenshot of the Exponential CMS e-commerce checkout workflow, showing the multi-step checkout process including cart confirmation, address entry, payment method selection, and order summary screens from the shop module.
Replacement instructions:
Install Exponential 3.1 with the shop module, perform a checkout, screenshot the checkout flow. Save as /doc/images/checkout.png
See /sdk/missing.html for the full list of missing images.
| 
