5 Replies Latest reply on Sep 17, 2007 3:07 PM by Ronald van Kuijk

    Understanding JBPM

    dingo dog Newbie

      The problem definition
      I would like to have a system where end users could upload their par files to my webapp and I could handle their processes for them independent of domain or usecase

      The webapp dependency
      1. Every workflow applies to one of x documents on the server. The user selects the document at runtime.
      2. Every workflow par uploaded to my webapp depends on user lists (to assign tasks at runtime) that are determined at runtime

      Progress
      I have figured out how to create pars and upload pars to my webapp.

      Question
      1. I cannot understand is how can I tie a workflow to a document. Would that be done in each process instance as a context variable that I pass to the process instance.

      2. If I want my webapp to be generic enough to accommodate any workflow definition then all that I perceive that I do in the webapp is to get the process instance and just call p.signal(). this would create token (or tokens in the case of forks) and processing can continue.

      I apologize for the long email but I want to be clear.

      Thanks.

        • 2. Re: Understanding JBPM
          Ronald van Kuijk Master

          bumping posts, especially ones of just a few days old, is really not appreciated by some people in this forum.

          Sometimes you do not get an answer because the answer is so obvious that people expect you to find out with a little investigation

          • 3. Re: Understanding JBPM
            dingo dog Newbie

             

            "kukeltje" wrote:
            bumping posts, especially ones of just a few days old, is really not appreciated by some people in this forum.

            Sometimes you do not get an answer because the answer is so obvious that people expect you to find out with a little investigation


            did u ever get smacked as a kid?

            • 4. Re: Understanding JBPM
              Edward Staub Expert

               

              1. I cannot understand is how can I tie a workflow to a document. Would that be done in each process instance as a context variable that I pass to the process instance.


              Yes

              2. If I want my webapp to be generic enough to accommodate any workflow definition then all that I perceive that I do in the webapp is to get the process instance and just call p.signal(). this would create token (or tokens in the case of forks) and processing can continue.


              "generic enough to accommodate any workflow definition" is pretty vague - there are infinite degrees of freedom you could be talking about. You probably need to answer this for yourself.

              -Ed Staub

              • 5. Re: Understanding JBPM
                Ronald van Kuijk Master

                No ding, I was the one doing the smacking... but now we are on the subject... See the answers Ed gave? Soooooo obvious...