5 Replies Latest reply on Dec 9, 2005 9:53 AM by Ronald van Kuijk

    Project in jBPM

    sy62k Newbie

      I am working on a project tracking tool. It will have mainly three sections, one each for clients, employees and jobs. Menu items are provided to add/remove/modify each of them. Users are allowed to see only a certain portions of the website based on their role. I have already implemented clients and employees section in JSF. Currently thinking of doing jobs section using jBPM. The flow is some thing like:
      1. A new job is created by one of the supervisors
      2. An email is sent to master level users
      3. An employee to whom the job is assigned does the work and updates the number of hours he has put.
      4. Supervisor changes the status of the job as completed.
      5. An email is sent to the master level users informing them that the jobs been finished.

      Any adivse is appreciated,
      Thanks a lot,

        • 1. Re: Project in jBPM
          Ronald van Kuijk Master


          What advide do you need. Everything you mention is possible with jBPM. The only thing is that in 3 the employee realy completes a task and the supervisor has to have another task (4) to 'complete' it. Nothing special here.

          • 2. Re: Project in jBPM
            sy62k Newbie

            I am sorry. I forgot to write my question. Does jBPM add any considerable advantage for my project as its kind of simple?


            • 3. Re: Project in jBPM
              Ronald van Kuijk Master

              If the 'jobs' are simple, jBPM probably does not offer a considerable amount of advantage. Probably JSF with a simple pageflow and a db is enough. This doesnt mean you *can* do it with jBPM :-)

              • 4. Re: Project in jBPM
                Alejandro Guizar Master

                I do see advantages even for simple processes. In the first place, you can easily adapt your software to eventual changes in the process. Second, and perhaps even more important, you get activity logs, which lets you do things like check which jobs are outstanding, evaluate performance and identify bottlenecks. Finally,
                jBPM is lightweight enough to fit even this size of project.

                If the logs are of no use to you, I'd adhere to Ronald's opinion.

                • 5. Re: Project in jBPM
                  Ronald van Kuijk Master

                  You are right Alex, I forgot the logs, but that is probably because we (internally at the company I work for) are used to having components that do log, so we get that automagically.

                  The other 'advantages' you mention are eventually also true. There could be a slight disadvantage also. If you do not defined e.g. the process in your war file and deploy it in one go with the webapp) it could introduce an extra deployment difficulty. You have to deploy the war as well as the process. It would be nice if we could create an example of an all in one war (code + process) as an example