Late binding calls the wrong version of a subprocess
A parent process invokes a subprocess using late binding.
Both processes are in the same module. A new version of the subprocess
is created by copying the module and changing the valid-from timestamp.
After the module is deployed, the running instances of the parent
process continue to invoke the old version of the subprocess instead
of the new version.
Reason
In a late binding, the process template name of the subprocess is specified as part of the reference partner properties of the invoke activity in the parent process. Business Process Choreographer determines the version of the process that is currently valid at run time.A common reason for late binding using the wrong version of a subprocess is that the module that contains the subprocess does not have a Service Component Architecture (SCA) export. Without an export, processes in other modules are not visible to the parent process and it always invokes the version of the subprocess that is in the same module.
This topic only applies to BAW, and is located in the BAW repository. Last updated on 2025-01-20 10:38