What?s New 

API

• Added a new API method that allows you to update the log level of a running TIBCO Flogo app. (IPAS-18406)
• Added new API methods that allow you to enable, disable, and view the status of the TIBCO Flogo Flow tester. When enabled, the Flow Tester service allows you to test Flogo apps connected to on-premise systems using the Hybrid Agent. (IPAS-18918)
• Added new API methods that allow you to enable, disable, and view the status of the TIBCO BusinessWorks execution history service. When enabled, you can view execution history on the App Details page for TIBCO BusinessWorks apps that connect to on-premise systems using the Hybrid Agent. (AMBW-43702)
• Updated the enable DB Service API method to use an internal system key, which makes the Hybrid Agent Access key parameter (tunnelKey) optional. (IPAS-19067)

Develop/TIBCO Flogo®

• Enhanced data mapper
  • The Flogo data mapper has a redesigned user interface based on a drag-and-drop experience and visual data linking. This new data linking view makes it easier to quickly see what data is mapped and where the data is going in the target datastore. 
  • You can now do conditional data mapping by using if/else conditions. The if/else statements are used to execute blocks of code based on the specified conditions.
• Enhanced Monitoring (applicable for an app executable only)
  • A new component, TIBCO Flogo® Flow State Manager, has been introduced. Use this component along with the TIBCO Flogo® Enterprise Monitoring application to collect information about the state of all executed flows of a Flogo app. The details are displayed on the TIBCO Flogo® Enterprise Monitoring dashboard.
• Connect to on-premise systems with the Flow tester
  • The Flow Tester now allows you to test apps that connect to on-premises systems by selecting the Using on-premise services check box.
• Deploy a Flogo app in Knative
  • You can now create and deploy a Flogo app as a Knative service.
• OpenTelemetry support
  • You can now capture traces from your Flogo app by using OpenTelemetry Collector and send them to observability vendor tools such as Jaeger, Zipkin, and Datadog.
• Changing Log Level of Running App Instance
  • You can now change the log level of a running app instance without restarting the app by using the GET and PUT curl commands.
• Timer trigger enhancements
  • In the Timer trigger, you can now specify the time to start the flow execution by using the Start Time field. You can select the date and time from the calendar. Alternatively, you can set an app property for the start time. When you configure an app property for the start time, you must use the RFC 3339 date and time format. 
• Auto-update of mappings when upstream activity or app property are renamed
  • When an upstream activity or app property is renamed, all the mappings are now automatically updated to use the new name of the activity or app property. 
• Additional mapper function
  • In the JSON category, a json.exists function has been introduced. This function checks whether a key exists in a specified JSON object. The key can be a JSONPath expression and the function returns true if the expression evaluates to true.
• Ability to migrate contribution models to newer versions
  • For existing apps, if a new field is introduced in the latest contribution version, the contribution is now automatically upgraded. In prior releases, you had to export and re-import the app to see the changes in the contribution.

Integrate/TIBCO BusinessWorks?

• Provision to view Execution History data on App Details page for TIBCO BusinessWorks remote apps
• Added support for EMS X Client libraries with Integrate apps deployed in TIBCO Cloud Integration. 
• Added support to remember mappings made in a smart mapping session
• Added out of the box support for TIBCO BusinessWorks? Container Edition plug-in for Apache Maven
• Added support for Java 11
• Added support for OpenTelemetry to fetch traces with any OpenTelemetry complaint service provider
• Added support of Binary Response Format for OAS 3.0 REST services and implementing callbacks in OAS 3.0
• Added the View Documentation icon for plug-ins in Plug-in Manager
• Added support for Eclipse 4.19 platform for TIBCO Business Studio for BusinessWorks
• Added support for TLS 1.3 version for HTTP, REST, SOAP, Mail, and TCP Palettes

Develop/TIBCO Flogo® Connectors

TIBCO Flogo® Connector for Apache Kafka

• The Partitioner field has been added in the Kafka Producer activity. (FGKAFKA-50)

TIBCO Flogo® Connector for Microsoft Azure Service Bus

• Custom Properties (WIAZSB-213)
• The Output Settings tab has been added in the Microsoft Azure Service BusQueueReceiver and Microsoft Azure Service Bus TopicSubscriber triggers.
• The Input Settings tab has been added in the Microsoft Azure Service Bus Publish activity.
• The Retry on Error tab has been added in the Microsoft Azure Service Bus Publish activity. (WIAZSB-195).
• The ScheduledEnqueueTimeUtc broker property has been added in the Microsoft Azure Service Bus Publish activity. (WIAZSB-214).

TIBCO Flogo® Connector for Microsoft SQL Server

• The Query Timeout field has been added in all the activities. (WIMSSS-397)
• The connector now certifies Call Procedure and Call Functions support with all the activities. (WIMSSS-401)

