Bug 1333589

+++ This bug was initially created as a clone of Bug #1333587 +++

Description of problem:


A parent process is started in BPM Suite 6.0 , at some point it enters a subprocess, the subprocess stops waiting for a signal or for a human task, then we migrate the base to BPM Suite 6.2, when we continue the subprocess in 6.2, the parent process will not be notified.

Version-Release number of selected component (if applicable):
n/a

How reproducible:
Always

Steps to Reproduce:
1. In BPM Suite 6.0.x, create a process that has a subprocess that will stop its execution at some point waiting for an external action (a signal or a human task)
2. Stop the server, migrate the database using the upgrade scripts first using the script to upgrade from 60 -> 61, then use the script to update the DB from 61 -> 62
3. Start business central pointing to the migrated DB or create a standanlone app that will allow you to continue the sub processinstance;
4. Continue the subprocess execution;

Actual results:

The parent process will get stuck waiting for the subprocess completion, but in the database and in the view, you will see that the subprocess was actually completed.

Expected results:

The parent process should continue its execution normally after the subprocess has been completed.

Additional info:

Attached you can find databases scripts that will help you to reproduce this, but it is not easy to reproduce it.

This error is happening because a flag called signalCompletion was only added to BPM Suite 6.2 and the sub process does not notify the parent process if it is not set to true, but since it is not present in the migrated database, it is restored as false, so the parent process is never notified.

--- Additional comment from William Antônio on 2016-05-05 18:23 EDT ---