Mysql schema

This is the reference schema for MySQL 5.

DROP TABLE IF EXISTS workflow;
CREATE TABLE workflow (
  workflow_id                INTEGER      UNSIGNED NOT NULL AUTO_INCREMENT,
  workflow_name              VARCHAR(32)           NOT NULL,
  workflow_version           INTEGER      UNSIGNED NOT NULL DEFAULT 1,
  workflow_created           INTEGER               NOT NULL,

  PRIMARY KEY              (workflow_id),
  UNIQUE  KEY name_version (workflow_name, workflow_version)
) ENGINE=InnoDB;

DROP TABLE IF EXISTS node;
CREATE TABLE node (
  workflow_id        INTEGER      UNSIGNED NOT NULL REFERENCES workflow.workflow_id,
  node_id            INTEGER      UNSIGNED NOT NULL AUTO_INCREMENT,
  node_class         VARCHAR(255)          NOT NULL,
  node_configuration TEXT                  NOT NULL,

  PRIMARY KEY             (node_id),
          KEY workflow_id (workflow_id)
) ENGINE=InnoDB;

DROP TABLE IF EXISTS node_connection;
CREATE TABLE node_connection (
  incoming_node_id INTEGER UNSIGNED NOT NULL,
  outgoing_node_id INTEGER UNSIGNED NOT NULL,

  KEY incoming_node_id (incoming_node_id)
) ENGINE=InnoDB;

DROP TABLE IF EXISTS variable_handler;
CREATE TABLE variable_handler (
  workflow_id   INTEGER      UNSIGNED NOT NULL REFERENCES workflow.workflow_id,
  variable      VARCHAR(255)          NOT NULL,
  class         VARCHAR(255)          NOT NULL,

  PRIMARY KEY (workflow_id, class)
) ENGINE=InnoDB;

DROP TABLE IF EXISTS execution;
CREATE TABLE execution (
  workflow_id              INTEGER UNSIGNED NOT NULL REFERENCES workflow.workflow_id,
  execution_id             INTEGER UNSIGNED NOT NULL AUTO_INCREMENT,
  execution_parent         INTEGER UNSIGNED NOT NULL REFERENCES execution.execution_id,
  execution_started        INTEGER          NOT NULL,
  execution_variables      TEXT             NOT NULL,
  execution_waiting_for    TEXT             NOT NULL,
  execution_threads        TEXT             NOT NULL,
  execution_next_thread_id INTEGER UNSIGNED NOT NULL,

  PRIMARY KEY                  (execution_id, workflow_id),
          KEY execution_parent (execution_parent)
) ENGINE=InnoDB;

DROP TABLE IF EXISTS execution_state;
CREATE TABLE execution_state (
  execution_id          INTEGER UNSIGNED NOT NULL REFERENCES execution.execution_id,
  node_id               INTEGER UNSIGNED NOT NULL REFERENCES node.node_id,
  node_state            TEXT             NOT NULL,
  node_activated_from   TEXT             NOT NULL,
  node_thread_id        INTEGER UNSIGNED NOT NULL,

  PRIMARY KEY (execution_id, node_id)
) ENGINE=InnoDB;

Database independent schema

To load the .dba definition into your database you must have the DatabaseSchema component installed. Save the file to your harddrive and use the following code to load it:

1. <?php
2. $db = ezcDbInstance::get(); // replace if you get your database instance differently
4. $schema = ezcDbSchema::createFromFile( 'array', 'workflow.dba' );
5. $schema->writeToDb( $db );
6. ?>

You may need to extend 'workflow.dba' to contain the proper path to the file.

Storing a workflow to database

This example shows how to store a workflow to database. The example assumes that the workflow is available in the $workflow variable.

1. <?php
2. // Set up database connection.
3. $db = ezcDbFactory::create( 'mysql://test@localhost/test' );
5. // Set up workflow definition storage (database).
6. $definition = new ezcWorkflowDatabaseDefinitionStorage( $db );
8. // Save workflow definition to database.
9. $definition->save( $workflow );
10. ?>

Loading a workflow from the database

This example loads the workflow named 'test' into the variable $workflow.

1. <?php
2. // Set up database connection.
3. $db = ezcDbFactory::create( 'mysql://test@localhost/test' );
5. // Set up workflow definition storage (database).
6. $definition = new ezcWorkflowDatabaseDefinitionStorage( $db );
8. // Load latest version of workflow named "Test".
9. $workflow = $definition->loadByName( 'Test' );
10. ?>

Executing a workflow

Executing a workflow is done by calling the method start on the execution object. This example shows how to execute the workflow test that is stored in the database. The id that is returned by the execute method identifies this execution thread and can be used later if the workflow must be resumed.

Executing a workflow using the ezcWorkflowDatabaseExecution executer requires the definition of the workflow (and all of its sub-workflows) to be stored in the database.

1. <?php
2. // Set up database connection.
3. $db = ezcDbFactory::create( 'mysql://test@localhost/test' );
5. // Set up workflow definition storage (database).
6. $definition = new ezcWorkflowDatabaseDefinitionStorage( $db );
8. // Load latest version of workflow named "Test".
9. $workflow = $definition->loadByName( 'Test' );
11. // Set up database-based workflow executer.
12. $execution = new ezcWorkflowDatabaseExecution( $db );
14. // Pass workflow object to workflow executer.
15. $execution->workflow = $workflow;
17. // Start workflow execution.
18. $id = $execution->start();
19. ?>

Resuming a workflow execution

If a workflow execution is suspended and needs to be resumed the method resume should be used. This example shows how to resume a suspended workflow and provide the input data 'choice'. The id is the one provided by the original call to execute.

1. <?php
2. // Set up database connection.
3. $db = ezcDbFactory::create( 'mysql://test@localhost/test' );
5. // Set up database-based workflow executer.
6. $execution = new ezcWorkflowDatabaseExecution( $db, $id );
8. // Resume workflow execution.
9. $execution->resume(
10. array( 'choice' => true )
11. );
12. ?>

Cancelling a workflow execution

If a workflow execution is suspended it can be cancelled by calling the cancel() method on the executer object.

1. <?php
2. // Set up database connection.
3. $db = ezcDbFactory::create( 'mysql://test@localhost/test' );
5. // Set up database-based workflow executer.
6. $execution = new ezcWorkflowDatabaseExecution( $db, $id );
8. // Cancel workflow execution.
9. $execution->cancel();
10. ?>

This method is also automatically called when the workflow execution reaches a ezcWorkflowNodeCancel node.

When the execution of a workflow is cancelled all nodes that are currently activated will be deactivated and the optional sequence of final activities that starts in $workflow->finallyNode is activated.