TIBCO Flogo® Connector for TIBCO Cloud? Messaging

• In the eFTL Message Subscriber Trigger, you can now configure an app property for the Content Matcher field to filter messages. (FGTCM-116)
• Upgraded the TIBCO Cloud? Messaging software development kit (SDK) and added the Max Pending Acks field in the TIBCO Cloud Messaging eFTL Connection dialog box. (FGTCM-117)

TIBCO Flogo® Connector for Oracle MySQL

• The connector now certifies Call Procedure and Call Functions support with all the activities. (WIMYSQ-580)

TIBCO Flogo® Connector for PostgreSQL

• The connector now certifies Call Procedure and Call Functions support with all the activities. (WIPGRS-506)

TIBCO Flogo® Connector for Salesforce.com

• OAuth 2.0 JWT Bearer Flow as an authorization type (FGASFC-274)

   

  You can now use the JWT created in Salesforce.com for authentication. It is an app property-enabled field.

•  App property Enabled for the Environment Field (FGASFC-324)

   

  The app property has been enabled for the Environment field when creating a  Salesforce connection.

 Integrate/TIBCO BusinessWorks? Plugins

TIBCO ActiveMatrix BusinessWorks? Plug-in for TIBCO FTL®

The ActiveMatrix BusinessWorks? Plug-in for TIBCO FTL® is now available in TIBCO Cloud Integration.

TIBCO ActiveMatrix BusinessWorks? Plug-in for HL7 with FHIR 

ActiveMatrix BusinessWorks? Plug-in for HL7 with FHIR users specify customized validation profiles, guidelines, maps, and other files when validating or translating HL7 data. And FHIR users specify Mapping rule and Structure Map files for FHIR Mapping Language of FHIR Transformation activity. These files can now be uploaded to TIBCO Cloud Integration as supplemental files, and can be accessed when building TIBCO Business Studio?- Cloud Edition processes involving the Plug-in.

Changes in Functionality

TIBCO Cloud? Integration

• The Connection URL field on the App Details > Environment Control > Hybrid Connectivity tab does not display for subscriptions purchased after January 2022.  To locate an access key Connection URL, refer to Using TIBCO Cloud - Proxy Agent in the online help. (IPAS-18474) https://account.cloud.tibco.com/cloud/docs/index.html#proxy-agent/using_proxy_agent.html

Develop/TIBCO Flogo^?

• Ability to specify start time in Timer trigger

   

  In the Timer trigger, you can now specify the time to start the flow execution by using the Start Time field. You can select the date and time from the calendar. Alternatively, you can set an app property for the start time. When you configure an app property for the start time, you must use the RFC 3339 date and time format. (FLOGO-8086, FLOGO-5911)

• Ability to migrate contribution models to newer versions

   

  For existing apps, if a new field is introduced in the latest contribution version, the contribution is now automatically upgraded. In prior releases, you had to export and re-import the app to see the changes in the contribution. (FLOGO-559)

Integrate / TIBCO BusinessWorks

• While doing Push to Cloud from TIBCO Business Studio? for BusinessWorks?, the progress window does not display. To enable the progress window, go to Studio > Window > Preferences > General and uncheck the "Always run in background" checkbox. (AMBW-44711)

Develop/TIBCO Flogo Connectors

TIBCO Flogo® Connector for Apache Pulsar

• The type of the JSON Web Token field has been changed from plain text to Secret. After the upgrade, if you have any pulsar connection configured with the JSON Web Token field, you see the masked value for the JSON Web Token field. (FGPUL-93)

TIBCO Flogo® Connector for TIBCO Cloud? Messaging

• The type of the Authentication Key field has been changed from plain text to Secret. After the upgrade, if you have any TIBCO Cloud Messaging eFTL connection configured, you see the masked value for the Authentication Key field. (FGTCM-119)

Migration and Compatibility

TIBCO Cloud Integration 

Whitelisting New IP Addresses

All outbound traffic from apps deployed on TIBCO Cloud Integration is routed to load-balanced NAT servers. Each region has up to six of those servers. In this release of TIBCO Cloud Integration we have added some additional IP addresses for each region.  Best practice is to whitelist both the existing and the new IP addresses for your region.  (IPAS-18839)

New IP Addresses for AWS in the US region

• 100.20.154.204
• 100.20.94.169
• 52.38.183.244

Existing IP Addresses for AWS in the US region

• 35.160.22.232
• 52.35.217.68
• 54.148.158.186

 New IP Addresses for AWS in the EU region

• 18.202.142.246
• 52.51.215.155
• 52.215.114.187

Existing IP Addresses for AWS in the EU region

• 52.18.33.150
• 52.211.120.80
• 52.213.242.236

New IP Addresses for AWS in the AU region

• 3.104.244.78
• 3.24.252.148
• 52.65.78.113

Existing IP Addresses for AWS in the AU region

