Binding

Key	Description
AMBW-46861	Summary: When invoking a REST service created with a Swagger file having an "array" tag under the Components/Schemas section, the "array" tag is not reflected in the runtime Swagger file. Workaround: Add the "array" tag in the generated runtime Swagger file manually if you need to create a REST service/reference binding.
AMBW-46806	Summary: Accept header value for Fault response is not honored in Swagger UI when the OAS 3.0 REST service configured with multiple response formats is hit. Workaround: Use Postman Client to hit the service and pass the Accept Header according to the expected response content-type.
AMBW-46721	Summary: When creating a top-down REST service with an OAS 3.0 JSON file having response header parameters and multiple response formats, the parameters are not reflected in the service binding. Workaround: None
AMBW-46663	Summary: If an OAS 3.0 REST service is created using a JSON file having anyOf/oneOf keywords with one of the schema referred with "$ref" and another sub-schema as "inline", then the inline schema is not reflected in the Reply activity. Workaround: None
AMBW-46607	Summary: If an OAS 3.0 REST service is created using a Swagger file having inline schema with "oneOf/anyOf" or nesting with "allOf", then the schema elements are not resolved in the Input tab of the Reply activity. Workaround: None
AMBW-46002	Summary: The "allOf" tag is not reflected in the runtime Swagger JSON generated for the REST service created using an imported Swagger JSON having the "allOf" tag. Note: The schemas are merged into a single schema object in the runtime Swagger file and this doesn't impact the functionality. Workaround: None.
AMBW-45941	Summary: The Swagger specifications having the pattern keyword are not supported in ActiveMatrix BusinessWorks 6.x. Workaround: You can either manually modify the Swagger specifications to remove the pattern tag before importing it in TIBCO Business Studio for BusinessWorks, or else after creating the service, you can manually modify the XSD by removing the pattern restriction for the respective element definition.
AMBW-44739	Summary: The description provided for form parameters on REST 3.0 service binding is not reflected on the reference binding as well as on top-down service binding's Form Parameters table. Workaround: None
AMBW-44492	Summary: The `415: Unsupported Media Type error` is thrown on Invoke activity of a REST Reference Binding while invoking a REST service with Request and Response formats other than JSON. That is, XML or Text. Workaround : To get rid of the error, select JSON format in Request and Response along-with other formats.
AMBW-44479	Summary: The dynamicConfigurations WSDL part and dynamicConfigurations element aren't automapped by default for the input of Invoke activity created from the reference binding. Workaround: Either map manually or map using the Show Check and Repair option.
AMBW-44338	Summary: On selecting Binary checkbox in Response tab of REST Service Binding, if we keep default configurations in Resource Schema then the Reply activity's response is seen as "String" instead of base64Binary. Workaround: On selecting Binary checkbox re-select "binary" or "base64" from Resource Schema dropdown.
AMBW-44208	Summary: The `java.lang.NullPointerException` is thrown on adding new operation to a REST service when you change the JSON Definition Style or the Request schema from the drop-down for the newly added operation. Workaround: If you are adding new operation then select the required schemas in the REST Service Wizard and avoid modifying it from service binding.
AMBW-44197	Summary: `REST Service Binding configuration error` is thrown at design time when the Resource Schema of DELETE operation is modified in the Response tab of REST Service Binding. Workaround: If you want the DELETE operation response to be other than String then select the appropriate value in the drop-down menu for Response while creating a service using REST Service Wizard. This workaround is not applicable for the Binary Response format.
AMBW-44116	Summary: For REST 3.0 service if you select Binary check box in Response, then at design time the Resource Schema details "$item base64Binary" is not displayed on Response tab for all operations on service binding and for POST operation on reference binding. There is no impact on anything at runtime. Workaround: None.
AMBW-44022	Summary: The Swagger UI accessed using `Lrestdoc` command is not supported to show the callbacks section for the REST Operation of an ActiveMatrix BusinessWorks REST Service Endpoint created by dragging a Swagger Path whose operation is configured with callbacks. Workaround: None.
AMBW-43156	Summary: The Swagger UI is seen as blank when the Swagger URL is hit from Internal Web Browser in TIBCO Business Studio for BusinessWorks. Workaround: Hit the Swagger URL from an external browser.
AMBW-43023	Summary: The "format" tag is not created for "Password" type form parameter in bottom-up REST service and hence seen as String on the reference binding. Workaround: Manually add the "format" : "password" tag to the form parameter in the swagger file.
AMBW-36113	Summary: A multipart message where one part points to type and the other part points to element and a message using mixed security mode is not supported. Workaround: Change mixed security mode in a given WSDL.
AMBW-32951	Summary: A SOAP service responding with mustUnderstand attribute as true is ignored irrespective of selecting or deselecting the Ignore mustUnderstand check box on the SOAP Reference binding. This behavior does not affect the client and server communication. Workaround: None
AMBW-32760	Summary: On creating SOAP Reference Binding with the concrete WSDL generated at run time with multilevel schema imports, the java.lang.NullPointerException is displayed when clicking the reference binding. Workaround: None
AMBW-29098	Summary: When creating a concrete WSDL by right-clicking on the Service Descriptor folder, the following error is generated at design time: WSDL import error. Workaround: None
AMBW-27870	Summary: On importing WSDL with RPC Encoded style, a validation error is generated at design time since the underlying schema with namespace http://schemas.xmlsoap.org/soap/encoding/ is not generated. Workaround: To remove the validation error and create the SOAP Reference Binding, download the encoding schema with the said namespace and ensure that schema is a part of the application module or the shared module.
AMBW-27435	Summary: When module properties used from a shared module project were renamed, the changes made were not reflected at the SOAP binding level. Workaround: Select the updated module property from the drop down in the SOAP binding.
AMBW-26806	Summary: When a REST service with a schema that uses a type which was imported from another XSD is invoked in a REST Reference Binding, it fails with the ServiceRuntimeException. Workaround: None
AMBW-23104	Summary: When the WSDL uses multiple parts in the Request body of an operation, a design time validation error occurs on the generated SOAP reference binding. The application works fine at run time. Workaround: None
AMBW-13607	Summary: REST Doc UI is not supported on Firefox browser. Workaround: Use other browsers for the Doc UI.
AMBW-13572	Summary: For some use cases, REST Doc UI does not show the correct error code in case of Internal Server errors on the Server side. Workaround: Check the raw message that contains the correct error code.
AMBW-13485	Summary: REST Doc UI does not support browsers like Internet Explorer. Workaround: Use Chrome browsers for the Doc UI.
AMBW-8982	Summary: Changing the Resource name in the REST service Bindings tab, does not update the Resource Service Path. Workaround: None

AMBW-46861

Summary: When invoking a REST service created with a Swagger file having an "array" tag under the Components/Schemas section, the "array" tag is not reflected in the runtime Swagger file.

Workaround: Add the "array" tag in the generated runtime Swagger file manually if you need to create a REST service/reference binding.

AMBW-46806

Summary: Accept header value for Fault response is not honored in Swagger UI when the OAS 3.0 REST service configured with multiple response formats is hit.

Workaround: Use Postman Client to hit the service and pass the Accept Header according to the expected response content-type.

AMBW-46721

Summary: When creating a top-down REST service with an OAS 3.0 JSON file having response header parameters and multiple response formats, the parameters are not reflected in the service binding.

Workaround: None

AMBW-46663

Summary: If an OAS 3.0 REST service is created using a JSON file having anyOf/oneOf keywords with one of the schema referred with "$ref" and another sub-schema as "inline", then the inline schema is not reflected in the Reply activity.

Workaround: None

AMBW-46607

Summary: If an OAS 3.0 REST service is created using a Swagger file having inline schema with "oneOf/anyOf" or nesting with "allOf", then the schema elements are not resolved in the Input tab of the Reply activity.

Workaround: None

AMBW-46002

Summary: The "allOf" tag is not reflected in the runtime Swagger JSON generated for the REST service created using an imported Swagger JSON having the "allOf" tag.

Note: The schemas are merged into a single schema object in the runtime Swagger file and this doesn't impact the functionality.

Workaround: None.

AMBW-45941

Summary: The Swagger specifications having the pattern keyword are not supported in ActiveMatrix BusinessWorks 6.x.

Workaround: You can either manually modify the Swagger specifications to remove the pattern tag before importing it in TIBCO Business Studio for BusinessWorks, or else after creating the service, you can manually modify the XSD by removing the pattern restriction for the respective element definition.

AMBW-44739

Summary: The description provided for form parameters on REST 3.0 service binding is not reflected on the reference binding as well as on top-down service binding's Form Parameters table.

Workaround: None

AMBW-44492

Summary: The 415: Unsupported Media Type error is thrown on Invoke activity of a REST Reference Binding while invoking a REST service with Request and Response formats other than JSON. That is, XML or Text.

