Three level Workflow, is it possible?

Previous topic

General

Next topic

Author	Message
Ted Striker	Sunday 26 September 2004 11:50:08 pm Hi, I'm new to workfolows, I have stablished some simple workflow where a User Tye could create but not publish an article and some other higher level user just allowed it to be published. But, is it poossible to do the following workflow? <b>1. Section Editor:</b> User that can create content but not publish inside a specific section (when saving the doc next level will be notified) <b>2. Section Chief Editor:</b> Can validate (not publish) the articles created by the Editor level (can also create and modify the contents created by the Editor) and send the work to publish <b>3. Section Admin:</b> gets noticifactions and send the work to publish Can this workflow be stablish with eZPublish? Or just more simple workflows are allowed? TIA Can you feel it Mr. Anderson? Closing in on you? Oh I can, I really should thank you after all. It was, after all, it was your life that taught me the purpose of all life. Purpose of life is to end.
Björn Dieding@xrow.de	Monday 27 September 2004 8:42:02 pm Did you ever had a change to look in to build-in "approval" workflow? It should be pretty similar to the things you want to archive. You might need to add the 3 third step to that workflow though. And out the publish to a later point. I think this is possible, but it can get tricky when you edit a draft at the 2nd step. Looking for a new job? http://www.xrow.com/xrow-GmbH/Jobs Looking for hosting? http://hostingezpublish.com ----------------------------------------------------------------------------- GMT +01:00 Hannover, Germany Web: http://www.xrow.com/
Ted Striker	Tuesday 28 September 2004 12:12:14 am Thanks Björn I will take a look at what you say, and let you know if it does the job. Honestly I believe that the second level will be overpasses in the end Can you feel it Mr. Anderson? Closing in on you? Oh I can, I really should thank you after all. It was, after all, it was your life that taught me the purpose of all life. Purpose of life is to end.

Author

Message

Ted Striker

Sunday 26 September 2004 11:50:08 pm

Hi,

I'm new to workfolows, I have stablished some simple workflow where a User Tye could create but not publish an article and some other higher level user just allowed it to be published. But, is it poossible to do the following workflow?

1. Section Editor: User that can create content but not publish inside a specific section (when saving the doc next level will be notified)

2. Section Chief Editor: Can validate (not publish) the articles created by the
Editor level (can also create and modify the contents created by the Editor) and send the work to publish

3. Section Admin: gets noticifactions and send the work to publish

Can this workflow be stablish with eZPublish? Or just more simple workflows are allowed?

TIA

Can you feel it Mr. Anderson? Closing in on you? Oh I can, I really should thank you after all. It was, after all, it was your life that taught me the purpose of all life. Purpose of life is to end.

Björn Dieding@xrow.de

Monday 27 September 2004 8:42:02 pm

Did you ever had a change to look in to build-in "approval" workflow?

It should be pretty similar to the things you want to archive.

You might need to add the 3 third step to that workflow though. And out the publish to a later point.

I think this is possible, but it can get tricky when you edit a draft at the 2nd step.

Looking for a new job? http://www.xrow.com/xrow-GmbH/Jobs
Looking for hosting? http://hostingezpublish.com
-----------------------------------------------------------------------------
GMT +01:00 Hannover, Germany
Web: http://www.xrow.com/

Ted Striker

Tuesday 28 September 2004 12:12:14 am

Thanks Björn I will take a look at what you say, and let you know if it does the job.

Honestly I believe that the second level will be overpasses in the end

Can you feel it Mr. Anderson? Closing in on you? Oh I can, I really should thank you after all. It was, after all, it was your life that taught me the purpose of all life. Purpose of life is to end.

eZ debug

Timing:	Jan 18 2025 21:12:16
Script start
Timing:	Jan 18 2025 21:12:16
Module start 'layout'
Timing:	Jan 18 2025 21:12:16
Module start 'content'
Timing:	Jan 18 2025 21:12:16
Module end 'content'
Timing:	Jan 18 2025 21:12:16
Script end

Main resources:

Total runtime	0.0196 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.0069	589.8125	152.6250
Module start 'layout'	0.0069	0.0043	742.4375	39.4609
Module start 'content'	0.0112	0.0060	781.8984	93.3047
Module end 'content'	0.0172	0.0023	875.2031	34.3047
Script end	0.0195		909.5078

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0027	14.0400	14	0.0002
Check MTime	0.0012	6.2836	14	0.0001
Mysql Total
Database connection	0.0007	3.6120	1	0.0007
Mysqli_queries	0.0038	19.2540	3	0.0013
Looping result	0.0000	0.1182	1	0.0000
Template Total	0.0019	9.7	1	0.0019
Template load	0.0010	5.0678	1	0.0010
Template processing	0.0009	4.6439	1	0.0009
Override
Cache load	0.0006	2.9883	1	0.0006
General
dbfile	0.0006	3.0261	8	0.0001
String conversion	0.0000	0.0451	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