Author |
Message
|
scar |
Posted: Thu Dec 22, 2005 5:49 am Post subject: Migrating process Instances. |
|
|
Centurion
Joined: 23 Jun 2004 Posts: 145
|
If I change the model and deploy it to the server is there any way to migrate the previous process instances to the new model, so those old process instances also will follow the new process flow rather than the old one. |
|
Back to top |
|
 |
vennela |
Posted: Thu Dec 22, 2005 5:51 am Post subject: |
|
|
 Jedi Knight
Joined: 11 Aug 2002 Posts: 4055 Location: Hyderabad, India
|
|
Back to top |
|
 |
scar |
Posted: Thu Dec 22, 2005 6:00 am Post subject: |
|
|
Centurion
Joined: 23 Jun 2004 Posts: 145
|
we are doing something like
get the container
Terminate the Process instnace
create a new instance with the same name and same container.
But this is turning out to be a maintenance nightmare, as we are also capturing data in an external db for reporting purpose. |
|
Back to top |
|
 |
hos |
Posted: Thu Dec 22, 2005 6:29 am Post subject: |
|
|
Chevalier
Joined: 03 Feb 2002 Posts: 470
|
As venella said: no.
Do it right the first time. I.e. make your instances 'migratable'. Forsee a version info, make your code flexible to handle dynamic container content, etc. I know there are several appends in this forum that deal with this topic. |
|
Back to top |
|
 |
tsrisudh |
Posted: Tue Dec 27, 2005 4:48 am Post subject: |
|
|
 Centurion
Joined: 11 Aug 2005 Posts: 113
|
What do you mean by migratable? I tried searching the forum,but did not find much info.
This is a major issue right, i make changes to my process but all the exiting instances will not follow the new path, how do we handle this in production kind of scenarios? _________________ Srisudhir Tadepalli |
|
Back to top |
|
 |
ProcessCentric |
Posted: Tue Dec 27, 2005 6:02 am Post subject: |
|
|
 Apprentice
Joined: 04 Nov 2005 Posts: 25 Location: USA
|
Your still asking for something that cannot be done. Once a process instance begins with a certain process template the process will continue using that template until it is complete. Only new process instances will follow the new template.
The only real option is to stop and restart those processes that are currently running in production so they pick up the new template. Keep in mind though they will "start over" and is this ok. You cannot "overlay" an existing template with a new one.
You must take this into account when you first use workflow. Ask questions like
1. Will I ever need to alter this process.
2. Where will I most likely alter this process.
3. Can my external applications handle different template versions based on a container value.
4. Can I build flexibility into my model upfront.
If you plan for this up front it should't be a big deal. If you don't plan for it or have radical changes in the process flow, and cannot have two different versions running at the same time, then have users complete all existing processes before implementing the new templtate. (no easy task if your at a large company).
hope that helps at least a little.
good luck |
|
Back to top |
|
 |
|