JR58874: PRIMITIVES THAT HAVE AN OPTIONAL MODIFIER PROPERTY 'FORMAT' ARE REJECTED DURING DISCOVERY WHEN THE FORMAT IS UNKNOWN

bpm.8600.cf2018.03.delta.repository

APAR status

• Closed as program error.

Error description

• When you create an external service by discovering a REST
  service using a Swagger definition, and the Swagger definition
  lists a
  primitive data type with the optional modifier property
  'format', but
  the format string is unknown to BPM, recovery fails with error
  Data type <data type> with format <format> is not supported.
  

Local fix

• n/a
  

Problem summary

• IBM BPM allowed only the values defined in the Swagger
  specification 2.0 for the data type property "format". However,
  the specification also says that "the format property is an open
   string-valued property, and can have any value to support
  documentation needs."
  (https://github.com/OAI/OpenAPI-Specification/blob/master/versio
  ns/2.0.md#data-types). Therefore, this format should be
  accepted.
  

Problem conclusion

• A fix will be included in a future release of IBM BPM that
  alters the validation and treats the "format" property as an
  open string-valued property that can have any string value, as
  described in the specification. The restrictions for custom
  simple types combinations are still valid.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  BPM ADVANCED

• Fixed component ID

  5725C9400

Applicable component levels