Validations
- A workflow process must have a unique process name. This means that a process cannot be created if the process name is empty or if a process with the same name already exists.
- A workflow process must have a process display name in the English (i.e. "en") locale. A display name in the user's locale should also be specified, but this is optional.
- A workflow process is required to specify a category.
- A released version of workflow process cannot be deleted once it has been enacted. This is required as even if a newer version of a process exists, process instances that are in progress when the new version becomes available run to completion with the version that they started with. Process definitions are also a necessary historical record that is drawn upon to create auditing information.
- A released version of workflow process cannot be deleted if it is referenced by a subflow activity in a released version of another process, where that released version is the latest released version.
- If a failure allocation strategy has been specified for the workflow process, then it's type must be TARGET.
- The callback service class name cannot be specified if the workflow process has not been exposed as a webservice.
- The callback service class name must represent a class that can be found on the application classpath.
- The callback service class name must represent a class that extends the org.apache.axis.client.Service class.