TIBCO® Cloud Integration Release Notes

Last updated:
2:34pm Aug 07, 2019

TIBCO Cloud Integration will be performing a scheduled maintenance release on 13th August, 2019 at 9:00 AM PDT.  This release contains only closed issues. 

Aug 01, 2019

Release Notes

What's New

We've made a number of improvements and addressed defects. Going forward you can access "What's New" from the Guide Center in the lower right-hand corner of the screen.


The Flogo connector for Avro has been updated. We have also updated the TIBCO BusinessWorks plug-ins for Service Now, ADB, and SAP S/4HANA Cloud.

Changes in Functionality

Recent changes that were made to the following connectors require you to create new connections and reconfigure any existing applications:

- TIBCO Flogo Connector for Twilio

- TIBCO Flogo Connector for Stripe

- TIBCO Flogo Connector for Magento

Migration and Compatibility

With the deprecation of sandboxes and introduction of roles management starting in this release, sandbox-related commands in TIBCO Cloud(TM)– Command Line will result in an error. You must upgrade your TIBCO Cloud – Command Line installation in order to get the latest changes. Once you have upgraded TIBCO Cloud – CLI, run the command tibcli -h to obtain a list of valid TIBCO Cloud – CLI commands. Refer to "About Sandboxes With the TIBCO® Cloud - Command Line Interface" on the TIBCO Cloud Integration documentation page for more details on sandbox deprecation.

Deprecating and End Of Support for Development Tools

The next update of Hubspot Connector on TIBCO Cloud Integration will introduce design and schema changes for better usability purposes, this will require existing applications to be reconfigured and will also break the import of existing application JSONs.

The next update of Zuora Connector on TIBCO Cloud Integration will introduce design and schema changes for better usability purposes, this will require existing applications to be reconfigured and will also break the import of existing application JSONs.

Closed Issues


Summary: When two BW applications shared the same HTTP connector, the HTTP endpoint failed to activate using path spec "/", and the following error message was displayed: "Servlet already registered".


Summary: LiveApps failed to consume Integration (BusinessWorks) application REST endpoint.


Summary: You cannot test any activity from the following connectors in TCI Flogo Tester:




Summary: The ‘Push app’ button did not get enabled after an app was copied.


Summary: When a BusinessWorks project with an FTP get activity was used with TIBCO Cloud™ - Proxy Agent on TCI, the FTP would time out.


Summary: The app list command from the old TIBCO Cloud – CLI is no longer supported.


Summary: The command to retrieve app properties from the old TIBCO Cloud – CLI is no longer supported.


Summary: Existing apps with duplicate names could not be identified using the CLI . So, if there were multiple apps with the same name, a CLI command picked any one of the multiple apps randomly.


Summary: All existing apps with duplicate names were listed on Replace UI while trying to replace another app with one of the apps with the identical names. You were not be able to identify which app to replace since the app names were identical.


Summary: Existing promoted apps were not listed on the Replace App UI as a source app.


Summary: Existing promoted apps could not be copied from either the WebUI or CLI . Copy option would not be shown for those apps


Summary: For PostgreSQL connector, exporting an app and then importing it in a new app created in the same version did not work.

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: 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: 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: 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: Process Implementation/Process Diagram is not visible in the TIBCO Cloud™ Integration user interface, if the Integration (BusinessWorks) application process package name contains dot(.) or hyphen(-) in its name.

Workaround: Remove the dot(.) or hyphen(-) from the process package name and regenerate the ear and repush the application.


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

Workaround: None


Summary: In Web Integrator, when a RESTTrigger is created from a schema or JSON sample data containing Date and DateTime type attributes, the Date and DateTime DataTypes are shown as a string in the output tab of POST/PUT Operations and Input of ReplyToHTTPMessage Activity. Also, for the double data type, is shown as a number, and the null data type is shown as a blank icon in the mapping input tab.

Workaround: None


Summary: Only one Endpoint is shown beside the Web Integrator app name even when multiple endpoints are present inside the Web Integrator app.

