Jump to content
  • TIBCO Cloud? Integration V3.3.3.0 April 21, 2022 Release

    Manoj Chaurasia

    What?s New 

    TIBCO Cloud? Integration

    TIBCO Cloud Integration now has an updated dialog for Creating and Importing Apps! This new dialog is designed to provide users with recommendations for which Integration App types are available based on the desired use-case and subscription. The dialog also includes the following new features:

    • A list of each supported App type by use-case
    • A recommendation of the optimal App type choice by use-case
    • Importing an App (or template) from the Marketplace
    • Creating a new application by importing an exported App, Node.JS app, OpenAPI Specification, or importing a GraphQL Schema
    • Ability to remember and present your commonly used App types

    For example, if you want to build an API, you are provided a list of App types that support this use-case. The recommended App type is to import an existing API Specification from your organization and generate an App. (IPAS-19235)

    See Creating an App in the online help. 


    Develop/TIBCO Flogo®

    Improved user experience for creating and importing an app TIBCO Cloud? Integration now provides an improved and unified experience for creating and importing an app.

    Develop/TIBCO Flogo® Connectors

    TIBCO Flogo® Connector for Apache Kafka

    We have updated connectivity for the following connector:

    • Apache Kafka

    Integrate/TIBCO BusinessWorks? Plugins

    We have updated connectivity for the following plug-ins:

    • Files for Unix and Windows
    • Salesforce.com
    • Twitter

    Changes in Functionality

    TIBCO Cloud? Integration

    • When adding a new item to a Lookup table, the user's selection remains on the first row of the first page of the table. New data is not sorted until you move to a new page using the arrows at the bottom, you close and reopen the dialog, or you click the Sort icon next to the Value 1 column. Note that the Sort icon is only enabled when a new item is added and takes you to the top of the first page of the list of items. Data is sorted in binary order, for example, 1, 11, 12, 2, 20, 3. (IPAS-18188)

    Develop/TIBCO Flogo®

    • When mapped to the Return activity, Response headers are honored by the ReceiveHTTPMessage trigger. You must repush existing apps to pick up  the runtime changes.
    • Change in location of expand or collapse option in mapper


      In the mapper, the option to expand or collapse the tree has been moved from the right to the left. 

    • Handling connections while importing an app


      When importing an app, if the connection with a matching name and type existed in the environment, the Connections in the current environment drop-down is set to the existing connection by default. Prior to this release, the Connections in the current environment drop-down was set to create a new connection even if the connection used in the app existed.

    Closed Issues

    TIBCO Cloud? Integration


    In some cases, TIBCO BusinessWorks? Apps stopped while scaling or failed to start and generated an Application Container Error.


    TIBCO Cloud Integration BusinessWorks hybrid app fails to start when connecting to on-premises EMS.


    When you update the password properties of a Node.js copied app, password properties are not decrypted in the response.


    In some cases, Hybrid Agents using Hybrid Proxy connections do not log auto-discovery of remote on-premises apps and app instance ids in the associated log file.

    Develop/TIBCO Flogo®


    When opening a flow, validation takes a long time to complete.


    When using the TIBCO Flogo PATCH method in conjunction with TIBCO Cloud MESH, the InvokeRESTService activity does not retrieve the body element, preventing anything from being mapped to that element.


    For a valid running Timer trigger that has a Repeating set to True and a valid app property or calendar entry for the Start Time, if you bind an invalid app property and push the changes, you can still view or get the logs from an earlier run. The logs are executed based on conditions set in the earlier run.


    On unbinding an app schema from the request schema, the Save button is disabled.


    Newly added User Interface configurations for any activity, trigger, or connection do not reflect in the existing apps after a production refresh.

    User Feedback

    Recommended Comments

    There are no comments to display.

    Create an account or sign in to comment

    You need to be a member in order to leave a comment

    Create an account

    Sign up for a new account in our community. It's easy!

    Register a new account

    Sign in

    Already have an account? Sign in here.

    Sign In Now

  • Create New...