What?s New

TIBCO Cloud? Integration

Added two new API methods used to build a TIBCO Flogo® app executable from an application JSON file and then download that executable based on a build ID. The methods are as follows:  (IPAS-20260)

• POST /v1?/subscriptions?/{subscriptionLocator}?/app?/build?/flogo
• GET  /v1?/subscriptions?/{subscriptionLocator}?/app?/build?/flogo?/{buildId}

Added two new command options to the Hybrid Agent start command in the Command Line Interface: (IPAS-20193)

• data-chunk-size - Sets the maximum size of data for a single read-write operation. Default is 32KB
• data-ack-mode - Specifies the data ack mode. Defaults to true if not specified.

Develop / TIBCO Flogo®

• Support for AWS AppConfig  - You can now use AWS AppConfig along with a Flogo app. You can use AWS AppConfig to configure, manage, and quickly deploy Flogo app configurations.
• Support for object type as a query parameter - The InvokeRESTService activity now supports the object type as a dynamic query parameter. Only a simple JSON object type is supported.
• UI revamp of app properties - The revamped app properties User Interface provides an improved user experience while working with app properties.
• HTTP Client Authorization Connection - If you select OAuth2 as the authorization type, you can now specify a unique identifier of the audience for an issued token. The audience value is an app client ID for an ID token or the API that is being called for an access token.
• Integration with TIBCO Cloud? API Modeler - Flogo can now be used with TIBCO Cloud? API Modeler, a new version of the API Modeler. This version is an easy and powerful web-based tool that allows you to create and model APIs graphically.
• Execution History for Flogo Apps - You can now use the TIBCO Cloud? Integration Execution History service to publish, store, and retrieve execution statistics generated by Flogo apps. The execution history data is stored in an on-premises database or a database hosted on the cloud. The execution history data is displayed on the Execution History tab of the App Details page for a specific app.

Develop/TIBCO Flogo® Connectors

TIBCO Flogo® Connector for Amazon S3

TIBCO Flogo® Connector for TIBCO Cloud? Messaging

TIBCO Flogo® Connector for TIBCO® Data Virtualization - New!

TIBCO Flogo® Connector for Microsoft SQL Server

TIBCO Flogo® Connector for Salesforce

TIBCO Flogo® Connector for Stripe

Integrate/TIBCO BusinessWorks? Plugins

TIBCO ActiveMatrix BusinessWorks? Plug-in for Apache Cassandra

TIBCO ActiveMatrix BusinessWorks? Plug-in for Microsoft Dynamics CRM

TIBCO ActiveMatrix BusinessWorks? Plug-in for OSISoft Pi

TIBCO ActiveMatrix BusinessWorks? Plug-in for Snowflake

• Snowflake Bulk Load Activity (BWFL-342) - Snowflake Bulk Load is a new activity that enables the loading of mass data into Snowflake using the JDBC copy command via stage or Amazon S3.  For more information, see Snowflake Bulk Load Activity in the TIBCO ActiveMatrix BusinessWorks? Plug-in for Snowflake User's Guide. The Snowflake Bulk Load Activity provides support for data compression by default. https://au.integration.cloud.tibco.com/docs/index.html#Subsystems/bwpluginsnowflake/users-guide/the-snowflakebulkload-activity.html
• Support for New Authentication Types (BWFL-350, BWFL-354) - The Snowflake JDBC Connection shared resource now supports the following authentication types.
  • Federated authentication and SSO with Okta
  • External OAuth with Okta
  • Snowflake OAuth
• Support for Merge Operation (BWFL-464) - The Merge operation is now supported for Snowflake Insert, Snowflake Update, and Snowflake Delete activities.
• Support for Automatic Table and Column Creation for Snowflake Bulk Load and Snowflake Insert activities (BWFL-502) - The plug-in runtime now supports automatic creation of the Snowflake table if it does not exist and automatic creation of columns if it does not exist in the Snowflake table.
• Support for Table Name Module Property when using External Schema (BWFL-513) - The plug-in runtime now supports the module property for table name when an external schema is used.

