The new deployed version of the process should be applied as soon as possible. To guarantee this, the new deployed version of the process becomes immediately the active version. The other process version becomes inactive.
Processes can run for a while. The system ensures that the running process will be completed even when a new version of the process is deployed and becomes active while this process is still running.
New sub-processes are an exception. A running process, which includes a sub-process, branches in the newest version of the sub-process. This is automatically done when the data type has not been changed in the new version of the sub-process When the data type of the start event is changed, consequently the interface is changed. The interface has another URL and therefore the flow cannot branch in the new version of sub-process and also cannot branch in the old version of the sub-process because this version is inactive. In this case, the process stops and you get an appropriate error message.
If you change the data type of the start event in a sub-process you need to change the call of the sub-process (URL) in the main process.
Ascertaining the URL of a New Sub-Process
The URL is generated during the built. To figure out the URL of the new sub-process version:
Open the Web Service Navigator.
On the Service Test tab choose in the Search Service Interfaces area Provider System .
In the Search For field enter *<WSDL file name>* and choose Search .
You can search only for the name.
Select the corresponding service interface in the result list.
In the Service Information area, expand the tray to display the WSDL URL.