eZ Publish Knowledge Series: Editorial workflow with Object States

Wednesday 29 July 2009 6:18:50 am - 4 replies

Introduction

Typical workflow-like processes basically boil down to transitions in states for objects driven by human or other external interaction. The introduction of freely definable object states, possibly grouped in object state collections and coupled to the role/policy system of eZ Publish, enables a wide range of applications.

4 replies

Author	Message
Jason Hen	Saturday 20 February 2010 11:08:27 pm Very nice articles! Everybody may got some problems in daily life, like loan problems, how to lose weight fast? which is the best travel agency? and baby care problems? Google can help you to find out the answers.
Mercedes Barrio	Tuesday 30 March 2010 3:53:02 am Hello, I need that notifications were sent automaticaly when the state changes. It is posible to configure it with version 4.2.? If not, how can I implemented?. Thanks
Sander van den Akker	Wednesday 07 April 2010 8:16:49 am Just a note, object states can be used for different purposes too. I use it to flag items that should appear in a top menu for example. The advantage of this approach is that you don't have to to edit the whole content object (with the a possible menu checkbox attribute inside the meta attribute group). eZ Publish certified developer http://auth.ez.no/certification/verify/392313
Nicolas Pastorino	Wednesday 07 April 2010 8:34:43 am " Just a note, object states can be used for different purposes too. I use it to flag items that should appear in a top menu for example. The advantage of this approach is that you don't have to to edit the whole content object (with the a possible menu checkbox attribute inside the meta attribute group). " Thanks for sharing your use-case. Makes a lot of sense. Cheers ! -- 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

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

eZ debug

Timing:	Jan 30 2025 21:15:55
Script start
Timing:	Jan 30 2025 21:15:55
Module start 'layout'
Timing:	Jan 30 2025 21:15:55
Module start 'content'
Timing:	Jan 30 2025 21:15:55
Module end 'content'
Timing:	Jan 30 2025 21:15:55
Script end

Main resources:

Total runtime	0.0238 sec
Peak memory usage	6,144.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0054	588.4219	151.2422
Module start 'layout'	0.0054	0.0041	739.6641	220.7344
Module start 'content'	0.0094	0.0128	960.3984	1,006.4922
Module end 'content'	0.0222	0.0015	1,966.8906	33.9922
Script end	0.0237		2,000.8828

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0025	10.4889	14	0.0002
Check MTime	0.0011	4.4286	14	0.0001
Mysql Total
Database connection	0.0006	2.3467	1	0.0006
Mysqli_queries	0.0034	14.2927	3	0.0011
Looping result	0.0000	0.0381	1	0.0000
Template Total	0.0012	5.0	1	0.0012
Template load	0.0009	3.9503	1	0.0009
Template processing	0.0002	0.9928	1	0.0002
Override
Cache load	0.0006	2.5783	1	0.0006
General
dbfile	0.0002	0.8956	8	0.0000
String conversion	0.0000	0.0251	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	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs