Uploaded image for project: 'eZ Publish / Platform'
  1. eZ Publish / Platform
  2. EZP-29054

Spike : symfony workflow component integration

    XMLWordPrintable

    Details

    • Sprint:
      [2.4] - Sprint 1
    • Story Points:
      13

      Description

      We want to add support for configurable workflows on backoffice / repository operations, such as content editing. The Symfony Workflow component is our first option.

      The spike aims at seeing how workflows could be integrated so that they can be triggered from the backoffice, and iterated on.
      The workflow "board" UI should be kept in mind as a target.

      Possible outcomes:

      • table in details tab with the current workflow state
      • 2 buttons in action bar (edit mode) to send the content to the previous and next state

      Workflow definition

      The idea is to create a very simple workflow with 2 intermediate steps between the `draft` and `published` (coming from eZ Platform).
      Also in order to simplify, user won't be able to skip steps (forward and backward).
      Example of yml configuration.

      framework:
          workflows:
              blog_publishing:
                  type: 'workflow'
                  supports:
                      - blog_post #ContentType identifier
                  initial_place: draft
                  places:
                      - draft
                      - design
                      - proofread
                      - published
                  transitions:
                      draft_to_design:
                          from: draft
                          to:   design
                      design_to_draft:
                          from: design
                          to:   draft
                      design_to_proofread:
                          from: design
                          to:   proofread
                      proofread_to_design:
                          from:   proofread
                          to: design
                      proofread_to_publish:
                          from: proofread
                          to:   publish
      

      User group assignment

      Define a group of user responsible for every `place` / state: interface or yml?

      Open questions;

      1. Will the workflow be admin SiteAccess aware? e.g. I can have a multisite configuration and the Content Types are shared between the 2 sites. But the workflow for a Content Types is different for each site.
      2. How to define a workflow for create and a different workflow for edit?

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              bertrand.dunogier@ez.no Bertrand Dunogier
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: