Integrate / TIBCO Business Studio? for BusinessWorks? Known Issues

To access release notes see: TIBCO Cloud? Integration Release Notes at https://community.tibco.com/s/article/TIBCO-Cloud-Integration-Release-Notes.

AMBW-40912

Summary: TIBCO Cloud Integration is unable to monitor the TIBCO BusinessWorks Container Edition remote apps with a hybrid agent for hybrid monitoring when those apps are running in a  Windows container.

Workaround: None.

AMBW-41151 / IPAS-12555

Summary: On the Apps list, the Set Endpoint Visibility menu option is available for apps without endpoints.

Workaround: None.

AMBW-42762

Summary: For TIBCO BusinessWorks Container Edition, the FTL plug-in is not visible for the TIBCO Cloud deployment target.

Workaround: Use Cloud FTL plug-in activities.

AMBW-43118

Summary: The TIBCO Cloud Integration API sends form parameters as a comma-separated array, causing a fault in the REST Service Binding.

Workaround: Use a Runtime swagger file, such as a top-down approach to creating the service.

AMBW-43860

Summary: When you create a client with an object data type in the input output schema and that client is used to consume a Flogo service, design time and runtime errors are generated because the object data type is not supported from the BusinessWorks client side.

Workaround: None

AMBW-45015

Summary: For MySQL, an activity with large input data is not shown in the job details on the Execution History user interface.

Workaround: None

AMBW-45146

Summary: For the Oracle database, if the data size is greater than 4000 characters, the FluentD container fails to insert the activity (input/output) data.

Workaround: Set the MAX_STRING_SIZE = EXTENDED for the Oracle database to increase the byte size capacity from 4000 (default) to 32767.

Note that this change is at the server level and it is irreversible.

BWCE-3773
Summary: When using Swagger 2.0 with Endpoints, requests with repeating parameter/array parameters do not work and  a 500 internal server error is displayed.
Workaround: Add a "collectionFormat" : "multi" attribute for array type parameters in the manifest.json file.

BWCE-6610
Summary: The  execution history scenario is not working for Oracle (Proxy mode).
Workaround: None
 

TIBCO ActiveMatrix BusinessWorks? SmartMapper

SM-2985

Summary: SmartMapper supplement is required even when the application uses SQL Server as the SmartMapper Storage Service.

Workaround: Before you push a SmartMapper application that is using SQL Server as the SmartMapper Storage Service, supplement a dummy smartmapper.zip with an empty folder.

SM-3104

Summary: New projects that use JDBC storage fail when created with TIBCO Business Studio? for BusinessWorks? version 6.9.0. 

Workaround: None.