| Author |
Message
|
| MaheshPN |
 Posted: Thu Jun 02, 2005 8:33 am Post subject: Handling old process instances with new template/model |
 |
|
Master
Joined: 21 May 2003
Posts: 245
Location: Charlotte, NC
|
Hi Guys,
Due to change in the business, we need to make a change in the existing model followed by adding new containers.
As most of the loans are long lived and will be running with old template. When the developers change the code to set new containers, its going to yell for old loans. The solution I thought was to check the version of the template before check-in. Is there any better solution or can we do something so that WF can handle automatically?
Thanks in advance!!
-Mahesh |
|
| Back to top |
|
 |
| karthik |
| Posted: Thu Jun 02, 2005 10:57 am Post subject: |
|
|
Centurion
Joined: 17 Oct 2003
Posts: 114
|
Hi Mahesh
Are you saying that you are using the same code to set containers for both the old models as well as the new models.
My understanding of the template model is that the already running process instances will continue to use the same model and any new process instances created after the deployment of the new template will use the new template (based on the Valid from date on the new template).
So, if you can explain what you are trying to do here .. will give us an insight and will be more educational to all of us here as well
Thanks
Karthik |
|
| Back to top |
|
|
| MaheshPN |
| Posted: Thu Jun 02, 2005 11:12 am Post subject: |
|
|
Master
Joined: 21 May 2003
Posts: 245
Location: Charlotte, NC
|
Hi Karthik,
The application remains the same. we made the change in the underlaying model, added some new activities. So,when the application set the new container element, it has check whether the process instance is new or old before setting the new container element. As you said correctly, old instances will follow the old template and will not have the new containers I have added.
Hope this makes it clear.
thanks,
-Mahesh |
|
| Back to top |
|
|
| jmac |
| Posted: Thu Jun 02, 2005 1:19 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
Mahesh:
I generally have a "version" member that I default in the Source Container, and simply map to all activities. This is similar to what you are suggesting about checking template version, I think.
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| koko |
| Posted: Fri Jun 03, 2005 4:34 am Post subject: |
|
|
Master
Joined: 26 Sep 2003
Posts: 206
|
Guys,
I have another question related to this one.
say I have one template running till now. I modify it ( add some data, activities ) to it and let this new template take effect from tomorrow.
I may have new flows coming into my system after tomorrow which need to work according to the old template's logic. I thinking of appending the version no to the template name and treat these as two seperate flows rather than seggregate them with a version no in the source.
Am I on the right track??
_________________
Thanks
Koko |
|
| Back to top |
|
|
| jmac |
| Posted: Fri Jun 03, 2005 5:23 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
| koko wrote: |
| Am I on the right track?? |
I don't think there is any other way to do this. So, yes you are on the right track.
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
|
|
