Workflow approval by group such as Editors?

Next topic

Author	Message
Clive Flatau	Friday 21 January 2005 7:28:33 am Can somebody confirm that it is <b>not</b> possible to give approval capability to a group in the latest release v3.5 for a workflow i.e. multiple users i.e. that a single named user has to be the approver. We are building a system for news authors and editors. Multiple editors as approvers is an obvious requirement. Could I get round it by creating multiple event/aprroves, each with a named user, for the same section (I don't think so). Clive
Balazs Halasy	Saturday 22 January 2005 12:36:57 am Hi there, As far as I know, it has never been possible to assign a group of approvers. Don't think you can create any easy workaround. In addition: keep in mind that once an object is pending (waiting for approval) it can not be edited by anyone (neither the original author or the person who is assigned to approve it). In other words, the editor can only accept or reject the pending object. Allman
Clive Flatau	Monday 24 January 2005 1:47:49 am Thanks for the definitive response. Clive

Author

Message

Friday 21 January 2005 7:28:33 am

Can somebody confirm that it is <b>not</b> possible to give approval capability to a group in the latest release v3.5 for a workflow i.e. multiple users i.e. that a single named user has to be the approver.

We are building a system for news authors and editors. Multiple editors as approvers is an obvious requirement. Could I get round it by creating multiple event/aprroves, each with a named user, for the same section (I don't think so).

Clive

Balazs Halasy

Saturday 22 January 2005 12:36:57 am

Hi there,

As far as I know, it has never been possible to assign a group of approvers. Don't think you can create any easy workaround. In addition: keep in mind that once an object is pending (waiting for approval) it can not be edited by anyone (neither the original author or the person who is assigned to approve it). In other words, the editor can only accept or reject the pending object.

Allman

Clive Flatau

Monday 24 January 2005 1:47:49 am

Thanks for the definitive response.

Clive

eZ debug

Timing:	Jan 31 2025 08:05:04
Script start
Timing:	Jan 31 2025 08:05:04
Module start 'layout'
Timing:	Jan 31 2025 08:05:04
Module start 'content'
Timing:	Jan 31 2025 08:05:04
Module end 'content'
Timing:	Jan 31 2025 08:05:04
Script end

Main resources:

Total runtime	0.0187 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.0054	588.2656	151.2266
Module start 'layout'	0.0054	0.0027	739.4922	36.6797
Module start 'content'	0.0081	0.0086	776.1719	90.0938
Module end 'content'	0.0167	0.0019	866.2656	29.9922
Script end	0.0187		896.2578

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0027	14.5128	14	0.0002
Check MTime	0.0012	6.3496	14	0.0001
Mysql Total
Database connection	0.0009	4.7310	1	0.0009
Mysqli_queries	0.0023	12.3601	3	0.0008
Looping result	0.0000	0.0586	1	0.0000
Template Total	0.0014	7.3	1	0.0014
Template load	0.0010	5.4103	1	0.0010
Template processing	0.0003	1.8072	1	0.0003
Override
Cache load	0.0007	3.5864	1	0.0007
General
dbfile	0.0035	18.9455	8	0.0004
String conversion	0.0000	0.0382	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