Validations
- A process definition cannot be imported if an unreleased version of a process already exists with the same name, and the overwrite option has not been selected.
- A process definition cannot be imported if a name for that process has not been specified
- A process definition cannot be imported if a process already exists with the same name and different process identifier. This validation ensures that an imported definition cannot inadvertently overwrite an existing process definition unless the process identifiers match.
- When copying an existing process, the name of the new process must be unique within the workflow system.
- The length of the name of the workflow process definition being imported must not exceed the maximum length allowed for such a name. This length is 254 characters.
- The length of the names of any of the workflow data objects contained in the workflow process definition being imported must not exceed the maximum length allowed for such a name. This length is 75 characters.
- The length of the names of any of the workflow data object attributes contained in the workflow process definition being imported must not exceed the maximum length allowed for such a name. This length is 75 characters.
- Any code table values that are contained in the workflow process definition being imported must be valid (i.e. the code table must exist and the specified code must exist in that codetable).
- For each localizable text in the process definition being imported, there must exist at least an entry for the English (i.e. "en") locale. Entries in other locales can also exist (e.g. the different user locales supported by the application) but each translation must be accompanied by an entry for the English locale.
- The identifiers for activities, transitions, transition condition expressions, loop condition expressions, events and reminders must be unique in the workflow process definition being imported.