This check prevents the developer from unnecessarily invoking the startProcess method. New method in BPM public API for checking whether process definition uses conditional startĪ developer can use the BPM public API to check whether a process definition is a conditional start process definition.A message is displayed explaining why the activation is not allowed. If so, the activation of the new conditional start process definition is prohibited. During deployment, the system automatically checks whether there is already an active conditional start process definition that uses the same message trigger. Additional check for shared trigger restriction in conditional start scenarios and descriptive error messages when activation of a conditional start process definition fails due to shared triggersĪ message trigger cannot be shared between several active conditional start process definitions.As of SP8 it is possible to share the same message trigger between conditional start and non-conditional start processes. With SP8 we have removed some restrictions and added some more checks to help minimize issues:īefore this SP8, triggers could not be used with conditional start scenarios. Read more about conditional start with SAP NetWeaver BPM in this blog series: Boost your Correlation Scenarios with Conditional Start in BPM.
The Conditional Start feature in SAP NetWeaver BPM is available as of SP6 of SAP NetWeaver 7.31.
