[opencms-dev] Adding Workflow functionality to OpenCMS ver 6.0

[Arash Kaffamanesh]

Shi,

That sounds very great, why not to contibute it to the whole commnuity, does Alkacon know about it?
Does OSWorkflow support BPEL?

Could you please provide more information about your implemenation?

Kind Regards,
Arash



-----Original Message-----
From: opencms-dev-bounces at opencms.org [mailto:opencms-dev-bounces at opencms.org] On Behalf Of Shi Yusen
Sent: Freitag, 16. September 2005 19:12
To: 'The OpenCms mailing list'
Subject: ??: [opencms-dev] Adding Workflow functionality to OpenCMS ver 6.0


Hi Rajiv,

We have integrated OSWorkflow 2.7 with OpenCMS 6.0.0 in an intra website of China Armed Police. If you choose the same engine, I'd like to share the implement with you.

Regards,

Shi Yusen/Beijing Langhua Ltd.

-----邮件原件-----
发件人: Tristan Tarrant [mailto:tristan.tarrant at dataforte.net] 
发送时间: 2005年9月15日 0:54
收件人: rajiv at eutkarsh.com; The OpenCms mailing list
主题: Re: [opencms-dev] Adding Workflow functionality to OpenCMS ver 6.0

On Wed, 2005-09-14 at 12:07 +0200, Rajiv Terwadkar wrote:
> Dear All,
> I would like to add workflow functionality in OpenCMS, I will 
> appreciat your comments/ help / site references etc for this Thanks 
> and Regards Rajiv

Personally I would like to see workflow functionality attached to content items in the vfs: currently opencms' workflow is completely separate and more of an internal messaging system. Workflow should be based on project, group membership and template (different types of objects may have different workflows). Using these properties an initial state is set on the object (or maybe even multiple objects, but this is more difficult). The explorer view should show the current state and an entry in the vfs context menu should show a dialog with a list of possible states which are available for the next step and a list of possible target users for the chosen next state. States may even imply opencms actions: e.g. when an object is forwarded to a specific state it may be automatically published. For the workflow engine I'd use the excellent OSWorkflow which also allows adding beanshell scripts within actions.

This is my 2¢. Opinions are welcome.

Tristan





_______________________________________________
This mail is send to you from the opencms-dev mailing list
To change your list options, or to unsubscribe from the list, please visit http://mail.opencms.org/mailman/listinfo/opencms-dev