Consider the following rules and guidelines when you import process objects from WSDL, XSD, and Swagger files:
Application Integration does not generate process objects if the WSDL, XSD, or Swagger document is incorrect.
If you use WSDL or XML schema files, Application Integration generates process objects from complex types and does not use the element declarations.
Application Integration converts enumerations to picklists.
Application Integration maps the unsupported types to string or the closest related type. Application Integration also prints a warning message about the type conversion on the
tab of the associated step.
If you use a Swagger file, Application Integration generates process objects only from the type definitions available in the
section. Application Integration does not generate process objects for the types that are used inline in the path declarations.
When multiple types share the same name, Application Integration adds indexes to the generated process object names to avoid duplication.
When you import process objects, you cannot overwrite existing process objects in the same location. Application Integration does not import duplicate process objects and displays an error in the log of the associated step.
When you import process objects with names that include the period (
) character from a URL that contains a WSDL source file, Application Integration replaces the period (
) character with the following string:
For example, if a process object name is
, Application Integration changes the name as follows: