TIBCO® Cloud Integration Release Notes
Last updated:
10:53am May 10, 2017

May 09, 2017

Release Notes

What's New

Virtual Private Network (VPN) Connectivity

Organizations today are integrating to everything.  Everything includes being able to connect to applications and services hosted in private networks and datacenters.  With TIBCO Cloud Integration, this is accomplished with our Virtual Private Network capabilities.  With the VPN capability, TIBCO Cloud Integration users can connect to on-premise sources leveraging security infrastructure already in place in private networks and datacenter.  No software to install, just configure your VPN connection and go.

New and Noteworthy

TIBCO® Cloud Integration - API Modeler

  • Users can now organize API specs by putting them into different groups.
  • Users can now add the PATCH method in their API specifications using API Modeler.

TIBCO® Cloud Integration - sFTP Plugin

The TIBCO ActiveMatrix BusinessWorks™ Plug-in for sFTP has been added to TIBCO Cloud Integration to provide secured file transfer between TIBCO Cloud Integration and cloud file providers.

TIBCO® Cloud Integration - Integration Apps

Users can now update password fields through the web user interface as well. Existing apps need to be repushed before making use of this functionality.

Deprecating Microflows™

In this release of TIBCO Cloud Integration the Microflow™ functionality will deprecated. With this we're removing the overlapping functionality with all of the 'policy steps' in the Microflow™ functionality also being available in TIBCO Mashery. To support the custom JavaScript stages we've introduced the Node.js Application Type.

Closed Issues


Known Issues


Summary: TIBCO® Cloud Integration does not support user-defined SSL parameters for their application. While TIBCO Business Studio™ - Cloud Edition does not stop you from creating an SSL Server Configuration Shared Resource, this resource, if created will be ignored during the application deployment.

Workaround: None


Summary: If the imported API specification contains a content type other than application/json or application/xml, the content type does not display.

Workaround: None


Summary: The required check-box is not added for the body parameter, therefore, you cannot use it to specify whether the body parameter is required as other parameters.

Workaround: None


Summary: If the schema type of the body parameter defined in an API specification is object, the body parameter is lost after importing the API specification.

Workaround: Manually re-add the body parameter


Summary: If the imported API specification contains unsupported attributes, such as enum, maximum, and minimum, and you export the API specification after editing the attributes, the attributes are lost.

Workaround: None


Summary: When importing an API specification in API Modeler, if the file size of the imported API specification is larger than 400 KB, the following error is returned:

The API does not exist in DB.

Workaround: None


Summary: When creating a routing stage in a Microflow application, the stage is not able to route to non-restful endpoints

Workaround: None


Summary: The Marketo plug-in uses absolute file paths in some of the activities. Due to the nature of TIBCO Cloud Integration these activities are not supported

Workaround: None


Summary: After implementing a Swagger specification that has a “basePath” element in the specification the API tester functionality does not work correctly.

Workaround: Manually remove the “basePath” element prior to implementing it in TIBCO Business Studio™ - Cloud Edition. This does not affect the API specifications created in the API Modeler in TIBCO Cloud Integration.


Summary: The JavaScript code to implement advanced mock responses is not automatically saved

Workaround: To ensure the code is not lost, save the JavaScript code prior to changing methods.


Summary: The API documentation generated from TIBCO Business Studio™ - Cloud Edition which is used to display the endpoints in the API tester will contain all endpoints that are present in the API specification used when implementing the project. The original API specification is passed along to the runtime and does not take into account any non-implemented operations.

Workaround: None


Summary: Two-way SSL Authentication is not supported when using the Salesforce Outbound Listener and the Microsoft Dynamics CRM Entity Event Source Activity. This is because you cannot add your own authentication resources (see IPAS-530).

Workaround: None


Summary: Using XML reserved characters in application properties will result in those overridden values being ignored.

Workaround: None


Summary: On Macintosh systems only: Launching TIBCO Business Studio™ - Cloud Edition by double-clicking TIBCOBusinessStudio.app intermittently fails if Java 6 is not installed on your system


1. Right-click TIBCOBusinessStudio.app and select 'Show Package Contents'

2. Run TIBCOBusinessStudio executable under Contents-> MaCOS folder


Summary: When editing a Microflow App, if you do not push the edited application, you will still be able to scale up the application, which will fail, since the updates are not pushed to the runtime yet.

Workaround: Always push any changes on a MicroFlow App before scaling


Summary: Amazon S3 plug-in does not support relative paths. Hence file type is not supported in the Put and GetObject activities

Workaround: None


Summary: Amazon S3 plug-in is not supported on Mac OS

Workaround: None


Summary: The Put activity (put bucket) throws incorrect error message when the shared resource is configured with invalid Access Key ID

Workaround: None


Summary: Using the API tester view for a Microflow Applications with a header parameter in the Open API specification will lead to error messages with an HTTP 204 status code.

Workaround: None


Summary: The resource name of an API spec is used as the basepath in the URL for REST endpoints that are generated by TIBCO Business Studio™ - Cloud Edition. This causes an inconsistency between the Mock endpoint URL and TIBCO Business Studio™ - Cloud Edition URL when a Mock application is replaced with integration application. This will also have an impact on a Microflow application created based on the Mock application that has been replaced. The Microflow application will need to be re-created based on the new integration application.

Workaround: None


Summary: Installation fails with an Ant task error when TIBCO Business Studio™- Cloud Edition is installed on top of an existing installation with the same version.

Workaround: Uninstall the old TIBCO Business Studio™ - Cloud Edition before installing the new TIBCO Business Studio™ - Cloud Edition or install the new TIBCO Business Studio™ - Cloud Edition in a new TIBCO_HOME.


Summary: The following activities in the TIBCO MDM projects are not supported for TIBCO Business Studio™ - Cloud Edition as the relative path does not work:

File type attributes

Upload Datasource activity

Text search activity

Upload and Import activity

Workaround: The recommended approach to build TIBCO MDM projects and work with these specific activities is to use TIBCO® MDM Studio.


Summary: Application properties of type ‘password’ are not editable from the TIBCO® Cloud Integration web UI.

Workaround: Update the application properties in the TIBCO Business Studio™ - Cloud Edition and push the application from there. Or using tibcli, password can be updated and application can be pushed again


Summary: Apps that have a DateTime module property do not start when deployed to the TIBCO® Cloud Integration runtime.

Workaround: None


Summary: In the TIBCO Business Studio™ design time, the Test Connection feature for Email Palette shows success even though you have selected plain port with TLS enabled and TLS Port without TLS enabled combination.

Workaround: None. Even though the design time does not throw any error, you will a failure during runtime.


Summary: When mutual authentication is enabled, SSL test connection fails in TIBCO Business StudioTM - Cloud Edition.

Workaround: None


Summary: Using the PATCH method in TIBCO® Cloud Integration – Microflow™ times out with a ‘504 bad gateway’ error.

Workaround: None


Summary: Immediately after registering an account, signing in, then creating an app for the first time, the UI to select an application type is not shown. Similarly, when clicking the API Specs tab for the first time, the page is still in the Apps tab.

Workaround: Refresh the browser. Alternatively, create another app, and the UI will be shown.


Summary: Password Properties do not work when updated inside a group.

Workaround: A password property should be moved out of group if you want to update it from the Web UI or update it in TIBCO Business Studio™ - Cloud Edition Re-push the app after moving the property.


Summary: After importing a stage file to Microflow, the Push updates button is not available.

Workaround: Refresh the browser or add a stage.


Summary: There is an issue with the 64-bit Chrome browser version 57.0.2987.133, which prevents you from entering a payload that exceeds 17 lines for a POST or PUT operation. 

Workaround: Use Chrome browser that is lower than version 57.0.2987.133, or use a different browser.


Summary: After pushing an app, the status icon of the app will still appear red.

Workaround: Refresh the page.


Summary: Moving applications from one sandbox to another is sequential. You can only move one application at any given moment of time.

Workaround: None