Workaround: None


Summary: When a app with VPN connection is promoted to an operational sandbox , a new promoted app is created with 0 state. The VPN connection status for this promoted app is - "/0 instances connected" which is incorrect.

Workaround: Scaling up the promoted app will bring up the VPN status to normal.


Summary: Currently, the Salesforce Wave Analytics connector does not support mm/dd/yyyy (using a “/” delimiter) format in the date type.

Workaround: Use other date formats, such as mm-dd-yyyy (using a dash as the delimiter) instead.


Summary: If a record does not have any input, the Salesforce Wave Analytics connector throws "interface conversion: interface {} is nil, not map[string]interface {}exception."

Workaround: None.


Summary: If using a MongoDB connection shared resource, use a host port number between 1024-9999.

Workaround: None


Summary: If your BusinessWorks application contains a string of type Password and is more than 63 characters in length, you are unable to successfully deploy the application.

Workaround: Make sure the password has fewer than 63 characters.


Summary: When clicking a rest endpoint that invokes a service If the project for that service contains credential mapping policy, it results in an error.

Workaround: None



If the REST Service is implemented with HEAD/OPTIONS method, then from Swagger UI, it is not possible to invoke these operations.

WorkAround: None


Summary: Set to Default is not available in Environment control tab for password type app property.

Workaround: None

IPAS 8860

Summary: The endpoint URL formed in TIBCO Cloud Integration for OData service is incorrect.

Workaround: Manually edit the endpoint URL for OData in TIBCO Cloud Integration by replacing the special character "%2F" with "/"

in the URL and appending the application name and the OData resource name to the URL. For example, if the endpoint URL were  https://localdev-integration.cloud.tibcoapps.com:97/plf7pbumdgul74wsuhl3... you must edit it to https://localdev-integration.cloud.tibcoapps.com:97/plf7pbumdgul74wsuhl3...


Summary: For any TIBCO BusinessWorks plug-in that requires supplement in TCI, if the supplement was pushed prior to version upgrade of plug-in, then any subsequent application push containing that plug-in will fail.

Workaround: Re-push the respective supplements for the plug-ins used in the application.


Summary: If you promote the concatenated module property, its value gets assigned to null in the manifest.json file.

Workaround: You can use concatenated module properties at TIBCO Cloud Integration runtime without promoting those properties from TIBCO Business Studio™ for BusinessWorks™.IPAS-10016

Summary: When you open a Mock app not owned by you, and proceed into the "Advanced Mock Response" page, you are still able to edit the response code and the "Update Mock App" button is still enabled, even though nothing happens when you click the button.

Workaround: None


Summary: After renaming the app, the new name is not reflected on API Tester.

Workaround: Repush the app


Summary: Flow limit values cannot be overridden using the 'BW_APPLICATION_JOB_FLOWLIMIT' property under the 'Engine Variables' tab.

Workaround: Specify the flow limit property in the 'CUSTOM_ENGINE_PROPERTY' under the 'Engine Variables' tab, for example :



Summary: When an application with default values for promoted properties for profile is pushed to TCI , the app does not fails to run resulting in a numberformat exception.

Workaround: None


Summary: If you update the engine variables after pushing a BusinessWorks app and re-push the app from tibcli without the -r option, the engine variables do not get updated after the re-push. The same issue is present when re-pushing the app from the TIBCO Business Studio™ for BusinessWorks™ as well as the Web UI.

Workaround: None


Summary: After pushing a BusinessWorks app if you update one of the properties by overriding it, then delete the overridden property from TIBCO Business Studio™ for BusinessWorks™ and generate a new EAR and manifest file, when repushing the app from tibcli with a -r option it will result in an error.

Workaround: Set the override to default then re-push the app. Doing so will delete the updated app property from TIBCO Cloud Integration.


Summary: When invoking the supplement command, be sure not to put all the artifacts (EAR file, application manifest file and the supplement files) in the same directory. When the supplement gesture is made, TIBCO Cloud CLI automatically creates a manifest file which it deletes once the action is completed, hence resulting in two manifest files in the same folder. TIBCO Cloud CLI cannot differentiate between the two manifest files causing both files to be deleted.

