TIBCO Cloud? Integration V3.2.0.0 August 26, 2021 Release

TIBCO Cloud Integration V3.2.0.1 September 22, 2021 Release

New and Noteworthy

There are no new features in this release.

Closed Issues

FLOGO-8123

For TIBCO Flogo, the InvokeRestService activity with the request type set to form-urlencoded does not render the output correctly if the input payload contains whitespaces.

FLOGO-8133

For TIBCO Flogo, the login action under HTTP Client Authorization Configuration fails with an Invalid credentials error for the 'Client Credentials' grant type and 'Body' as 'Client Authentication'.

FLOGO-8140

For TIBCO Flogo a large response payload, the response time is significantly higher for the REST trigger when configured with string datatype.

Deprecating and End Of Support for Development 

IPAS-15461

Limited messaging support was provided as part of the TIBCO Cloud Integration - Integrate capability prior to the availability of TIBCO Cloud Messaging as a first-class, full-scale messaging service.

With the availability of the suite of messaging options as part of TIBCO Cloud Messaging, we will be deprecating and retiring the legacy and limited messaging Cloud FTL palette offered as part of TIBCO Cloud Integration by the next release.

We recommend evaluating the extensive set of messaging options now available as part of TIBCO Cloud Messaging (https://www.tibco.com/products/tibco-cloud-messaging) and the corresponding Plug-in for TIBCO eFTL? (https://integration.cloud.tibco.com/docs/index.html#tci/connectors/eftl/index.html).

What?s New 

TIBCO Cloud? Integration

• We have added support for using OAuth tokens instead of user credentials when logging into the TIBCO® Cloud - Command Line Interface (CLI) or the TIBCO Cloud? Integration - Hybrid Agent. Note that to use the new authorize command with an OAuth Token you must download the latest version of the TIBCO® Cloud - Command Line Interface (CLI) or the TIBCO Cloud? Integration - Hybrid Agent. (IPAS-12042)
• The Apps list can now be filtered by App Status either from the filter panel on the left side of the page or from the statuses displayed in the Dashboard at the top of the page. Note that TIBCO Cloud? Live Apps and TIBCO Cloud Integration - Connect apps are not included in app status filters. (IPAS-12869 and IPAS-15812)
• TIBCO Cloud? Live Apps applications are displayed on the Apps list. (IPAS-17462)
• We have added an option to delete a Marketplace listing on the shortcut menu for a listing. (IPAS-16887)
• Enhanced the Hybrid Agent start agent command to include an option for enabling tunnel debug messages in the debug log. (IPAS-17759)

API

• We have added a new API in the TIBCO Cloud Integration API to upload supplements for TIBCO Flogo and TIBCO BusinessWorks apps. (IPAS-16703)
  • POST ?/v1?/subscriptions?/{subscriptionLocator}?/supplements?/{supplement}
• We have added support for attaching access keys when creating or updating an app via the TIBCO Cloud Integration API using the following method:
  • POST /v1/subscriptions/{subscriptionLocator}/apps (IPAS-16597)
• We have added support for updating variables/properties for an app by uploading a file via the TIBCO Cloud Integration API using the following method:
  • POST /v1/subscriptions/{subscriptionLocator}/apps (IPAS-16597)
• We have added support for multipart/form-data to the TIBCO Cloud Integration
  • PUT ?/v1?/subscriptions/{subscriptionLocator}/apps/{appId}/env/variables API method allowing you to upload variables from a .json, .txt, or .prop file. (IPAS-16546)
• We have added a new method to the TIBCO Cloud Integration API to return a list of Hybrid Agents and their associated status: 
  • GET /v1/subscriptions/{subscriptionLocator}/hybridAgents (IPAS-17968)
• We have added support for deleting marketplace listing via the TIBCO Cloud Integration API using the following method: (IPAS-17821)
  • DELETE /v1/subscriptions/{subscriptionLocator}/marketplace/listings/{listingId} 
• We have updated the TIBCO Cloud? Integration API rate limit to a sliding window of 20,000 calls per hour. (IPAS-17412)
• We have added new API methods to view, copy, and upload Extensions for TIBCO Flogo apps. (FLOGO-7067,  FLOGO-6689, IPAS-17253)
  • GET /v1/subscriptions/{subscriptionLocator/extensions POST ?/v1?/subscriptions/{subscriptionLocator}/extensions/copy
  • POST ?/v1?/subscriptions/{subscriptionLocator}/extensions/upload 
• We have added a new API method to encrypt Flogo app properties of type password (FLOGO-7590)
  • POST ?/v1?/utils?/encrypt
• We have added new API methods to build and download a Flogo app executable (FLOGO-7447)
  • POST ?/v1?/subscriptions?/{subscriptionLocator}?/apps?/{appId}?/flogo?/build
  • GET ?/v1?/subscriptions?/{subscriptionLocator}?/apps?/{appId}?/flogo?/build
• We have added a new API method to export a TIBCO Flogo app in JSON format: (FLOGO-5375, FLOGO-4891)
  • GET ?/v1?/subscriptions?/{subscriptionLocator}?/apps?/{appId}?/export

Develop/TIBCO Flogo

• New activities:
  • ReplyToTrigger activity: Use this activity to map output values and send a response back to the trigger without ending the execution of the flow.  (FLOGO-7608)
  • ProtobufToJSON activity: Use this activity to convert protocol buffer messages to JSON format. (FLOGO-7069)
  • No-Op activity: Use this activity to create branches in a flow without performing any other operation. (FLOGO-4459)
• New triggers: (FLOGO-4708)
  • App Startup trigger: Use this trigger to execute flows before starting the app engine.
  • App Shutdown trigger: Use this trigger to execute flows before the app engine is gracefully shut down.
• Building an app executable: You can now build an app executable from the User Interface. (FLOGO-7446)
• Support for Mutual TLS: The InvokeRESTService activity now supports mutual TLS (client certificate and client key). You can either select a certificate or configure an app property for these fields. (FLOGO-7548 and FLOGO-7354)
• Overriding an app property value in the Flow Tester: You can now override app property values in the launch configuration of the Flow Tester. To override properties defined in the app and those defined in a connection, go to Mapping settings > properties. (FLOGO-6084)
• Mapper Support on the ?Retry on Error? tab: On the Retry on Error tab of an activity, you can now map elements in the schema by using the mapper or enter values for the element in the mapper directly. 
• Deploying a Flogo App to Microsoft Azure Functions: After you have designed a Flogo app or imported an existing app, you can now deploy it to Microsoft Azure Functions. 
• Support for $loop.index in foreach array mapping: Starting from this release, you can include $loop.index in the array mapping of the foreach() method to get the current index.
• New functions: 
  • New category, URL: (FLOGO-7652)
    • url.encode
    • url.escapedPath
    • url.hostname
    • url.path
    • url.pathEscape
    • url.port
    • url.query
    • url.queryEscape
    • url.scheme
• JSON (FLOGO-7651)
  • json.get
  • json.length
  • json.ecodeNumbersToString
  • json.objKeys
  • json.objValues
  • json.set

Develop/TIBCO Flogo® Connectors

• Google Cloud SQL: The connector now provides support for 5.7 and 8.0 versions of MySQL. It also supports PostgreSQL versions 10 and 11.
• Marketo: Release Notes
• Microsoft Azure Service Bus: Release Notes 
• Microsoft SQL Server: The connector now supports: 
  • Connection TCP Timeout (WIMSSS-394)
  • App property override for certificates (WIMSSS-345)
• Oracle MySQL: The connector now supports Connection TCP Timeout.
• PostgreSQL: The connector now supports: 
  • Connection TCP Timeout (WIPGRS-500)
  • App property override for certificates (WIPGRS-449)
• Redis: Release Notes
• Salesforce.com:  Release Notes
• WebSockets: The Websocket Subscriber trigger reconnects automatically to the Websocket server in the event of a connection failure. You can specify auto reconnect attempts and auto reconnect maximum interval by using the AutoReconnectAttempts and AutoReconnectMaxDelay fields. (FGWSKT-107)

Integrate/TIBCO BusinessWorks? Plugins

• Facebook: Release Notes
• Google Cloud Storage: Release Notes
• MongoDB: Release Notes
• SAP: Release Notes
• Snowflake: Release Notes
• OData Services for SAP S/4HANA

Changes in Functionality

TIBCO Cloud? Integration

IPAS-18158

The Agents page column labeled Machine has been renamed to Agent Host to clarify that this information pertains to the computer where the agent is hosted.

IPAS-17944

The App Details Logs tab is limited to displaying a maximum of 10,000 lines and allows you to download a log file with up to 1 million lines. If your query exceeds these limits, a notification is displayed.

IPAS-15789

We have added support for testing and copying TIBCO Cloud Mesh endpoint URLs on the App Details page. Note that the URL generated in the Swagger response when testing a TIBCO Cloud Mesh endpoint cannot be used to access the endpoint outside the Swagger test page. Use the URL provided by the Copy URL button with an OAuth token.

Develop/TIBCO Flogo^?

FLOGO-7992

The handler and activity execution time logs have now been moved from an INFO level to a DEBUG Level.

FLOGO-7642

With the newly added support for form-url-encoded for the REST trigger, if the trigger is configured with an application/JSON request body type but the client sends the Content-Type as application/x-www-form-urlencoded, Flogo Enterprise converts all of the body to a key-value pair body (with the body as the key and an empty string as the value).

FLOGO-7587

For the InvokeRESTService activity, upon clicking the Validate flow button, validation errors related to the TIBCO Cloud Mesh service are now displayed.

FLOGO-5827

When designing a flow, if the flow input or output has a NULL value in the JSON data at the parent level, an error message is now displayed and the Save button is disabled.

FLOGO-5425

On the Retry on Error tab for an activity, you can now set values using the mapper.

FLOGO-5133

In the ReceiveHTTPMessage trigger and InvokeRestService service, you cannot select an app-level schema if the trigger or activity has multiple responses.

FLOGO-1518 

When you click the Delete Activity icon, a confirmation dialog box is now displayed. 

Closed Issues

TIBCO Cloud? Integration

 IPAS-18240

The TIBCO Cloud Integration login failed because TIBCO Cloud Integration could not handle characters that were not UTF-8 encoded in the user name.

IPAS-17660

The last row in a  Lookup table displays twice after deleting an entry until you refresh the browser.

IPAS-17117

If your organization has transitioned from TIBCO Scribe® Online Classic to TIBCO Cloud? Integration, you cannot grant or revoke access to your Connectors for customers using a TIBCO Scribe® Online Classic Organization.

IPAS-16844

If you replace a BusinessWorks app using the TIBCO Cloud Integration API, attempting to return instrumentation for an instance of that app using the ?GET /v1?/subscriptions?/{subscriptionLocator}?/apps?/{appId}?/instances?/{instanceId}?/monitoring?/bw?/instrumentation call, fails with an error similar to the following: Failed to get instrumentation for app instance.

IPAS-16054

If you change the agent on a TIBCO Cloud Integration - Connect app and then attempt to reprocess failed records, no error message is displayed and the records are not reprocessed. 

IPAS-15718

When using Swagger 2.0 with Endpoints, requests with repeating parameter/array parameters are not working and return a 500 internal server error.

*IPAS-13878 

When working in TIBCO Cloud Integration, if you click a link or a button that opens a dialog, such as the Flow editor or a Connection dialog, that dialog sometimes ends up behind the browser. 

Develop/TIBCO Flogo

FLOGO-7757

The InvokeRestService activity sets the Accept header as application/JSON by default.

FLOGO-7666

The value of data type BIGINT is converted to an incorrect value.

FLOGO-7648

An app pushed from the TIBCO Cloud - Command Line Interface fails if the app is developed with an extension with a visibility level (user/org) different from the level available in the User Interface while pushing it from TIBCO Cloud - Command Line Interface.

FLOGO-7587

Validation errors for updating in TIBCO Cloud Mesh service or service not available are not shown for the InvokeRestService Activity after validating the flows.

FLOGO-7544

The Discard button is activated in the OSS Invoke REST Service activity even when no changes are made. The User Interface is disoriented after clicking on the Discard button and requires a browser refresh.

FLOGO-7541

If the trigger with coercion has an individual mapping for elements, the mapping of the Return activity changes after export and import.

FLOGO-7528

If you import an app that contains double quotes (""), the value within the double quotes is not preserved in the activity and the expression becomes empty. A design-time validation error is generated.

FLOGO-7510

In the Invoke REST Service activity, when Configure Response Codes is set to True and is provided in the JSON Schema format, Response Headers are not populated in the Output.

FLOGO-7474

The array.foreach() function cannot be used as a function argument or in conditional expressions.

FLOGO-7407

When a dynamic name is used in the property value lookup, the mapper reports a validation error. For example, an error is thrown for the following property:

$property[$activity[Foo].output.name],

FLOGO-6936

In the InvokeRESTService activity, when Configure Response Codes is set to true and Response Body or Response Headers is configured with a JSON schema, response headers do not show up correctly in the output.

FLOGO-6892

If an app is in a failed state and you copy the app or change ownership of the app, the app goes into an infinite loop.

FLOGO-6720

If an extension is deleted before an app and uploaded again, the deleted app name or flow name is shown in the extension.

FLOGO-5827

Flow input or output with JSON data of NULL value is not supported.

FLOGO-4931

Multi-dimensional arrays are not supported in TIBCO Cloud Messaging.

FLOGO-4930

Anonymous arrays are not supported in TIBCO Cloud Messaging.

Integrate / TIBCO BusinessWorks

AMBW-43368

When creating a REST reference from a TIBCO BusinessWorks Cloud OAS 3.0 mesh service that contains multiple part/form-data, the following error is generated: "Problem while loading file". 

Develop / TIBCO Flogo Connectors

TIBCO Flogo® Connector for Marketo 

FGMKTO-52

The output schema that should be generated after setting up the connection and action in the settings tab and after configuring the Input mapper options, is not being generated for the Marketo Delete activity.

TIBCO Flogo® Connector for Microsoft Azure Service Bus

WIAZSB-165

When starting the app with Azure Service Bus as a trigger, the following error is seen:

"[flogo] - Failed to create engine instance due to error: error initializing trigger [AzureServiceBusQueueReceiver]: Failed to load Azure Service Bus connection configuration. Failed to load Kafaka client configuration."

This error occurs if a Kafka client is not configured in your app.

WIAZSB-138

Flogo apps that implement Azure Service Bus subscribers (on Queues or Topics/Subscriptions) suddenly and periodically stop working. The Azure Service Bus also stops reading any messages.

WIAZSB-115

The following error occurs when an attempt is made to read Azure Service Bus messages from dead-letter-queues using the Flogo® Connector for Microsoft Azure Service Bus:

AzureServiceBus-trigger-topicsubscriber] - Failed to build a new subscription named %s due to error: %sabac/$deadletterqueueerror code: 400, Details: The specified HTTP verb (GET) is not valid.

TIBCO Flogo® Connector for MySQL

WIMYSQ-546

Inserting a record with null values does not work.

TIBCO Flogo® Connector for Oracle MySQL

WIMYSQ-545

When using an IP address to create a TIBCO Cloud Integration Hybrid connection if there are connection timeout errors, retry attempts are not displayed.

TIBCO Flogo® Connector for PostgreSQL

WIPGRS-483

When using an IP address to create a TIBCO Cloud Integration Hybrid connection, if there are connection timeout errors, retry attempts are not displayed.

WIPGRS-462

When you use ENUM functions on table creates with enum as the datatype for one of its columns, the following error is generated:  "query parsing failed: no prefix parse function found for ILLEGAL" 

WIPGRS-461 

Datatype JSON is not supported. At run time the output for the JSON datatype shows as a base64 encoded value.

WIPGRS-428

At runtime the output for the XML datatype shows as a  base64-encoded value.

WIPGRS-257

Postgres values of type enum are base-64 encoded instead of the actual value being displayed.

TIBCO Flogo® Connector for SAP HANA Database

WISAHC-26

When using the Flogo Connector for SAP S/4HANA Cloud, Input options in activities are missing after API service selection.

TIBCO Flogo® Connector for SugarCRM

WISCRM-183  

When importing an older flow, the Connection and Module fields for the  ReceiveSugarCRMessage trigger are not populated by default.

TIBCO Flogo® Connector for WebSockets

FGWSKT-63

If the Websocket Client activity does not send the required query or header parameters by the Websocket Server trigger or if there is a URI mismatch between the Websocket Client activity and the Websocket Server trigger, then instead of the 400 or 404 error, the following error is displayed:

?502, cannot upgrade ws connection, websocket: bad handshake.?

Integrate/TIBCO BusinessWorks? Plugins

TIBCO ActiveMatrix BusinessWorks? Plug-in for HL7 with FHIR

HL-1156

Workflows created with TIBCO ActiveMatrix BusinessWorks Plug-in for HL7 with FHIR Version 8.0.0 FHIR activities are not compatible with Version 8.1.0.

HL-1157

When running a CDSServices workflow with the ServiceDiscovery palette activity on TIBCO ActiveMatrix BusinessWorks Plug-in for HL7 with FHIR  in  TIBCO Cloud? Integration, the associated URL must end in /cds-services/.

TIBCO ActiveMatrix BusinessWorks? Plug-in for Snowflake

BWFL-125

The Query activity fails when dealing with a NULL value from a NUMBER column.

Deprecating and End Of Support for Development

IPAS-15461

Limited messaging support was provided as part of the TIBCO Cloud Integration - Integrate capability prior to the availability of TIBCO Cloud Messaging as a first-class, full-scale messaging service.

With the availability of the suite of messaging options as part of TIBCO Cloud Messaging, we will be deprecating and retiring the legacy and limited messaging Cloud FTL palette offered as part of TIBCO Cloud Integration by the next release.

We recommend evaluating the extensive set of messaging options now available as part of TIBCO Cloud Messaging (https://www.tibco.com/products/tibco-cloud-messaging) and the corresponding Plug-in for TIBCO eFTL? (https://integration.cloud.tibco.com/docs/index.html#tci/connectors/eftl/index.html).