Visuel à insérer ici
Powerful
Automation Made
Simple
eZ Conference 2017
London
Gaetano Giunta
House rules
A. No slides Few slides
B. Live Demo
C. Please do interact at any time
01
Once upon a time…
02
Remember the Good Old Times ?
eZ Publish 4 - circa 2007
Remember the Good Old Times ?
eZ Publish 4 - as seen by contemporary developers
eZ Publish did have a workflow mechanism
Good
• It was there!
• Good for Content Approval
• Good for Delayed Publication
• Extensible
Bad
• Slow to set up
• Hard to debug
• Not good for CI
• Little functionality by default
eZ Publish did have a workflow mechanism
Good Bad
Can we do better ?
A Workflow Engine for the Space Age
Question Time
Demo Time
02
The fine print
03
What it can do
• Wait until date
• Manipulation of Content / Location: ALL of it
• Send mail
• Make http calls
• Execute shell commands
Easy to Use
• Multiple command line tools
• Information in the debug log
• “References” can be dumped to a file for
inspection
Easy to Extend
• To add custom workflow steps all you need is
a tagged service
• Symfony Events are fired for every workflow
step - you can listen to them via tagged
services
Needs a little maintenance
• One cronjob to pick up suspended workflows
• One cronjob to cleanup executed workflows
Known limitations
• Not based on a State Machine
• No GUI interaction
• eZ5 Signals always trigger After the fact
Future Evolutions
• Execute workflows asynchronously
• Branch from one workflow to the other
• Simplify syntax for common cases
• …any suggestion is welcome
THANK YOU
github.com/kaliop-uk
@gggeek
please retweet :-)

Powerful Automation Made Simple

  • 1.
    Visuel à insérerici Powerful Automation Made Simple eZ Conference 2017 London Gaetano Giunta
  • 2.
    House rules A. Noslides Few slides B. Live Demo C. Please do interact at any time 01
  • 3.
    Once upon atime… 02
  • 4.
    Remember the GoodOld Times ? eZ Publish 4 - circa 2007
  • 5.
    Remember the GoodOld Times ? eZ Publish 4 - as seen by contemporary developers
  • 6.
    eZ Publish didhave a workflow mechanism Good • It was there! • Good for Content Approval • Good for Delayed Publication • Extensible Bad • Slow to set up • Hard to debug • Not good for CI • Little functionality by default
  • 7.
    eZ Publish didhave a workflow mechanism Good Bad Can we do better ?
  • 8.
    A Workflow Enginefor the Space Age
  • 9.
  • 10.
  • 11.
  • 12.
    What it cando • Wait until date • Manipulation of Content / Location: ALL of it • Send mail • Make http calls • Execute shell commands
  • 13.
    Easy to Use •Multiple command line tools • Information in the debug log • “References” can be dumped to a file for inspection
  • 14.
    Easy to Extend •To add custom workflow steps all you need is a tagged service • Symfony Events are fired for every workflow step - you can listen to them via tagged services
  • 15.
    Needs a littlemaintenance • One cronjob to pick up suspended workflows • One cronjob to cleanup executed workflows
  • 16.
    Known limitations • Notbased on a State Machine • No GUI interaction • eZ5 Signals always trigger After the fact
  • 17.
    Future Evolutions • Executeworkflows asynchronously • Branch from one workflow to the other • Simplify syntax for common cases • …any suggestion is welcome
  • 18.