Two-step workflow

Next topic

Author	Message
Antonio Goliati	Friday 17 February 2006 2:00:07 am How do I create a two-step validation workflow like the following : - a "contributor" create a document but cannot publish it - a "validator" then receives a mail or sees the document in his pending list, then he can refuse or validate the document without publishing it - a "publisher" then receives a mail or sees the document in his pending list, then he can refuse the document or decide to publish it (make it visible) Thank you for any help.
Artturi Markko	Tuesday 21 February 2006 3:33:49 pm Hello, I have exactly the same concern. Being new on Ez Publish, I have no answer but for what I've seen, documents are either in state 'Draft', 'published' or 'archived' (which is a by the way a bit behind what you can do with plone). I guess a solution implies having another state, maybe by creating a dedicated attribute in the class of the submitted content. I'd be very interested by hearing about solutions about that. Regards,

Author

Message

Friday 17 February 2006 2:00:07 am

How do I create a two-step validation workflow like the following :
- a "contributor" create a document but cannot publish it
- a "validator" then receives a mail or sees the document in his pending list, then he can refuse or validate the document without publishing it
- a "publisher" then receives a mail or sees the document in his pending list, then he can refuse the document or decide to publish it (make it visible)

Thank you for any help.

Artturi Markko

Tuesday 21 February 2006 3:33:49 pm

Hello,

I have exactly the same concern.

Being new on Ez Publish, I have no answer but for what I've seen, documents are either in state 'Draft', 'published' or 'archived' (which is a by the way a bit behind what you can do with plone).
I guess a solution implies having another state, maybe by creating a dedicated attribute in the class of the submitted content.

I'd be very interested by hearing about solutions about that.

Regards,

eZ debug

Timing:	Jan 18 2025 22:21:02
Script start
Timing:	Jan 18 2025 22:21:02
Module start 'layout'
Timing:	Jan 18 2025 22:21:02
Module start 'content'
Timing:	Jan 18 2025 22:21:02
Module end 'content'
Timing:	Jan 18 2025 22:21:02
Script end

Main resources:

Total runtime	0.0166 sec
Peak memory usage	2,048.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0049	587.8125	152.6094
Module start 'layout'	0.0049	0.0033	740.4219	39.4141
Module start 'content'	0.0082	0.0064	779.8359	89.1953
Module end 'content'	0.0146	0.0019	869.0313	30.3047
Script end	0.0165		899.3359

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0025	14.8986	14	0.0002
Check MTime	0.0011	6.8082	14	0.0001
Mysql Total
Database connection	0.0009	5.2567	1	0.0009
Mysqli_queries	0.0029	17.6688	3	0.0010
Looping result	0.0000	0.0792	1	0.0000
Template Total	0.0015	9.2	1	0.0015
Template load	0.0008	5.0262	1	0.0008
Template processing	0.0007	4.0956	1	0.0007
Override
Cache load	0.0006	3.6072	1	0.0006
General
dbfile	0.0011	6.5734	8	0.0001
String conversion	0.0000	0.0360	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