Polymorphic Support Limitations

Before creating layouts for polymorphic business objects or adding descriptive flexfields to a layout, review the limitations here:

• Extensible flexfields (EFFs) are only supported for ADF REST services.
• A polymorphic business object is assumed to only contain a single discriminator field. Multiple discriminators are not supported.
• The discriminator field must be a string.
• When a polymorphic column or form field expands, the order is global segments, the discriminator, and then context-sensitive segments. Note that changing the order of the global segments or context-sensitive segments is not supported.
• In order to bind a polymorphic business object to a layout, it must expose polymorphic business object metadata. In an OpenAPI metadata document, this means that it must contain a "discriminator" and "oneOf" syntax in the schema for the business object. The "anyOf" polymorphic business object syntax is not supported.
• Hierarchical polymorphic business objects are not supported. All polymorphic segments must be defined directly on the polymorphic business object in the OpenAPI metadata document.
• When a layout contains a polymorphic business object, the "fields" and "expand" query parameters should not be manually configured in the Download Parameters area of the Layout Designer's Download tab.
• The case where a child business object's fields are determined by a parent business object's discriminator value is not yet supported.
• Limiting discriminator values for a polymorphic business object displayed in a Table layout does not limit:
  • The set of values that can be chosen in a list of values (LOV) for a discriminator field
  • The values users can provide for a discriminator field