Workaround : To get rid of the error, select JSON format in Request and Response along-with other formats.

AMBW-44479

Summary: The dynamicConfigurations WSDL part and dynamicConfigurations element aren't automapped by default for the input of Invoke activity created from the reference binding.

Workaround: Either map manually or map using the Show Check and Repair option.

AMBW-44338

Summary: On selecting Binary checkbox in Response tab of REST Service Binding, if we keep default configurations in Resource Schema then the Reply activity's response is seen as "String" instead of base64Binary.

Workaround: On selecting Binary checkbox re-select "binary" or "base64" from Resource Schema dropdown.

AMBW-44208

Summary: The java.lang.NullPointerException is thrown on adding new operation to a REST service when you change the JSON Definition Style or the Request schema from the drop-down for the newly added operation.

Workaround: If you are adding new operation then select the required schemas in the REST Service Wizard and avoid modifying it from service binding.

AMBW-44197

Summary: REST Service Binding configuration error is thrown at design time when the Resource Schema of DELETE operation is modified in the Response tab of REST Service Binding.

Workaround: If you want the DELETE operation response to be other than String then select the appropriate value in the drop-down menu for Response while creating a service using REST Service Wizard.

This workaround is not applicable for the Binary Response format.

AMBW-44116

Summary: For REST 3.0 service if you select Binary check box in Response, then at design time the Resource Schema details "$item base64Binary" is not displayed on Response tab for all operations on service binding and for POST operation on reference binding. There is no impact on anything at runtime.

Workaround: None.

AMBW-44022

Summary: The Swagger UI accessed using Lrestdoc command is not supported to show the callbacks section for the REST Operation of an ActiveMatrix BusinessWorks REST Service Endpoint created by dragging a Swagger Path whose operation is configured with callbacks.

Workaround: None.

AMBW-43156

Summary: The Swagger UI is seen as blank when the Swagger URL is hit from Internal Web Browser in TIBCO Business Studio for BusinessWorks.

Workaround: Hit the Swagger URL from an external browser.

AMBW-43023

Summary: The "format" tag is not created for "Password" type form parameter in bottom-up REST service and hence seen as String on the reference binding.

Workaround: Manually add the "format" : "password" tag to the form parameter in the swagger file.

AMBW-36113

Summary: A multipart message where one part points to type and the other part points to element and a message using mixed security mode is not supported.

Workaround: Change mixed security mode in a given WSDL.

AMBW-32951

Summary: A SOAP service responding with mustUnderstand attribute as true is ignored irrespective of selecting or deselecting the Ignore mustUnderstand check box on the SOAP Reference binding. This behavior does not affect the client and server communication.

Workaround: None

AMBW-32760

Summary: On creating SOAP Reference Binding with the concrete WSDL generated at run time with multilevel schema imports, the java.lang.NullPointerException is displayed when clicking the reference binding.

Workaround: None

AMBW-29098

Summary: When creating a concrete WSDL by right-clicking on the Service Descriptor folder, the following error is generated at design time: WSDL import error.

Workaround: None

AMBW-27870

Summary: On importing WSDL with RPC Encoded style, a validation error is generated at design time since the underlying schema with namespace http://schemas.xmlsoap.org/soap/encoding/ is not generated.

Workaround: To remove the validation error and create the SOAP Reference Binding, download the encoding schema with the said namespace and ensure that schema is a part of the application module or the shared module.

AMBW-27435

Summary: When module properties used from a shared module project were renamed, the changes made were not reflected at the SOAP binding level.

Workaround: Select the updated module property from the drop down in the SOAP binding.

AMBW-26806

Summary: When a REST service with a schema that uses a type which was imported from another XSD is invoked in a REST Reference Binding, it fails with the ServiceRuntimeException.

Workaround: None

AMBW-23104

Summary: When the WSDL uses multiple parts in the Request body of an operation, a design time validation error occurs on the generated SOAP reference binding. The application works fine at run time.

Workaround: None

AMBW-13607

Summary: REST Doc UI is not supported on Firefox browser.

Workaround: Use other browsers for the Doc UI.

AMBW-13572

Summary: For some use cases, REST Doc UI does not show the correct error code in case of Internal Server errors on the Server side.

Workaround: Check the raw message that contains the correct error code.

AMBW-13485

Summary: REST Doc UI does not support browsers like Internet Explorer.

Workaround: Use Chrome browsers for the Doc UI.

AMBW-8982

Summary: Changing the Resource name in the REST service Bindings tab, does not update the Resource Service Path.

Workaround: None