[opencms-dev] openCMS workflow - Please help!

Wed Jan 23 15:39:42 CET 2008

@Huy Tran: Thank you for the input. Yes, you have a point there - it may be
more comfortable when the user could approve/reject directly in the website
preview or inside the FCK editor. I've chosen the FCK Editor approach for my
previous workflow implementation. Maybe I'll add this feature to the current
one anytime later but keep in mind this is just more a UI thing. Wherever
you initiate your approval process you have to implement some logic for
managing workflow states in every case. And that's the major amount of work.

I would be very interested how you have realised the different workflow
states in detail? Does it also perform permission modifications? Would be
happy if you have some more input/ideas for me.

@Viki: Sorry, currently you can just approve/reject via the workplace
context menu. If you want you can add these functionalities yourself and
contribute ;-)

@Alkakon: I'm wondering why my mails are alway boucing back (see
below,opencms-dev-bounces at opencms.org
)?

Cheers
David

On Jan 23, 2008 8:17 AM, Vikrama Sanjeeva <viki.sanjeeva at gmail.com> wrote:

>
> David, I have downloaded the full-package (OpenCms_Workflow2_v0.4.1_full-
> package.zip ~ 4.73MB ).  I will install it. However, as Huy Tran said, I
> am also looking to achieve this functionality out of workplace. Means, a
> toolbar will be there right on website which will allow customers to
> create/edit/publish contents using pre defined customize process. Lets
> say it "Approval Process".
>
>   Could this be done via "OpenCms_Workflow2" ? OR as Huy Tran said, I will
> have to develop the Approval Process manually using OpenCMS API?
>
>   This is the time for me to decide the right approach for my requirement.
> I will appreciate any guidence/help.
>
> Thanks.
>
> Bye,
> Viki.
>
> 2008/1/23 <HuyTran at c-mg.net>:
>
>   Hi,
> >
> > I think this is very good. I first came up with the same ideas but our
> > customers who is Reviewers and Approvers don't want to work in the
> > workplace, they want to use a toolbar on the page itself to approve or
> > reject the pages. So if your customer feel easy to work in the workplace, I
> > think this is the best solution.
> >
> >
> >
> > Good lucks.
> >
> >
> >
> > Huy Tran
> >
> >
> >  ------------------------------
> >
> > *From:* opencms-dev-bounces at opencms.org [mailto:
> > opencms-dev-bounces at opencms.org] *On Behalf Of *David Trattnig
> > *Sent:* Tuesday, January 22, 2008 11:57 PM
> > *To:* The OpenCms mailing list
> > *Subject:* Re: [opencms-dev] openCMS workflow - Please help!
> >
> >
> >
> > Hi Viki
> >
> > > * user A created a content
> > > * content went for to user B.
> > > * user B either Rejects or Approves content
> > > * if B approves, it went to C
> > > * Finally C publishes the content
> >
> > I would say that's the main functionality of the *OpenCms Workflow2
> > Module* which can be found here
> > http://sourceforge.net/project/showfiles.php?group_id=180314 (Download
> > the latest full package version). As you don't need advanced workflow
> > features I reckon this workflow implementation fits best for you. Especially
> > you don't need to modify/rebuild the OpenCms core as *Huy Tran*suggested and configuration is very easy.
> >
> > First of all you've to create three projects for the three types of
> > users A, B and C and assign these users (respectively their usergroups) to
> > the projects (I've named the projects "Offline", which is already available,
> > "Review" and "Approval"). Don't forget to assign all three projects to the
> > same directory ("/", *root *suggested).
> >
> > Then go on with the quick installation guide:
> >
> >    1. Import the *commons*, *springmanager *and * workflow2* module
> >    via OpenCms module import mechanism.
> >    2. Copy opencms-workplace.xml to %OPENCMS_DIR%\WEB-INF\config\
> >    (replace current configuration)
> >    3. Restart your server.
> >    4. As a final step you have to create your workflow inside the
> >    workflow administration panel of OpenCms. Voilá!
> >
> > That's all. The Workflow2 Module automatically uses the OpenCms DB
> > connection without configuration. If you need advanced DB configuration have
> > a look at *readme.txt *inside the distribution package. In case of
> > problems just leave me a message.
> >
> > Have fun
> > David
> >
> >  2008/1/22 Vikrama Sanjeeva <viki.sanjeeva at gmail.com>:
> >
> > Thanks all. Well, i am least interested in doing all the manually using
> > openCMS API. However, I am now looking for free workflow engines for
> > openCMS. The is the decision time for us as we are going to build client's
> > website on openCMS and providing functinalities of workflow like the one i
> > mentioned in my 1st post.
> >
> >
> >
> >   Which opencms-workflow engine is more mature? In terms of less bugs,
> > easy to use and providing basic workflow functionalities?
> >
> >
> >
> > Here are two which I know. One is by Mr. Shi Yusen
> >
> >
> >
> > 1: OpenCms-jBPM
> >
> > 2: Bearingpoint-OpenCms-Modules Commons
> >
> >
> >
> > Please help me in selecting suitable workflow engine for openCMS?
> >
> >
> >
> > Bye,
> >
> > Viki.
> >
> > On Jan 21, 2008 9:43 PM, Shi Yusen <shiys at langhua.cn> wrote:
> >
> > Perhaps you can try our free OpenCms-jBPM module. It's here:
> > http://sourceforge.net/projects/jbpm-opencms/
> >
> > Regards,
> >
> > Shi Yusen/Beijing Langhua Ltd.
> >
> > 在 2008-01-21一的 17:24 +0300 ，Vikrama Sanjeeva写道：
> >
> > > Hi ALL,
> > >
> > >   This is urgent question and am looking for help and guidence in this
> > > regard.
> > >
> > > Is below workflow achievable using openCMS?
> > >
> > > * user A created a content
> > > * content went for to user B.
> > > * user B either Rejects or Approves content
> > > * if B approves, it went to C
> > > * Finally C publishes the content
> > >
> > > this is simple workflow. Please tell me how I can achieve this
> > > workflow in openCMS?
> > >
> > > thanks
> > >
> > > Bye,
> > > Viki.
> > >
> > >
> > >
> > >
> >
> > > _______________________________________________
> > > This mail is sent to you from the opencms-dev mailing list
> > > To change your list options, or to unsubscribe from the list, please
> > visit
> > > http://lists.opencms.org/mailman/listinfo/opencms-dev
> >
> >
> > _______________________________________________
> > This mail is sent to you from the opencms-dev mailing list
> > To change your list options, or to unsubscribe from the list, please
> > visit
> > http://lists.opencms.org/mailman/listinfo/opencms-dev
> >
> >
> >
> >
> >
> > _______________________________________________
> > This mail is sent to you from the opencms-dev mailing list
> > To change your list options, or to unsubscribe from the list, please
> > visit
> > http://lists.opencms.org/mailman/listinfo/opencms-dev
> >
> >
> >
> >
> > _______________________________________________
> > This mail is sent to you from the opencms-dev mailing list
> > To change your list options, or to unsubscribe from the list, please
> > visit
> > http://lists.opencms.org/mailman/listinfo/opencms-dev
> >
>
>
>
> _______________________________________________
> This mail is sent to you from the opencms-dev mailing list
> To change your list options, or to unsubscribe from the list, please visit
> http://lists.opencms.org/mailman/listinfo/opencms-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://webmail.opencms.org/pipermail/opencms-dev/attachments/20080123/a4482ba1/attachment.htm>