Browse Prior Art Database

Provide compatibility pre-check and guided modification for the process instance migration

IP.com Disclosure Number: IPCOM000240401D
Publication Date: 2015-Jan-29

Publishing Venue

The IP.com Prior Art Database

Abstract

When customer need modify the business process template for any reason, any long running process instance need to be selected either migrate to the new template or wait it finish at the legacy template. Most of the custom would like to migrate to the new process template because it's reflect the new business model. To migrate the legacy process instance to the new process template is a challenge because sometimes it's hardly to maintain the process template is migration compatible. This disclosure offer an alternate approach by allow the migration compatible validation at the design time and provide the customer a chance to maintain the maximal compatibility There are 6 general ideas: 1. Provide a way to go though all process instances to identify which activity have the active token and how many 2. Summarize the process instances to the patterns based one which activity(s) have the active token, because at the process template only several activities might have the active token if the instance at the stable mode(instance migration need the instance at the stable mode), most of the activity are short running. 3. The result of the step 1 and 2 will be the input of the designer, to mark which activity delete or move will cause the migration compatible issue and how bad - how many instance will be impact 4. If an activity need move to other flow or deleted, will give customer a chance to select which activity will be the new host of the existing token. 5. When the new added variable initialized after active token, it's easy to know it's compatible 6. Different pattern use the different policy for the migration.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.

Page 01 of 19

Provide compatibility pre

Provide compatibility pre-

Terminology

Process Template:

--check and guided modification for the process instance migration

check and guided modification for the process instance migration

1


Page 02 of 19

Activity

2


Page 03 of 19

Process Instance: the data and flow to present the process for each run

3


Page 04 of 19

4


Page 05 of 19

Token: the pointer for the active activity

Process instance migration: apply the new process template to the unfinished process instances, which make sure the unfinished flow (after the token) can apply the new logic according to the new process template

5


Page 06 of 19

Background

When customer need modify the business process template for any reason, any long running process instance need to select either migrate to the new template or wait it finish at the legacy template. Most of the custom

would like to migrate to the new process template because it's reflect the new business model. To migrate the legacy process instance to the new process template is a challenge because sometimes it's hardly to maintain the process template is migration compatible. In today's support, we provided that capability but there are several drawbacks:

6


Page 07 of 19


1. when the customer modify the process template at the designer, it's hardly to verify if the modification is compatible for the instance migration
2. when an activity have a token, meanwhile this activity is deleted at the new template, the token will either move to other activity or leave it as the orphanage token by the single pre-defined policy.

3. when add a new local variable at the process template and initialize the variable at one activity, it's no way to know if it will be initialized after migrate the process instance.

4. all instance need follow the same migration policy (eg. delete the orphanage token, move the token to the next activity, etc.)

Customers would like to get the migration compatible validation as early as possible, eg. when an active activity has to be removed, the customer can be remind to select which activity can be the new host of the token, or just delete the token
There is currently no known products that provide this level of compatible pre-check.

Proposal

This proposal offer an alternate approach by allow the migration compatible validation at the design time and provide the customer a chance to maintain the maximal compatibility

There general idea is:
1. We provide a way to snapshot all process instances to identify which activity have the active token and how many
2. We can summarize the process instances to the patterns based one which activity(s) have the active token, because at the process template only have several activities might have the active token if the instance at the stable mode(instance migration need the instance at the stable mode), most of the activity are short running.

3. The result of the step 1 and 2 will be the input of the designer, to mark which activity delete or

7


Page 08...