Creating a simple custom workflow event

Thursday 09 December 2010 8:01:18 am - 6 replies

Introduction

This tutorial will guide you through the development of a simple eZ Publish workflow event. At the end of the tutorial, you should be able to create your own workflow event, configure a workflow that would execute the event and configure workflow triggers in the admin interface.

Note : the PDF version of this tutorial, as well as the downloadable extension are here.

6 replies

Author	Message
Robin Muilwijk	Saturday 11 December 2010 12:27:38 am Hi, Great tutorial! A very good addition to the online docs, I'm sure this will inspire others when setting up their workflows. It also shows the power of eZ Publish, thanks for this contribution! -- Robin Board member, eZ Publish Community Project Board - Member of the share.ez.no team - Key values: Openness and Innovation. LinkedIn: http://nl.linkedin.com/in/robinmuilwijk // Twitter: http://twitter.com/i_robin // Skype: robin.muilwijk
Kristof Coomans	Saturday 11 December 2010 9:34:58 am There seems to be a small typo on Step 8: " It’s not time to see how to retrieve them. " I guess "not" should have been "now". Nice tutorial, posting Twitter updates is a perfect use case for workflows! However, the used process of authorizing eZ Publish to have access to the twitter account looks quite cumbersome to me. I guess it could be made a lot easier by offering a screen for that in the eZ Publish administration interface that starts the full web-based authorization process instead of the out-of-band/PIN code authentication which was not really suitable for this kind of app. A good example of how this is done is the nxc_twitter extension available at http://projects.ez.no/nxc_twitter. independent eZ Publish developer and service provider \| http://blog.coomanskristof.be \| http://ezpedia.org
Romeo Antony	Sunday 12 December 2010 12:29:49 am Huy, Good tutorial. Learned a lot from this like how to integrate 3rd party libraries, creating custom wrokflowevents.
Maxime Thomas	Monday 13 December 2010 4:46:56 am Hi, Excellent article which shows the power of workflows and how thing can be easily done with it. However, I just regret you don't put some examples on how debug thoses workflows, it can be tricky for some people. Max maxime.thomas@wascou.org \| www.wascou.org \| http://twitter.com/wascou Maxime Thomas maxime.thomas@wascou.org \| www.wascou.org \| http://twitter.com/wascou Company Blog : http://www.wascou.org/eng/Company/Blog Technical Blog : http://share.ez.no/blogs/maxime-thomas
Nicolas Pastorino	Wednesday 15 December 2010 4:46:39 am " There seems to be a small typo on Step 8: " It’s not time to see how to retrieve them. " I guess "not" should have been "now". " Thanks, fixed now. " Nice tutorial, posting Twitter updates is a perfect use case for workflows! However, the used process of authorizing eZ Publish to have access to the twitter account looks quite cumbersome to me. I guess it could be made a lot easier by offering a screen for that in the eZ Publish administration interface that starts the full web-based authorization process instead of the out-of-band/PIN code authentication which was not really suitable for this kind of app. A good example of how this is done is the nxc_twitter extension available at http://projects.ez.no/nxc_twitter. " I agree here, although it is not exactly the scope of this already thorough tutorial. It could be a follow-up tutorial, showing how to create custom panels and tabs in the admin interface ? Easy, yet very useful. Cheers Kristof, -- Nicolas Pastorino Director Community - eZ Member of the Community Project Board eZ Publish Community on twitter: http://twitter.com/ezcommunity t : http://twitter.com/jeanvoye G+ : http://plus.tl/jeanvoye
Quoc Huy Nguyen Dinh	Wednesday 15 December 2010 4:50:29 am Thank you all for the feedbacks. Very much appreciate it. @Kristof, I've notified Nicolas to see if the typo can be corrected. Regarding the Twitter API you are correct, this is not the easiest way to handle this and NXC technique is sweet. But this allows one to also discover eZ Script. @maxime, I usually debug my workflows with eZLog::write() which is used here.

You must be logged in to post messages in this topic!

eZ debug

Timing:	Jan 17 2025 21:21:17
Script start
Timing:	Jan 17 2025 21:21:17
Module start 'layout'
Timing:	Jan 17 2025 21:21:17
Module start 'content'
Timing:	Jan 17 2025 21:21:17
Module end 'content'
Timing:	Jan 17 2025 21:21:17
Script end

Main resources:

Total runtime	0.1525 sec
Peak memory usage	4,096.0000 KB
Database Queries	89

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0044	597.7969	152.1406
Module start 'layout'	0.0044	0.0021	749.9375	39.5078
Module start 'content'	0.0065	0.1447	789.4453	1,017.3750
Module end 'content'	0.1512	0.0012	1,806.8203	26.4766
Script end	0.1524		1,833.2969

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0029	1.9038	16	0.0002
Check MTime	0.0013	0.8223	16	0.0001
Mysql Total
Database connection	0.0006	0.3712	1	0.0006
Mysqli_queries	0.0821	53.8398	89	0.0009
Looping result	0.0006	0.4183	87	0.0000
Template Total	0.1284	84.2	2	0.0642
Template load	0.0021	1.3727	2	0.0010
Template processing	0.1263	82.8011	2	0.0631
Template load and register function	0.0002	0.0998	1	0.0002
states
state_id_array	0.0007	0.4878	2	0.0004
state_identifier_array	0.0009	0.5790	3	0.0003
Override
Cache load	0.0018	1.1954	54	0.0000
Sytem overhead
Fetch class attribute name	0.0008	0.5537	13	0.0001
Fetch class attribute can translate value	0.0005	0.3385	6	0.0001
class_abstraction
Instantiating content class attribute	0.0000	0.0084	13	0.0000
XML
Image XML parsing	0.0025	1.6626	6	0.0004
General
dbfile	0.0013	0.8781	50	0.0000
String conversion	0.0000	0.0038	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded
1	node/view/full.tpl	forum_topic/full.tpl	extension/community_design/design/suncana/override/templates/forum_topic/full.tpl
7	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
13	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
2	content/datatype/view/ezxmltags/link.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/link.tpl
1	content/datatype/view/ezxmltags/emphasize.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/emphasize.tpl
1	content/datatype/view/ezxmltags/separator.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltags/separator.tpl
6	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
4	content/datatype/view/ezxmltags/quote.tpl	datatype/ezxmltext/quote.tpl	extension/ezwebin/design/ezwebin/override/templates/datatype/ezxmltext/quote.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 36 Number of unique templates used: 9

Time used to render debug report: 0.0001 secs