Workflow

Table of contents:

About

While a complex concept in general eZ publish workflow event system is very basic in nature.

Notion of workflow predefined status code returns

A Workflow event is executed based on settings which bind a workflow event class to a module trigger.

These are available in eZ publish by default

Name	ID	Description
EZ_WORKFLOW_TYPE_STATUS_NONE
EZ_WORKFLOW_TYPE_STATUS_ACCEPTED		Accepted event
EZ_WORKFLOW_TYPE_STATUS_REJECTED		Rejected event
EZ_WORKFLOW_TYPE_STATUS_DEFERRED_TO_CRON		Event deferred to cron job
EZ_WORKFLOW_TYPE_STATUS_DEFERRED_TO_CRON_REPEAT		Event deferred to cron job, event will be rerun
EZ_WORKFLOW_TYPE_STATUS_RUN_SUB_EVENT		Event runs a sub event
EZ_WORKFLOW_TYPE_STATUS_WORKFLOW_CANCELLED		Canceled whole workflow
EZ_WORKFLOW_TYPE_STATUS_FETCH_TEMPLATE
EZ_WORKFLOW_TYPE_STATUS_FETCH_TEMPLATE_REPEAT
EZ_WORKFLOW_TYPE_STATUS_REDIRECT
EZ_WORKFLOW_TYPE_STATUS_WORKFLOW_DONE
EZ_WORKFLOW_TYPE_STATUS_REDIRECT_REPEAT
EZ_WORKFLOW_TYPE_STATUS_WORKFLOW_RESET		Workflow was reset for reuse
EZ_WORKFLOW_STATUS_DONE

Workflow events implement their custom logic and use the above return codes for most basic workflow events.

There are even more workflow event systems which provide their own unique and often advanced functionality. For a example ...

Describing each of the advanced workflow components generic functionality offered and how to use it as offered.

Shop
- Shop / Add to basket
- Shop / Update basket
- Shop / Checkout
- Shop / Confirm order

Shop : Payment Gateway
- Shop / Payment Information Entry
- Shop / Payment Authorization