|
|
|
|
|
- Define processes with message flow communication
- Test the process from the developer point of view.
- Deploy the process (to integration test environment, to productive environment).
- Activate process
Situation after test and release action. Note that both processes are released together.
When we try to activate the process on current DB then we get the following dialog.
When we transfer the process to test or productive environment we can Activate the process.
Change GPL.UseCase2.MessageReceiver
Situation after test and release actions:
Note that “GPL.UseCase2.MessageSender v.1” is connected to both “GPL.UseCase2.MessageReceiver v.1” and “GPL.UseCase2.MessageReceiver v.2”
Activate “GPL.UseCase2.MessageReceiver v.2”
If you try to activate “GPL.UseCase2.MessageSender v.1” connected with both receivers in an environment where is nothing, you'll get wrong result. Both receivers will be active.
Change GPL.UseCase2.MessageSender
Test
GPL.UseCase2.MessageReceiver was changed as well.
Release
Note that now again just one message flow exist between these two new version
Activate
Note that after activation we have the same situation like in release - both processes are deployed and we have one message flow between them. There is no message flow pointing to retired process when both processes have a new version.