I know this is not easy to explain, but perhaps a MBPM Developer understands what our problem is ;-)
Scenario:
We have designed a small subprocess that is used like a "v7 map segment" within multiple other processes. The subprocess also contains an action which "clones" the folder.
We figured out that the cloning (copying) of the folder only works for one of the parent processes, all other throw an expception within the systems stored procedure "esp_update_action". This error is caused because of wrong entries inside the eSubprocess table.(see Screenshot)
We embedded the subprocess in more than one process but the eSubprocess table only references to one of these processes.
Solution/Workaround
The stored procdure [psp_clone_all_processes] queries the eSubprocess table by eSubProcessName and eVersion number. It seems that the subprocess version number has to be equal with the version of the parent process, which is not the case. eSubProcessName is the primary key here, therefore also querieng for eversion makes no sense!
As a workaorund we modified the query and removed the eVersion parameter.