3 Replies Latest reply on Aug 5, 2008 10:20 AM by kukeltje

    reopen a process instance ?

    memius

      Is it conceptually correct (and if so, technically possible) to reopen a closed process instance ?

      Consider next situation : you have an insurance dossier that is functionally 'closed' (all payments done, everyone happy, etc...)
      But ... there is always the option that new data pops up and this dossier has to be 'reopened'. Let's say that this can happen within 5 years after 'closing' the dossier.

      How do you put this in a process ?

      You could eg. create a time for five years and after that, close the process instance (but even then it seems to be functionally possible to have the need to reopen a dossier).
      or you could leave the process instance open (but all process instances would stay alive then :s).


      What is the normal way of doing this ? It appears to me that this kind of process occurs a lot (medical files, accountancy, law suit, ...)


      Btw, I consider the correct concept more important than the technical jbpm possible solutions.


      Sincerely,
      Dieter D'haeyere.

        • 1. Re: reopen a process instance ?
          kukeltje

          think out of the box... Think dossier and process, the latter working on the former. Dossiers stay for as long as e.g. legally needed. processes working on dossiers end. If new data pops up, a new 'process' for the same dossier is started. Maybe a specific version, related to some info in the dossier.

          • 2. Re: reopen a process instance ?
            memius

            Well, my problem might be that I don't really see that 'box' ;)

            When are you talking about a process ? How far does that go ...
            Indeed a dossier is db data ... doing some data processing on that dossier is a process ... So if I understand you correctly, you would put the different kinds of related actions in a process (if they are consecutive, eg.)
            And not create a 'big' process where you deal with one dossier until it is finished.
            Now ... my problem is ... we have some tasks which are related to a dossier but don't really fit in a process (eg. prepare and send a mail if some trigger occurs). Would you create tiny processes for any of those tasks ? Even if they only contain one task... or would you create task instances at runtime and don't put them in any process... (which might not be very consistent, since in the one case you'll create process variable (eg. dossier id) and in the other you'll have to create task variables for the same data)

            Anyway .. just some thoughts... I don't expect to get the only exact answer... but these are just some conceptual thoughts I struggle with.



            • 3. Re: reopen a process instance ?
              kukeltje

               

              And not create a 'big' process where you deal with one dossier until it is finished.


              Depends... an simple insurance claim could be dealt with within one process, more complex claims which could take many years (e.g. personal injury) maybe not. And certainly do not look at a morgage as being a process.

              Would you create tiny processes for any of those tasks ?

              You could if you want to take advantage of one tasklist, reminders etc...

              which might not be very consistent, since in the one case you'll create process variable (eg. dossier id) and in the other you'll have to create task variables for the same data)


              Keep task data as minimal as possible... just like processdata. Store all that in your domain model and just reference it