Changes in Functionality

Develop / TIBCO Flogo®

• If you are entitled to TIBCO Flogo Enterprise and you would like to get access to TIBCO Cloud Integration to design your TIBCO Flogo apps, you can send a Support Request here by using a template to provide the required Cloud contact details for us to provision Cloud access. See the template here: https://community.tibco.com/s/article/Request-access-to-TIBCO-Flogo-Enterprise-on-TIBCO-Cloud-Integration
• In support of moving TIBCO Flogo Enterprise to a cloud-first design experience, entitled customers shall have access to the latest versions of TIBCO Flogo Connectors with TIBCO Cloud Integration - Develop (Flogo). No new releases will be provided on edelivery.tibco.com for the TIBCO Flogo Connectors compatible with TIBCO Flogo Enterprise Web UI. For more information, see the TIBCO Flogo Connectors and deprecation of TIBCO Flogo Enterprise Web UI article in the Support Community.  https://support.tibco.com/s/article/TIBCO-Flogo-Connectors-and-deprecation-of-TIBCO-Flogo-Enterprise-Web-UI
• SSL certificates generated using Subject Alternative Names (SAN) (FLOGO-9210) - If a client app fails due to a missing SAN field in the certificate, you must configure the certificate with a valid SAN and repush the app.
• Validation rules at design time (FLOGO-9436) - Validation rules for a string type and primitive expression at design time have changed. The validation of an expression that expects a string now allows you to return a primitive data type such as boolean and number. For example, if the following expression is used in an activity that expects a string message, an error message is not displayed for the returning number types:

TIBCO Flogo® Connector for Stripe

Integrate/TIBCO BusinessWorks? Plugins

• TIBCO ActiveMatrix BusinessWorks? Plug-in for OSISoft Pi

Closed Issues

TIBCO Cloud? Integration

TIBCO Cloud Integration - Connect App Status counts are not included in the total App Status Filter counts in the left pane of the TIBCO Cloud Integration Apps page.

IPAS-19294

Apps created by using the TIBCO Cloud Integration - Connect POST /v1/orgs/{orgId}/solutions/{solutionId}/cloneAsync API method with the byReference parameter enabled (true) share resources with the source App. Source Apps and target Apps that share resources cannot be edited. In the TIBCO Cloud Integration - Connect User Interface, you can open those Apps and the Flows they contain, but attempting to edit them generates an error and the changes cannot be saved. The User Interface currently does not block access.

IPAS-19746

The name of the TIBCO Cloud Mesh service is not getting updated in the Service registry when the app is pushed from the TIBCO Command Line Interface with a modified name.

IPAS-19521

When scheduling a TIBCO Cloud Integration - Connect app, on the User Interface the time zone defaults to the International date line west (UTC-12:00). Internally the time zone defaults to UTC, causing the app to run at the wrong time.

IPAS-18542

The Hybrid Agent system requirements documentation does not include Minimum CPU and Memory requirements. The minimum CPU is 1. The minimum Memory is 512 MB RAM. Note that CPU and RAM usage increases as the workload on the agent increases.

IPAS-18162

Occasionally, HTTP Status 504 Gateway timeout errors are generated when attempting to upload a supplement for TIBCO BusinessWorks plug-ins.

IPAS-13644

When switching between the Apps List and the App Details for an app, the app instance number displayed sometimes does not match.

Develop/TIBCO Flogo

The Flogo app that is deployed using TIBCO Cloud Integration API does not display on the User Interface because the FLOGO extension is not uploaded.

FLOGO-8041

When a Flogo app is deleted using the Delete app API, the Connection usage count is not updated.

Develop / TIBCO Flogo Connectors

TIBCO Flogo® Connector for Microsoft SQL Server

Added retry logic in case of Broken-pipe error.

TIBCO Flogo® Connector for TIBCO Cloud? Messaging

The TIBCO Cloud Messaging publisher fails to publish a message if InvokeRest activity output having an array is mapped in the message field.