Workaround: Create a separate folder for the supplemented files and run the supplement command from that directory.


Summary: A Kafka application connecting to a non Kerberos Kafka server must be supplemented with an empty krb5.conf file.

Workaround: None.


Summary: In the TIBCO Flogo Connector for Amazon S3, in the Update activity for ACL Update Type, if ACL value is provided in the input tab, a runtime error is thrown.

Workaround: None


Summary: if an app property is configured for the port field  in REST and GraphQL triggers, the app push will fail.

Workaround: Do not use an app property to configure the REST and GraphQL port numbers.


Summary: Apps that use the OSS REST trigger or REST Invoke activity do not work in the Flow tester or with binary.

Workaround: Add a value to "timeout" under REST Invoke tasks.


Summary: You run into an error after an old application JSON file is imported if it uses the default REST Invoke activity.

Workaround: Import the application and delete existing default REST Invoke activity and add new REST Invoke activity from the Default category.


Summary: External upload of Project Flogo GraphQL trigger is not supported.

Workaround: Use Out-of-the-box GraphQL trigger.


Summary: After importing an app in a new application, the field values of the Settings tab are not retained.

Workaround: Re-authenticate Azure Connection and re-configure the Settings tab field values.


Summary: When a message that is published to a topic or a queue in the service bus has the 'TimeToLive' broker property set, Microsoft Azure Service Bus Queue Receiver and Microsoft Azure Service Bus Topic Subscriber triggers are not able to process and display its value in the outpu

Workaround: None.


Summary: The following sections specify the grammar supported by Flogo DB Service 2.0.1 for

SQL SELECT, INSERT and DELETE statements. The grammar follows the standard normative form as described in PostgresSQL documentation available on the web. As such, this document does not go at lengths describing parameters and their elements constituting each clause in the grammar, instead it assumes familiarity and understanding of these constructs from the user. Nevertheless, the user may consult PostgreSQL documentation on the Web for detailed description if they so may desire.

SQL Statement

The following grammar is supported for SQL SELECT queries:

[ WITH with_query [, ...] ]


[ * | expression [ [ AS ] output_name ] [, ...] ]

[ FROM from_item [, ...] ]

[ WHERE condition ]

[ GROUP BY grouping_element [, ...] ]

[ { UNION | INTERSECT | EXCEPT } [ ALL ] select ]

[ ORDER BY expression [ USING operator ] ] [, ...] ] table_name ]

In general the following clauses/parameters are not supported:


[ HAVING condition ]

{ RANGE | ROWS | GROUPS } frame_start [ frame_exclusion ]

{ RANGE | ROWS | GROUPS } BETWEEN frame_start AND frame_end [ frame_exclusion ]


FIRST | LAST } ] ]

[ LIMIT { count | ALL } ]

[ OFFSET start [ ROW | ROWS ] ]

[ FETCH { FIRST | NEXT } [ count ] { ROW | ROWS } ONLY ]



INSERT Statement

The following grammar is supported for SQL INSERT statement

INSERT INTO table_name [ ( column_name [, ...] ) ]

{ VALUES ( { expression } [, ...] ) [, ...] | query }

[ RETURNING * | output_expression ]

In general the following clauses/parameters are not supported:

[ WITH [ RECURSIVE ] with_query [, ...] ]



[ ON CONFLICT [ conflict_target ] conflict_action ]

[ [ [ AS ] output_name ] ]

DELETE Statement

The following grammar is supported for SQL DELETE statement:

DELETE FROM table_name [ * ]

[ USING using_list ]

[ WHERE condition ]

[ RETURNING * | output_expression ]

In general the following clauses/parameters are not supported:

[ WITH [ RECURSIVE ] with_query [, ...] ]

[ ONLY ] [ [ AS ] alias ]

[ WHERE CURRENT OF cursor_name ]

