Jump to content
  • TIBCO Cloud? Integration Release Notes - February 26, 2020 Update V1.34.0

    Manoj Chaurasia

    What?s New 

    TIBCO Cloud? - Proxy Agent

    • Apps with the same access key now use the same tunnel.
    • A running Proxy Agent auto-discovers apps as they start up when they have the same access key. 
    • The new logstream command for the TIBCO Cloud Integration -  Command Line Interface  streams app logs with the TIBCO Cloud? - Proxy Agent from all apps using the same access key.

    TIBCO Flogo®

    • Emit flow and activity metrics of a Flogo app to logs using two new environment variables: FLOGO_APP_METRICS_LOG_EMITTER_ENABLE and FLOGO_APP_METRICS_LOG_EMITTER_CONFIG.
    • While creating a REST trigger, configure it by uploading the API specification file. If the API specification changes after the trigger is created, merge the changes into an existing app by uploading the specification file again.
    • Propagate error data from a subflow to the main flow using the Throw Error activity.
    • Override the host name and port in the URL when calling a REST service using the InvokeRESTService activity.
    • In the InvokeRESTService activity, define a single schema for a category of response codes.  For example, if you are calling a REST service that uses the same schema for all response codes in the range 500-599 (such as 501, 502, 503, and so on), you can define a single schema (as 5xx) for them.

    Improved TCM connection management

    • The TIBCO Cloud Messaging Connector now uses an upgraded client library for improved handling of reconnect and connection timeouts.
    • Two new fields have been added to TIBCO Cloud Messaging Connector, AutoReconnectAttempts and AutoReconnectMaxDelay (in seconds),  used by  the client to re-establish a connection with TIBCO Cloud Messaging Server if the connection is lost.

    TIBCO BusinessWorks?

    • The new Monitoring tab on the App details page allows you to monitor the process and activity instrumentation statistics of your  TIBCO BusinessWorks? Apps.
    • We are now shipping the latest stable version of EMS client JAR files with TIBCO BusinessWorks? runtime. The benefit of shipping EMS client JAR files with TIBCO BusinessWorks? is you don't need to supplement EMS JAR files. Users can still supplement EMS JAR files if necessary to maintain backward compatibility if shipped EMS jars are not backward compatible.


    The ALLOW_ENDPOINT_REDIRECT engine variable was added to enable the use of a redirect in a public endpoint for NodeJS apps.

    TIBCO Flogo® Connector Updates

    • TIBCO Flogo® Connector for Amazon S3
    • TIBCO Flogo® Connector for SugarCRM

    TIBCO BusinessWorks? Plugin Updates

    • TIBCO ActiveMatrix BusinessWorks? Plug-in for Apache Kafka
    • TIBCO ActiveMatrix BusinessWorks? Plug-in for Microsoft Dynamics CRM

    Deprecating and End Of Support for Development Tools


    TCI_BW_LOGGER_OVERRIDES and TCI_BW_CONFIG_OVERRIDES variables usage is deprecated and will be removed in a future release. Use BW_UI_LOGGER_OVERRIDES and CUSTOM_ENGINE_PROPERTY variables under Environment Controls -> Engine variable in the TIBCO Cloud? Integration User Interface to set logger and custom engine properties respectively.

    Changes in Functionality

    TIBCO Flogo®

    Explicit save for activity and trigger configuration

    If you make any changes to the schema that you entered when creating a trigger, you must save the changes explicitly by clicking Save and then propagate the changes to the flow input and flow output. If you have made changes to the schema, but do not save the changes explicitly by clicking Save, a warning message is displayed asking you to first save the changes before the schema can be synchronized.

    Closed Issues


    Users with only one subscription that attempted  to log in via the TIBCO Cloud? ? Command Line Interface using the -org and -region parameters received the following message: Error: You belong to single organization, and the login attempt was not successful.

    IPAS-11315 / IPAS-11251 

    Pushing an App via the TIBCO Cloud? ? Command Line Interface failed when using a property file with password fields.


    Attempting to push an app using the TIBCO Cloud? ? Command Line Interface where some properties for that app were exported but not promoted, generated a missing properties error. The properties that were not promoted were not packaged in the manifest.json file when the EAR was generated. 


    Clarified the information in the documentation for private endpoints under the TIBCO Cloud? Integration Changing Endpoint Visibility help topic. 

    IPAS-10123 / IPAS-10572

    The TIBCO Business Studio? for BusinessWorks? EAR file generated to push an app to the cloud had an empty manifest.json.


    The TIBCO Business Studio? for BusinessWorks? JDBC update operation used the default timeout instead of the user configured timeout. 


    For the TIBCO Cloud? Messaging service, the Content Matcher for the MessageSubscriber trigger was not saved after importing an app.


    When an app property was bound to a trigger handler configuration and that app was exported, the name of the property was lost and did not display in the design-time model after the app was imported into the Flogo Web UI, causing the app to fail at runtime. 


    The Flogo AWS Connection failed at runtime if "Use Assume Role" was set to "True".


    When output was configured for a flow, a warning message regarding the Error Handler was reported.


    At design time, when a filter expression in a mapper had multiple arguments from $loop, a wrong validation marker was displayed. 


    The Flogo AWS Connection failed at runtime if "Use Assume Role" was set to "True" and "External ID" was not configured.


    The data set in the Throw Error activity in a sub flow was not accessible to the parent flow.


    In a Microsoft Azure environment, creating a TIBCO Flogo app from a Swagger spec failed with an error similar to the following  if the specification was large, such as 1.7 MB: 

    Resource path [/{id}/status] not supported due to invalid format


    Importing apps with AWS API Gateway Lambda Trigger, Receive Lambda Invocation Trigger, or S3 Bucket Event Lambda Trigger along with other triggers in the same app did not return a validation error at design time and the app failed at runtime.


    If you changed or switched a Loop type, the configuration settings of the previous Loop type were not stored or preserved.


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

    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...