• 54.79.49.140
• 52.63.136.111
• 13.54.75.2

New IP Addresses for Azure

None

Existing IP Addresses for Azure

• 40.91.78.2
• 52.149.56.186

In addition, you may need to whitelist the following DNS names to access app endpoints.

AWS US Region

• integration.cloud.tibcoapps.com
• *-integration.cloud.tibcoapps.com

AWS Europe Region

• eu-west-1.integration.cloud.tibcoapps.com
• *-integration.eu-west-1.cloud.tibcoapps.com

AWS Australia Region

• ap-southeast-2.integration.cloud.tibcoapps.com
• *-integration.ap-southeast-2.cloud.tibcoapps.com

Azure US Region

• integration.us.azure.cloud.tibcoapps.com

TIBCO Active Matrix BusinessWorks Plug-In for OSIsoft PI

After the January 2022 release of TIBCO Cloud Integration, the Plug-In for OSIsoft PI only supports PI JDBC Driver 2019. Follow the instructions in Supplementing Plug-ins and Connectors in the TIBCO Cloud Integration online help to supplement the plugin with the PI JDBC Driver 2019.  (PIBW-870)

https://integration.cloud.tibco.com/docs/index.html#tci/using/using-apps/configuring-apps/supplements.html

Note: Using the Plug-in for OSIsoft PI without the required supplement generates errors similar to one of the following errors: 