[ [ [ AS ] output_name ] [, ...] ]

SQL Functions

All DB Connectors

Following SQL functions are currently not supported:


Workaround: None


Summary: When a query has more than one parameter or when parameters are used in the middle of a query statement, you see a "Query parsing failure" error. For example,

SELECT FirstName, Salary FROM employees WHERE Salary > 2000 and Title = ?Title and BirthDate > ?B and HireDate > ?H;

You get an error saying query parsing failed: evaluation failed: WHERE clause: column not found: and Birth

Workaround: Use single character parameters, for example,

SELECT FirstName, Salary FROM employees WHERE Salary > 2000 and Title = ?T and BirthDate > ?B and HireDate > ?H;


Summary: When using an Insert statement with explicitly specified column names, if the column names are of mixed case, you get the following error:  

query parsing failed: evaluation failed: column not found in table:<field>  

Workaround: Either rename the columns to all lowercase letters, or restructure the query such that the column names are not specified.


Summary: The Iterator feature is currently not supported in TIBCO Flogo(R)  Connector for Jira.

Workaround: None


Summary: Attachments for TIBCO Flogo(R)  Connector for JIRA do not work.

Workaround: None


Summary: The connection dialog hangs if a non-existent host is used in the base URL for Magento.

Workaround: Refresh the page in your browser.


Summary: The Web UI does not throw a validation error and remains on the connection screen when you click on the Test button if the Magento Base URL or Access Token you entered is invalid.

Workaround: Re-enter the correct Magento Base URL and Access Token and click the Test button again.


Summary: If the SQL query begins and ends with double quotes, query fields are not populated.

Workaround: Make sure the query ends with semicolon. Remove the double quotes and refresh the page. The fields will now get populated.


Summary: Icons for DB connection created for older apps do not load up properly after an upgrade. There is no impact on the runtime functionality of applications using the connection.

Workaround: None


Summary: The mapper fails to resolve the function name on the output for the activity.

Workaround: Use an alias for functions with arguments, for example, select count(*) as newcount from <tablename>; 


Summary: When a query has more than one parameter or when parameters are used in the middle of a query statement, you get a "Query parsing failure" error. For example, in the following query,

SELECT FirstName, Salary FROM employees WHERE Salary > 2000 and Title = ?Title and BirthDate > ?B and HireDate > ?H;

you get the following error:

query parsing failed: evaluation failed: WHERE clause: column not found: and Birth

Workaround: Use single character parameters, for example, SELECT FirstName, Salary FROM employees WHERE Salary > 2000 and Title = ?T and BirthDate > ?B and HireDate > ?H;


Summary: When inserting into a PostgreSQL table if you do not put extra spaces before the VALUES clause, you get a runtime error. For example,

'insert into tempstudent VALUES (?id, ?name, ?dept_name,?tot_cred);'

Workaround: Add an extra space before the VALUES clause like this:

'insert into tempstudent   VALUES (?id, ?name, ?dept_name,?tot_cred);'

Notice the space between tempstudent and VALUES.


Create Prospects with custom fields is not supported.


Summary: When using SAP S/4HANA Cloud connector, activities are not automatically assigned unique activity names when being added to a flow.

Workaround: Manually change the activity name after adding the activity to the

flow to make it unique.


Summary: Authentication using OAuth does not work for TIBCO Flogo Connector for SAP Cloud for Customer.

Workaround: None


Summary: An application containing TIBCO Flogo for SAP SuccessFactors activities exported from Flogo Enterprise cannot be imported to TIBCO Cloud Integration.

Workaround: Configure TIBCO Flogo for SAP SuccessFactors activities directly in TIBCO Cloud for Integration.


Summary: Solr connection icons created for older apps do not load up properly. But there is no impact in the runtime functionality of the applications using the connection.

Workaround: None


Summary: Applications with Zoho connections created in 1.0.1 or earlier versions do not work when you import them in the version 1.1.0.

Workaround: After importing applications, create a new connection on 1.1.0 and use that connection in the application.