Exception occurred while processing Output for activity [JDBCQuery - Connection to https://127.0.0.1/DataAccessServer/Query failed. Error: [PI SQL DAS] Connection refused

Details: connect failed in tcp_connect()

Connection to net.tcp://127.0.0.1/DataAccessServer/Query failed. Error: NetTcp is not supported.

 or

Exception occurred while processing Output for activity [JDBCQuery - RDSAWrapper ( /opt/tibco/bwcloud/1.1/system/hotfix/shared/libRdsaWrapper64-1.5.3b.so) cannot be loaded because it could not be verified. Message: /opt/tibco/bwcloud/1.1/system/hotfix/shared/libRdsaWrapper64-1.5.3b.so (No such file or directory)] .-{ActivityName=JDBCQuery, ProcessName=pi_test.Resource_get, ModuleName=PI_test}

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

Integrate/TIBCO BusinessWorks Plug-ins

TIBCO ActiveMatrix BusinessWorks? Plug-in for EJB

• TIBCO ActiveMatrix BusinessWorks? Plug-in for EJB is deprecated as of the TIBCO® Cloud Integration January 2022 release. (BWEJ-316)

Closed Issues

TIBCO Cloud? Integration

IPAS-10430

Any TIBCO Flogo activity that requires connectivity to an on-premises service does not work in Flow Tester.

IPAS-18581

Documentation examples for configuring a Hybrid Agent via the TIBCO Cloud Command Line Interface have an incorrect command for configuring an agent without an access key.  When configuring an agent by providing specific app names, an access secret is still required for authentication. 

Automate / TIBCO Cloud Live Apps

CBPM-22671

The work item notifications > Email Template User Interface does not function correctly if Administrator is launched from the TIBCO Cloud Integration Environment & Tools page.

Develop/TIBCO Flogo

FLOGO-8648

When a user launches a TIBCO Flogo application for the first time after the January 2022 TIBCO Cloud Integration release, there is a mismatch in the app data after the app contribution auto upgrade. This mismatch generates design-time validation errors which were not there in previous releases.

This issue has been addressed by the February 14, 2022 release for any apps that have not been modified.  If you have modified any apps, contact Support for help recovering those apps manually.

FLOGO-8530

Custom errors from the implementation are not returned back to the client from the Graphql trigger.

FLOGO-8519

The documentation of the InvokeRESTService activity is updated to include the following note:

If the content type is other than the types application/json, application/xml, or text/plain, it is converted into Base64-encoded values. You can use the utils.decodeBase64 function to get the actual values. This is applicable when Configure Response Codes is set to True or False.

FLOGO-8448

The eBay oAuth flow does not work with grant type "Authorization Code". To fix this, whenever the grant type 'Authorization Code' is used to get the access token,  'Authorization Header' is now set in the request.

FLOGO-8438

When configuring the HTTP Client Auth connector for the TIBCO Cloud service account using client credentials, an "invalid credentials" error was returned.

FLOGO-8203

The Client Authentication type 'Header' does not work for the grant type 'Client Credentials'. 

FLOGO-8191, FLOGO-8140

For a large response payload, the response time is significantly higher for a REST trigger when configured with a STRING data type.

FLOGO-8189, FLOGO-8190, FLOGO-8123

In the InvokeRestService activity, if the request type is set to form-urlencoded and the input payload contains spaces, the activity does not render the output correctly. 

FLOGO-8176

The "Using the Loop Feature in an Activity" section of the documentation is updated to include the following note:

"Keep in mind that the index for the Repeat while true iteration begins at zero and iterates n+1 times. If you enter 4 as the iterator value, it executes as the following iterations: 0,1,2,3,4.?

FLOGO-8133  

The Login action under the HTTP Client Authorization Configuration fails with an ?Invalid credentials? error for the 'Client Credentials' grant type and 'Body' as 'Client Authentication'. 

FLOGO-8125

Images in the "Creating Your First REST API" section of the documentation are updated.

FLOGO-8036

When you import an app, the process takes a long time if the TIBCO Cloud Mesh service invoked by the InvokeRESTService activity is not available in the TIBCO Cloud Integration environment.

FLOGO-7968

If you have defined the multipart form data field as filecontent but provide a string in the input, multipart form data is returned as a string instead of a file.

FLOGO-7936

A manually-typed array is not supported in a ternary expression. As a workaround, you can use the new If/Else feature.

FLOGO-7810

When the ReplyToTrigger activity is used in a flow, the following warning related to the Return activity is incorrectly displayed: Flow output is defined but not configured. To set flow output, add Return activity from Default category.

FLOGO-7967

If you have defined a filecontent type as a multipart form data field, you cannot provide a filename as input.

FLOGO-7600

For Project Flogo extensions, the configuration user interface is disoriented after clicking the Discard button and requires a browser refresh. If you click the Discard button, the user interface for FIELDS is transformed to basic type inputs (input=text).

FLOGO-7523

Users that are not the owner of the app cannot export the app.

FLOGO-7572

When you upload a contribution with a Default category (display.category set to Default), an error message is not displayed.

FLOGO-7491

The REST trigger settings user interface hangs when an app is created from an Open API 3.0 spec with an Object type in multipart/form-data request.

FLOGO-7411

Overriding app property names with (secs) for the deployed Lambda functions from the command line is not supported.

FLOGO-6950

If an app is created with the app property type as password and double quotes are used in the value of the password, the app fails. 

FLOGO-6031 

In the InvokeRestService activity, the application level schema toggle is displayed for plain/text and other type request and response.

FLOGO-4324

For a JSON tag that does not have any value, Null is displayed in the output. As a workaround, you can use the new If/Else feature and add the "isdefined(xxxx)" condition. 

*FLOGO-3305

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

FLOGO-2844

If you change the input or output schema in a subflow, it does not give any warning or error in mapping in the call flow activity.

Develop / TIBCO Flogo Connectors

TIBCO Flogo® Connector for Amazon S3

FGAZS3-103

Multiple user-defined metadata tags not handled.

TIBCO Flogo® Connector for Apache Kafka

FGKAFKA-50

The Kafka Producer does not consider the value of the partition field that is set on the Input tab.

TIBCO Flogo® Connector for Docusign

FGDUSN-20

DocusignCreateEnvelope activity forms an incorrect request body when the access token has expired.

TIBCO Flogo® Connector for Google Docs

WIGDOC-77

GoogleDocCreate and GoogleDocGet activities in TIBCO Flogo® do not provide webContentLink and webViewLink in the activity output.

TIBCO Flogo® Connector for Microsoft Azure Service Bus

WIAZSB-233

Users who have only Queue or Topic level access are getting a connection authentication error which is resolved as we have enhanced the connection that connects to a single service bus Topic or Queue.

TIBCO Flogo® Connector for TIBCO Cloud? Messaging

FGTCM-128

You can now push an app with a large TIBCO Cloud Messaging JSON web token as a key.

Integrate/TIBCO BusinessWorks Plug-ins

TIBCO ActiveMatrix BusinessWorks? Plug-in for Amazon SQS and SNS

AWSM-497

When using the Receive activity, an error is displayed when confirming the SQS Event with ActiveMatrix BusinessWorks? Plug-in for Amazon SQS and SNS 6.5.0.

AWSM-504

When using the GetQueueMessage activity, an error is displayed when confirming the SQS Event with ActiveMatrix BusinessWorks? Plug-in for Amazon SQS and SNS 6.5.0.

AWSM-515

The message payload is printed at the INFO level.

TIBCO ActiveMatrix BusinessWorks? Plug-in for Salesforce

ASFC-1991

An error occurs when you set a null value for a field in the complex body of subRequest for the Salesforce Composite activities.

ASFC-2003

The Salesforce Bulk Ingest Operation activity converts the input character < to &lt when the Row format is used to add the records.

ASFC-2039

The Salesforce connection fails when it is configured with the proxy parameters.

TIBCO ActiveMatrix BusinessWorks? Plug-in for OSIsoft PI

PIBW-845

A user is unable to run the PI plug-in application in the TIBCO Cloud Integration.

PIBW-812

JDBC query activity is not supported on the TIBCO Cloud Integration Azure environment.