TIBCO Flogo® Enterprise

(1)

Release Notes

Version 2.13.0 May 2021

(2)

Contents 2

New Features 6

Release 2.13.0 6

TIBCO Flogo® Enterprise Core 6

TIBCO Flogo® Connector for Websocket 7

TIBCO Flogo® Connector for Oracle MySQL 7

TIBCO Flogo® Connector for Apache Kafka 7

TIBCO Flogo® Connector for TIBCO Cloud™ Messaging 8

TIBCO Flogo® Connector for Apache Pulsar 8

Release 2.12.0 8

TIBCO Flogo® Enterprise 8

TIBCO Flogo® Connector for Oracle MySQL, TIBCO Flogo® Connector for Microsoft SQL Server, and TIBCO Flogo® Connector for PostgreSQL 10

TIBCO Flogo® Connector for Apache Pulsar 10

Release 2.11.0 10

Release 2.10.0 12

TIBCO Flogo® Connector for MQTT 14

TIBCO Flogo® Connector for Oracle MySQL, TIBCO Flogo® Connector for Microsoft SQL Server, and TIBCO Flogo® Connector for PostgreSQL 14

Release 2.9.0 14

Release 2.8.1 16

Release 2.8.0 17

Release 2.7.0 19

(3)

Release 2.6.0 21

Release 2.5.0 23

Release 2.4.0 24

Release 2.3.0 25

Release 2.2.0 26

Release 2.1.0 26

Release 2.0.0 27

Changes in Functionality 28

Release 2.13.0 28

Release 2.12.0 28

Release 2.11.0 30

Release 2.10.0 31

Release 2.9.0 31

Release 2.8.1 33

Release 2.8.0 33

Release 2.7.0 34

Release 2.6.0 35

Deprecated and Removed Features 37

Flogo Enterprise Core 37

Migration and Compatibility 41

Release 2.13.0 41

Release 2.12.0 41

Release 2.11.0 41

Release 2.10.0 41

Release 2.9.0 42

(4)

Release 2.8.1 42

Release 2.8.0 42

Release 2.7.0 42

Release 2.6.0 43

Closed Issues 44

Release 2.13.0 44

TIBCO Flogo® Connector for PostgreSQL 46

TIBCO Flogo® Connector for Microsoft SQL Server 46

TIBCO Flogo® Connector for Oracle MySQL 46

Release 2.12.0 46

Release 2.11.0 47

Release 2.10.0 49

Release 2.9.0 50

Release 2.8.1 52

Release 2.8.0 55

Release 2.7.0 56

Release 2.6.1 58

Release 2.6.0 59

Release 2.5.0 60

Release 2.4.0 60

Release 2.3.0 61

Known Issues 62

Flogo Enterprise Core 62

Database Services 75

TIBCO Flogo® Connector for Oracle Database 75

TIBCO Flogo® Connector for Apache Avro 75

TIBCO Flogo® Connector for Microsoft SQL Server 76

TIBCO Flogo® Connector for Oracle MySQL 77

(5)

TIBCO Flogo® Connector for PostgreSQL 78

TIBCO Flogo® Connector for TIBCO Cloud™ Messaging 79

TIBCO Documentation and Support Services 80

Legal and Third-Party Notices 82

(6)

New Features

The following features have been added since the last major release of TIBCO Flogo®

Enterprise.

Release 2.13.0

TIBCO Flogo® Enterprise Core

File support

ReceiveHTTPMessage REST trigger and InvokeRESTService activity now support

multipart/form-data

and

form-urlencoded

request types to handle file support.

For more information, see "REST Trigger - ReceiveHTTPMessage" and

"InvokeRESTService" in TIBCO Flogo® Enterprise Activities, Triggers, and Connections.

Move branches within a flow

You can now move branches and their respective activities from an activity to another within a flow by selecting and dragging the branch across the flow designer.

For more information, see "Moving Branches" in TIBCO Flogo® Enterprise User's Guide.

Execute Javascript activity

This release introduces a new activity, Execute JavaScript, to execute Javascript code.

For more information, see "Execute JavaScript" in TIBCO Flogo® Enterprise Activities,

Triggers, and Connections.

Application tags

You can now define custom tags for your Flogo apps. These tags are preserved even when an app is imported or exported.

For more information, see "Using App Tags" in TIBCO Flogo® Enterprise User's Guide.

Automatic generation of manifest.json file

(7)

When an app is created, the

manifest.json

file is now automatically generated in the

<FLOGO_HOME>/apps/<app>/

directory.

For more information, see "Creating an App" and "Editing an App" in TIBCO Flogo®

Enterprise User's Guide.

TIBCO Flogo® Connector for Websocket

TIBCO Flogo® Connector for Websocket is added to send and receive messages over a Websocket connection. This connector provides the following out-of-the-box activities and triggers:

^l

Websocket Server trigger

^l

Websocket Subscriber trigger

^l

Websocket Client activity

^l

Websocket Write Data activity

For more information, see the "Websocket" section in TIBCO Flogo® Enterprise Activities,

TIBCO Flogo® Connector for Oracle MySQL

Support for Overriding a Certificate Using an Environment Variable

You can override Certificate Authority (CA) Certificate, Client certificate, and Client Key by using an app property. For more information, see 'Overriding a Certificate Using an Environment Variable' section in TIBCO Flogo Connector for Oracle MySQL User’s Guide.

TIBCO Flogo® Connector for Apache Kafka

Support for Connectivity to TIBCO Cloud Messaging Service

TIBCO Flogo® Connector for Apache Kafka now supports connectivity to TIBCO Cloud Messaging service. For more information, see 'Connecting to TIBCO Cloud Messaging - Kafka' section in TIBCO Flogo® Enterprise Activities, Triggers, and Connections guide.

(8)

TIBCO Flogo® Connector for TIBCO Cloud™ Messaging

Identifying message redelivery

The MessageSubscriber trigger output provides messageId and deliveryAttempt to identify message redelivery.

TIBCO Flogo® Connector for Apache Pulsar

Support for Connectivity to TIBCO Cloud

^TM

Messaging Service

TIBCO Flogo® Connector for Apache Pulsar now supports connectivity to TIBCO Cloud Messaging service. For more information, see the "Connecting to TIBCO Cloud

Messaging – Apache Pulsar" section in the TIBCO Flogo® Enterprise Activities, Triggers,

and Connections Guide.

Release 2.12.0

TIBCO Flogo® Enterprise

Distributed tracing by using AWS X-Ray

You can use AWS X-Ray for tracing a Flogo Enterprise app running in the cloud or in your local environment. You can track how the app is performing or troubleshoot performance issues and errors.

For more information, see the "Tracing Apps Using AWS X-Ray" section in the TIBCO

Flogo® Enterprise User’s Guide.

Share data within a flow or across flows in an app

A new activity, SharedData, is now available under the General category. This activity enables you to share runtime data within a flow or across flows in an app.

For more information, see the "SharedData" section in TIBCO Flogo® Enterprise Activities,

Response headers in InvokeRESTService activity

In the InvokeRESTService activity, if the output has multiple response codes, you can

(9)

now add response headers corresponding to each response code on the Output Settings tab.

For more information, see the "InvokeRestService" section in TIBCO Flogo® Enterprise

Activities, Triggers, and Connections.

Basic Auth and OAuth 2.0 support for InvokeRESTService activity

^l

The InvokeRESTService activity now supports Basic Auth and OAuth 2.0. The following fields have been added to the InvokeRESTService activity:

^o

Enable Authentication

^o

Authentication Connection

For more information, see the "InvokeRESTService" section in TIBCO Flogo®

Enterprise Activities, Triggers, and Connections.

^l

A new connection called HTTP Client Authorization Configuration has been added to the General category, to enable authentication and authorization in

InvokeRESTService activity. For more information about the connection, see the

"HTTP Client Authorization Configuration" section in TIBCO Flogo® Enterprise

XML response handling in InvokeRESTService activity

The InvokeRESTService activity now supports

application/xml

as the response type.

For more information, see the "InvokeRESTService" section in TIBCO Flogo® Enterprise

Adding a function in an argument to the array.forEach() function

You can now add a function in the first argument of the

array.forEach()

function. For example:

array.forEach(array.slice($activity[Mapper], 1, 4), "data")

For more information, see the "Mapping Complex Arrays - Using the array.forEach()

Function" in the TIBCO Flogo® Enterprise User's Guide.

(10)

TIBCO Flogo® Connector for Oracle MySQL, TIBCO Flogo®

Connector for Microsoft SQL Server, and TIBCO Flogo®

Connector for PostgreSQL

Added support for Connection Retry mechanism in case of a connection failure (while creating a connection or executing an activity).

TIBCO Flogo® Connector for Apache Pulsar

^l

The Apache Pulsar Message Ack activity acknowledges the Pulsar messages received by the Apache Pulsar Consumer trigger.

^l

The Apache Pulsar Consumer trigger is configured to process messages in a synchronous manner by using the Sync mode and multiple messages concurrently by using the Async mode.

^l

You can use the Apache Pulsar connection to set the connection and operation timeouts.

For more information, see the TIBCO Flogo® Connector for Apache Pulsar User's Guide.

TIBCO Flogo® Connector for TIBCO Cloud™ Messaging

The Message Subscriber trigger is configured to process multiple messages concurrently.

For more information, see the TIBCO Flogo® Connector for TIBCO Cloud™ Messaging

User's Guide

Release 2.11.0

TIBCO Flogo® Enterprise

SendEmail activity

The SendEmail activity now supports:

(11)

^l

Sending file attachments

^l

Setting Reply-To configuration

For more information, see the "SendMail" section in the TIBCO Flogo® Enterprise

Activities and Triggers Guide.

Step-back flow testing

Using the enhanced Flow Tester, you can:

^l

See the flow execution and the progress made in the execution of the flow. In the new Flow Tester interface, when an activity is being executed, a blue animation is displayed around it.

^l

See errors displayed at the activity-level.

^l

Select an activity after its execution to see the inputs and outputs.

^l

Change the inputs to other valid values and start the execution of the flow from that point onwards.

For more information, see the "Flow Tester" section in the TIBCO Flogo® Enterprise

User's Guide.

Support for OpenAPI Specification

Support for OpenAPI Specification is added as follows:

^l

The ReceiveHTTPMessage trigger supports Open API Specification 3.0.

^l

The InvokeRESTService activity supports both Open API Specification 3.0 and Swagger 2.0.

For more information, see the "REST Trigger - ReceiveHTTPMessage" and

"InvokeRESTService" sections in the TIBCO Flogo® Enterprise Activities and Triggers

Guide.

App file persistence

Flogo app (JSON) files are now persisted to the directory that you specify on your local machine. This allows you to easily use an external source control system such as Git or SVN. This makes it easier for you to setup the version control for Flogo apps for

automated delivery using Continuous Integration/Continuous Deployment (CI/CD).

For more information, see the "App File Persistence" section in the TIBCO Flogo®

Enterprise User's Guide.

(12)

Missing extensions

When you import an app that contains one or more activities or triggers that are not installed in your environment, a warning is displayed in the Import App dialog but you can still import those activities and triggers. Activities and triggers with a missing extension display an error until you upload the extension.

For more information, see the "Resolving Missing Activities and Triggers" section in the

TIBCO Flogo® Enterprise User's Guide.

Apache Pulsar connectivity

TIBCO Flogo® Connector for Apache Pulsaris added to send and receive messages using publish-subscribe pattern and includes:

^l

Apache Pulsar Consumer Trigger

^l

Apache Pulsar Producer Activity

For more information, see the TIBCO Flogo® Connector for Apache Pulsar documentation.

Database connectivity

^l

For all complex queries which needed manual mode, metadata generation is significantly enhanced to use standard query parsing leading to better user experience.

^l

Secure connection support for TIBCO Flogo® Connector for Microsoft SQL Server, TIBCO Flogo® Connector for PostgreSQL, and TIBCO Flogo® Connector for Oracle MySQL is now provided.

Release 2.10.0

TIBCO Flogo® Enterprise

Enhanced monitoring

^l

Hybrid monitoring: Unified monitoring experience in TIBCO Cloud Integration is now available for monitoring Flogo applications deployed in private cloud

environments outside of TIBCO Cloud. You can see and monitor your Flogo apps

(13)

the same way as apps deployed on TIBCO Cloud using the TIBCO Cloud Integration - Hybrid Agent.

^l

Kubernetes native monitoring: Flogo Enterprise Monitoring can be run as a standalone app or in a container on Kubernetes. Once it starts on Kubernetes, it monitors Flogo apps added to the Kubernetes cluster.

App version support

The web UI displays app versions that can be modified anytime. At the creation of a new app, the default version displayed is 1.0.0.

Automatically generated HTTP response, Return activities and mapping configuration

When creating triggers and flows from an API (Swagger) specification, the app's Configure HTTP Response, Return activities, and mappings are now automatically configured.

Additional configuration for "Send email" activity

Input fields are added to the "Send email" activity to support HTML body and CC/BCC configuration.

Ability to run updated application without binary rebuild

In the CLI builder, an option is available to exclude the JSON file of the app when building the binary of an updated app to avoid creating a new app binary if you only want to make minor configuration or mapping changes in the app.

Improved Prometheus metrics

New improved Prometheus metrics related to count and execution interval for activity and flow are now available.

Mapping enhancement for loop

The output of an activity is accessible for mapping in its input for each iteration while using repeat while true loop.

That is, when using the Mapper you can use the output of an activity generated by the last iteration as an input for the next iteration. You can see this output as part of

“Upstream Output”. For example, assume you have a loop with three iterations. In

iteration zero, there is no value from that output because the activity has not run

(14)

yet, but on the next iteration you can access the output of the activity from the previous run.

TIBCO Flogo® Connector for TIBCO Cloud™ Messaging

^l

TCMMessageAck has been added to the connector with the following modes:

^o

Auto: messages are auto acknowledged as soon as they are received from the TIBCO Cloud Messaging service.

^o

Explicit: messages can be acknowledged by using new activity TCMMessageAck within the flow.

^l

The MessageSubscriber trigger now supports standard durables.

TIBCO Flogo® Connector for MQTT

Auto reconnect: The MQTT Publisher activity and MQTT Subscriber trigger reconnect automatically to the MQTTbroker in an event of a connection failure.

TIBCO Flogo® Connector for Oracle MySQL, TIBCO Flogo®

Connector for Microsoft SQL Server, and TIBCO Flogo®

Connector for PostgreSQL

There have been significant enhancements to the connection configuration for configuring maximum open connections, maximum idle connections, and maximum connection

lifetime. For more details, please check the TIBCO Flogo

^® Activities and Triggers Guide.

Release 2.9.0

Application monitoring

TIBCO Flogo® Enterprise now provides a component, TIBCO Flogo® Enterprise Monitoring , to monitor running Flogo Enterprise apps. The Flogo® Enterprise Monitoring application collects metrics of flows and triggers from all running

applications that are registered with it. In the application's Web UI, you can visualize

the metrics.

(15)

For details, see the "TIBCO Flogo® Enterprise Monitoring Application" section in the

TIBCO Flogo® Enterprise User's Guide.

App-level schemas

In a flow input or output, you can now define a schema and share it across the app. An app-level schema can be used in any flow, activity, or trigger configuration where a schema editor is provided. Types of schemas supported are JSON and Avro.

For details, see the "Application Schemas" section in the TIBCO Flogo® Enterprise User's

Guide.

Coercing of fields

In the input, output or trigger reply configuration of an OSS activity, you can now coerce a parameter to take the value from a schema that you dynamically defined during design time.

Flogo Enterprise supports coercing for parameters of the following data types:

array

,

object

,

param

, and

any

.

Currently, coercion is supported only for top-level parameters.

Validation of flows

You can now validate an app before you deploy it. To validate your app, click the Validate button on the App details page. This validates each flow and activity. If a flow or activity has an error, it displays an error or warning icon on the flow or activity.

Validation of flow is done only when you click the Validate button.

Data mapping functions

This release now includes the

DateTime

and

Array.flatten

Open Source functions.

Iteration index available for "Repeat While True" loops

If you select Repeat while true as the type of a loop in an activity, iteration index is now available for mapping.

Support for PATCH method in InvokeRESTService activity

You can now use the PATCH method in the InvokeRESTService activity.

(16)

Configure app properties from the Flow View

You can now configure app properties from the Flow View directly, instead of navigating back to the Flow list page to edit the app properties.

Flexibility to start with a trigger or a flow

With the enhancements in this release, you can create and configure a new trigger without binding it to a flow. This gives you flexibility to start with either a trigger or a flow.

Release 2.8.1

Streaming App Metrics to logs

You can now emit flow and activity metrics of a Flogo Enterprise app to logs by using two new environment variables: FLOGO_APP_METRICS_LOG_EMITTER_ENABLE and FLOGO_APP_METRICS_LOG_EMITTER_CONFIG.

Merging changes to an API specification

While creating a REST trigger, you can configure it by uploading the API specification file.

If the API specification is changed after the trigger is created, you can now merge the changes into an existing app by uploading the specification file again.

Propagating error data from subflow to main flow

You can now propagate error data from a subflow to the main flow using the Throw Error activity.

Overriding host and port in the URL for Invoke REST Service activity

You can now override the host name and port in the URL when calling a REST service using InvokeRESTService activity.

Defining common schema for a response code category in REST Invoke activity

In the InvokeRESTService activity, you can now define a single schema for a category of

response codes. For example, if you are calling a REST service which uses 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.

(17)

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). These fields allow the client to re-establish a connection with TIBCO Cloud Messaging Server if the connection is lost.

Release 2.8.0

gRPC Support

This release of Flogo Enterprise:

^l

Includes a gRPC Client activity for calling gRPC services from the Flogo Enterprise flows

^l

Simplifies implementing the gRPC services in Flogo Enterprise by adding the ability to import gRPC Protocol Buffers (.

proto

) file for generating the trigger and flows automatically.

^l

Supports header input field for GRPCActivity Avro Schema Registry for Kafka

Flogo Enterprise now supports built-in connectivity to Avro Schema Registry for Kafka Client Configuration for Serialization and Deserialization of messages published on or subscribed from Kafka topic in Avro format. Basic authentication is used to connect to the registry if the username and password are provided.

OpenTracing

In the area of Microservices Observability, Flogo Enterprise now adds native support for OpenTracing, a Cloud Native Computing Foundation (CNCF) project, that provides vendor-neutral API specification and instrumentation libraries for distributed tracing.

This release also provides built-in integration with the open source Jaeger tracing library for collecting the traces from Flogo Enterprise apps. With this new feature, you can set an environment variable

FLOGO_APP_MONITORING_OT_JAEGER

to

true

for enabling generation of OpenTracing compliant traces and spans and collection of those traces and spans using Jaeger.

Flow Design

(18)

This release of Flogo Enterprise adds the following functionality to improve the Developer Experience (DX) for designing Flogo apps using the Web UI:

^l

Selective Import: To improve the reusability of Flogo Enterprise apps a new 'Selective Import' feature has been added to the Import functionality of the Web UI. This allows you to import a Flogo Enterprise app into a new app or an existing app with the flexibility to select specific triggers, flows and connections while importing the app.

^l

Loop: This release of Flogo Enterprise adds significant improvements to the ability to iterate execution an activity. A new Loop tab has been added on activity configuration with support for two types of loops - Iterate and Repeat while true.

Iterate type allows you to specify a number of iterations and Repeat while true type allows you to specify condition to repeat the execution of activity when the condition is true. In addition, this release includes a new Accumulate option for accumulating output of the activity from each iteration into in array.

^l

Retry on Error: There is a new 'Retry on Error' tab added in the activity

configuration of InvokeRESTService and TCMMessagePublisher activities to retry the execution of these activities if it encounters a retriable error. This new tab allows you to specify the retry count and retry interval.

^l

Success with no matching condition: This new type of branch added in this Flogo Enterprise release can be used when you want to execute one or more specific activities when none of the 'Success with condition' branches meet the condition and execute.

^l

List view: A new list view is added for Flow Input & Output parameters in addition to existing JSON schema view. This view allows users to define the Flow

parameters and their types in the UI.

^l

Copy activity: Flogo Enterprise now provides an option to create a copy of an existing activity within the same flow.

^l

Branch Labels: A label is now added to a branch by default and displayed when hovered on the branch. You can also update the branch labels.

Support for Red Hat

^®

OpenShift

^®

This release of Flogo Enterprise adds certification for Red Hat OpenShift Container Platform version 4.x.

Building a Docker image from CLI

(19)

In the area of DevOps Flogo Enterprise CLI now provides an option to build a Flogo application docker image. This is useful for automating of the docker image build process.

Release 2.7.0

gRPC Support

gRPC is a modern, open source RPC framework commonly used in Microservices architecture. This release adds a new trigger for implementing gRPC services in Flogo applications.

Certification for Serverless container deployments

This release adds certification for the following managed Cloud services for Serverless container deployments:

^l

Google Cloud Run

^l

Azure Container Instances TIBCO Cloud Deployment

Flogo Enterprise Web UI now provides an option to export Flogo application

deployment artifacts for deployment to TIBCO Cloud Integration (TCI) platform. You can use the TCI CLI (tibcli) to push the Flogo application developed in Flogo Enterprise Web UI on TCI.

REST API Development

This release of Flogo Enterprise adds the following advanced capabilities for simplifying development of REST APIs using Flogo applications:

^l

A new Configure Response Codes option has been added to the

ReceiveHTTPMessage trigger and InvokeRESTService activity that allows you to add multiple HTTP response codes and define response content-type and schema for each code.

^l

A new ConfigureHTTPResponse activity has been added in this release of Flogo Enterprise. You can add this activity before a Return activity if Configure

Response Codes option is enabled on the ReceiveHTTPMessage trigger and use

the activity to select a response code and define the response to be returned for

that specific code.

(20)

^l

You can also define custom HTTP response header on the ReceiveHTTPMessage trigger.

^l

InvokeRESTService activity adds ability to configure a connection timeout and proxy URL while invoking external REST APIs from the Flogo flows.

Kafka Consumer

KafkaConsumer trigger now supports the Whitelist feature to consume messages from multiple topics. You can whitelist a group of Kafka topics for consuming messages by specifying them as a comma-separated list of topics (Topic field) or a regex pattern (Topic Whitelist field).

Web UI Improvements

^l

Flogo Enterprise Web UI now provides ability to add multiple handlers for a trigger giving you the ability to bind multiple flows to a single trigger. It also adds a new Trigger View and the ability to switch between the Flow view and the Trigger view so that you can add more than one flow for a single trigger.

^l

Errors and warnings:

^o

Flogo Enterprise Web UI now provides a better and consolidated view of validation errors and warnings.

^o

For error branches, details of the error (such as activity and type of error message) are now captured and returned in the $error variable. These details can be used by subsequent activities and the logic of the flow can be based on the type of error.

New Activities

This release adds the following two new out-of-the-box activities in Flogo Enterprise:

^l

Sleep: This activity is used to pause execution of the Flow for a specified time period.

^l

ParseJSON: This activity is used to parse JSON data in String format into a JSON Object.

Mapper Functions

^l

This release of Flogo Enterprise adds support for mapper function contributions

giving you flexibility to create custom mapper functions, install them as

(21)

extensions and use within the mapping expressions.

^l

This release of Flogo Enterprise also includes a set of mapper functions from the open source Project Flogo out-of-the-box.

^l

The

array.foreach()

function now supports passing of an argument for filtering array elements to return only the matching elements.

Extensibility

^l

Flogo Enterprise Web UI now allows users to install extensions from GitHub repositories, thus eliminating the need to zip and upload the extension.

^l

Flogo Enterprise now provides ability to plug-in custom Golang code into the application binary enabling developers to write custom code for integrating with third-party tools like monitoring agents, configuration management.

Support for AssumeRole

This release of Flogo Enterprise adds support for AssumeRole in AWS Connection configuration.

Exporting an Application's .json File

You can now export an application's

.json

file (embedded within the binary file), by using the

./<app-binary-name> --export app

command. The

.json

is exported as

<app-binary-name>.json

.

Release 2.6.1

Starting with this release Flogo Enterprise supports Spring Cloud Services. The Spring Cloud Config Server is supported for application configuration management for Flogo apps deployed on Pivotal Application Service (PAS).

This release also adds support for Kubernetes Secrets. Kubernetes Secrets object lets you manage and store sensitive information such as passwords, keys, and so on. This new feature in Flogo Enterprise allows you to resolve the values of application properties in a Flogo application deployed on Kubernetes using Kubernetes Secrets.

Release 2.6.0

GraphQL

(22)

This release of Flogo Enterprise adds an out-of-the-box trigger for GraphQL that provides an efficient and flexible API design paradigm with a powerful query language allowing frontend clients to query exact data. You can import a GraphQL schema in a Flogo application and choose to auto-generate the GraphQL trigger and flows for implementing resolver functions or add a GraphQL trigger to existing flows allowing you to rapidly implement GraphQL server for your API.

Support for OpenAPI Specification 2.0 (formerly Swagger Specification)

Using Flogo Enterprise, you can now develop REST APIs from OpenAPI Specification version 2.0 (formerly Swagger Specification). You can import the OpenAPI Specification in a Flogo application and auto-generate the REST trigger and flows for implementing the API, which in turn enables rapid development.

Improved error handling capabilities

The new Error branch type extends the flow execution control and error handling capabilities of Flogo. An Error branch allows you to catch activity level exceptions and execute a different path in the flow if activity execution throws an error. Flogo

Enterprise now supports three types of branches - Success, Success with Condition, and Error.

Mapper activity

The new Mapper activity enables you to define data mappings for any data type and construct data in the required structure for mapping to subsequent activities in the flow.

New schema synchronization option

A new Sync flow input/output configuration option is added to the Flogo Enterprise Web UI on the Trigger configuration tabs. If you make any changes in the trigger

input/output schema, this option allows you to propagate the changes to the flow input and output parameters by copying the Trigger Output schema to Flow Inputs and

Trigger Reply schema to Flow outputs without having to manually update flow input/output schema.

Additional platforms supported for containerized deployment

The PaaS or containerized deployment options have been extended to support Pivotal

Application Service (PAS) of the Pivotal Cloud Foundry (PCF) platform, Amazon ECS,

and AWS Fargate.

(23)

Support for securing APIs using TLS

Using Flogo Enterprise, you can now secure APIs built using Swagger and GraphQL through X509 certificates.

Mapper improvement

With this release, you can clear child mappings configured for objects and arrays in the mapper using a single click "Clear Mapping" option.

Release 2.5.0

AWS Lambda Triggers

This release of Flogo Enterprise takes integration with AWS Lambda to the next level by adding triggers for Amazon API Gateway and Amazon Simple Storage Service (S3). This gives you ability to develop functions in Flogo, deploy them on AWS Lambda, and invoke them from Amazon API Gateway and S3.

Prometheus Support

In the area of Application Monitoring Flogo Enterprise now provides support for Prometheus, an open source project under Cloud Native Computing Foundation (CNCF). If the environment variable FLOGO_APP_METRICS_PROMETHEUS is set to true, Flogo application starts exposing flow and activity metrics via the HTTP endpoint as Prometheus-compliant time series data. This gives you the ability to configure Prometheus for pulling and storing Flogo application metrics, use features of Prometheus for monitoring as well as alerting, and also use tools like Grafana for visualization.

Out-of-the-box support for Kafka, MQTT, TCM and Avro connectors

Starting this release, Flogo Enterprise includes a range of activities and triggers for Apache Kafka, MQTT, Apache Avro, and TIBCO Cloud Messaging out of the box removing the need to install them as separate connectors.

Duplicating Flows

With this new feature added in the Flogo Enterprise Web UI, you can now make a copy

of an existing flow within a Flogo application.

(24)

Ability to build engine from CLI

To simplify CI/CD for Flogo applications, this release adds the ability to build a single Flogo runtime engine binary with a set of required connectors. You can execute this binary to run any compatible Flogo application by passing '--app' argument to provide the application's JSON file. This removes the need to install Flogo Enterprise on build machines and build the binary for individual applications. For example, If you develop ten applications that use TIBCO Flogo Connector for Kafka and TIBCO Flogo Connector for Avro connectors, you can build a single Flogo runtime engine binary with TIBCO Flogo Connector for Kafka and TIBCO Flogo Connector for Avro connectors included in it and use the same binary to run all ten applications instead of building ten different binaries.

Support for Docker Toolbox

For developers who are using Docker Toolbox on Windows this release allows using Docker Toolbox for running Flogo Enterprise Web UI.

Release 2.4.0

Configuration Management

This release adds a set of new features to help you isolate the configuration from your application and manage it using external stores, so that you can deploy the same application in multiple environments without making any changes to the application.

Flogo Enterprise extends the Application Properties feature and allows you to provide the values for application properties at runtime using environment variables or fetching them by connecting to external configuration stores such as Consul. This release

certifies use of Consul, AWS Param Store, and Kubernetes ConfigMaps for storing your application configuration. This release also adds the ability to export application properties from the application binary in a JSON file, or as environment variables. If you use application properties for configuring secrets in your application, such as database passwords, you can now generate obfuscated values for the secrets.

Application Logging

This release adds support for the Zap library for application logging. Zap aims to provide fast, structured, and leveled logging. You can switch to the Zap logger for your application by setting the environment variable,

FLOGO_LOGGER_IMPL,

to

zap

. This

release also gives you ability to log in JSON format by setting the environment variable,

FLOGO_LOGGER_FORMAT

, to

JSON

.

(25)

Kubernetes

Flogo Enterprise now certifies deployment and management of apps using Kubernetes.

This allows you to run Flogo apps in Docker containers and use Kubernetes to manage the containers leveraging the benefits of Kubernetes including self healing, load

balancing, health check, configuration management, rollouts, and rollbacks Application Metrics API

This release provides the ability to collect flow and activity metrics for monitoring your application using a REST API. You can now enable collection of application metrics by setting the environment variable,

FLOGO_APP_METRICS

, to

true

and collecting

instrumentation as well as execution statistics for the flows and activities in your application using the REST API.

Subflows

This release adds support for creating a subflow and calling the subflow from other flows in your application. This gives you the ability to define the common logic in a subflow and reuse it in multiple flows.

Mapper Improvements

Flogo Enterprise now adds a set of new array functions to support

count

,

get

,

delete,

and

append

operations in the mapper. The use of nested ternary operators in the mapper expressions for conditions is now supported. This release also improves validation of mandatory fields and expressions in the mapper.

Note: Application binaries created prior to 2.4 must be recreated to use above features.

Release 2.3.0

Application Properties

This release introduces the concept of application properties and the ability to define,

configure (inside an application) and manage application properties. Apart from

properties provided during application design, developers can also override the value

for such properties at the time of deployment.

(26)

Runtime Statistics

In the area of monitoring and tracking your application runtime, new features have been introduced across two areas:

^l

Memory and CPU profiling data can be collected and reviewed for a given application in a test environment

^l

TIBCO Flogo® Enterprise includes the ability to gather Go runtime statistics such as memory usage, number of Go routines, logical CPUs used, version and more Healthcheck

This release introduces the ability to enable healthcheck for a Flogo application that is running.

DB Service

TIBCO Flogo Enterprise 2.3 supports a common DB Service component that facilitates database operations for database connectors.

Release 2.2.0

Flow Testing

This release introduces the ability for testing the flows created using TIBCO Flogo®

Enterprise from the design-time including creating and managing launch configurations for running these tests.

Command-Line Interface

This release provides a command-line utility capable of building a Flogo application binary.

Release 2.1.0

Improved support for building and deploying AWS Lambda functions

This release allows developers to build Flogo flows as functions in AWS Lambda and

deploy them directly from the design-time environment in to their AWS accounts.

(27)

Support for Connectors

This release introduces an installation manager and the ability to install and manage connectors for Flogo® Enterprise.

Release 2.0.0

Improved experience across installation, design, and runtime

A completely revamped user experience across installation, design-time, and runtime components has been introduced in v2.0.0 of TIBCO Flogo® Enterprise. This makes the experience better aligned for enterprise developers and consistent with the concepts available in TIBCO Flogo

^®

apps.

Cross-compatibility for Flogo Applications

Starting with this release, Flogo apps/flows created in the open-source Project Flogo™

can be imported into TIBCO Flogo® Enterprise (or TIBCO Cloud™ Integration - Flogo®).

Starting from this release, Flogo® Enterprise picks the most current stable release of the open-source Project Flogo™ and is compatible with capabilities provided in such a release.

Support for AWS Lambda Trigger

This release introduces the support for triggers for server-less frameworks and

environments such as AWS Lambda. Developers can now build Flogo flows that can be

run in AWS Lambda as functions.

(28)

Changes in Functionality

The following functionality and features have been changed in this release of Flogo Enterprise.

Release 2.13.0

TIBCO Flogo® Enterprise Core

There are no changes in functionality in this release.

Release 2.12.0

The following functionality-related changes have been made in this release.

TIBCO Flogo® Enterprise

Flow Tester

The Flow Tester engine is now built from scratch every time you start the Flow Tester. As a result, the Flow Tester takes some time to start. The time taken to start the Flow Tester depends upon the number of contributions used in the app and the resources assigned to the Docker daemon.

For more information, see the Flow Tester section in the TIBCO Flogo® Enterprise User’s

Guide.

Order in which branches are executed

When an activity has multiple branches, the order in which the branches are executed is changed to:

1. Success branch

(29)

2. Success with condition branch

3. Success with no matching condition branch

4. The Error branch gets executed as soon as the flow execution encounters an error.

5. The Main flow is run last.

The order is random if there are more than two branches which belong to same type.

For more information, refer to the Order in which branches are executed section in the

TIBCO Flogo® Enterprise User’s Guide.

Docker image generation using the -n flag

The syntax of the

-n

flag of the Builder command to generate a Docker image has changed:

-n <name>:<tag>

(or)

-name <name>:<tag>

Where

<name>

is the name of the binary file to be generated and

<tag>

is the tag to be used if a Docker image is to be created.

Note: Standalone use of

-t

or

-tag

is no longer supported.

For more information, refer to the Builder Command section in the TIBCO Flogo® Enterprise

User’s Guide.

Metadata for Oracle MySQL

When Oracle MySQL activities contain SQL statements with prepared parameters, the datatype of the prepared parameter shows up as varchar in the fields table. This change does not have a runtime impact.

Mapper validation errors

When you click on the Validate button, mapper validation errors are now displayed at the

activity level as well as flow level.

(30)

Release 2.11.0

The following functionality-related changes have been made in this release.

TIBCO Flogo® Enterprise

Metadata in database connectors

For database connectors, metadata populated in the table now displays generic datatypes.

Aggregate function in TIBCO Flogo® Connector for Microsoft SQL Server

When using the Aggregate function (

SUM

,

AVG

,

COUNT

, and so on) in a query, use an alias with the Aggregate function as follows:

^l

Replace:

^o SELECT COUNT(*) FROM BookStore;

^o SELECT AVG(BookNumber) FROM BookStore;

^l

With:

^o SELECT COUNT(*) AS alias_name <name of alias> FROM BookStore;

^o SELECT AVG(BookNumber) AS alias_name <name of alias> FROM BookStore;

Table names with spaces

If a table name contains space, change the query as follows:

^l

From:

select * from "Order Details"

^l

To:

select * from [Order Details]

Authentication key type in TIBCO Flogo® Connector for TIBCO Cloud™

Messaging

In TIBCO Flogo® Connector for TIBCO Cloud™ Messaging, the type of the Authentication

Key field has been changed from PASSWORD to STRING.

(31)

Release 2.10.0

The following functionality-related changes have been made in this release.

Automatic generation of mappings, Configure HTTP Response, and Return activites

When a Flogo app is created from a Swagger API specification, Flogo REST triggers and flows are now automatically configured with:

^l

trigger and flow input/output mappings

^l

Return and Configure HTTP Response activities, wherever applicable

Flogo Studio now called Flogo Web UI

Flogo Studio is now called Flogo Web UI. For example, this is reflected in the following areas of the product:

^l

The commands

run-studio.sh

and

run-studio.bat

are renamed to

start- webui.sh

and

start-webui.bat

respectively.

^l

Console output of the startup scripts

^l

Docker image is renamed to

flogo-webui

^l

Title of the tab in the web browser

Release 2.9.0

The following functionality-related changes have been made in this release.

Connector installation

Starting with this release, you need not install the following connectors separately:

^l

TIBCO Flogo® Connector for PostgreSQL

^l

TIBCO Flogo® Connector for Oracle MySQL

^l

TIBCO Flogo® Connector for Microsoft SQL Server

(32)

Database service installation

Starting with this release, the database service is available out-of-the-box and need not be installed separately.

Revalidating an app after navigating into a flow

After validating an app, if you navigate into a flow, you must validate the app again irrespective of whether you made changes to the flow or not. Flogo Enterprise does not retain the results of any previous validation.

Validation improvements

^l

In prior releases, flows on the flow list page were validated automatically. Now, you need to manually validate the flows.

^l

In prior releases, on editing an activity, the entire flow was validated automatically.

Now, only that particular activity is validated automatically.

Timeout field of InvokeRESTService activity

The unit of measurement for the Timeout field in the InvokeRESTService activity has been changed to milliseconds. You might want to reconfigure this field using milliseconds and deploy the app again.

Changes in user interface

The following changes have been made to the user interface:

^l

Flows list page

^o

The App Properties Button has been renamed to Properties.

^o

The Revert to last build, Import, and Export buttons have been moved into a list menu.

^l

Flow Canvas/Details page

^o

The Start testing button is renamed to Test.

^o

The Revert to last build button is removed.

^o

The Properties button has been added for specifying app properties.

(33)

^l

Buttons have been rearranged to group primary actions together and secondary actions together.

Release 2.8.1

The following functionality-related changes have been made in this release.

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

Release 2.8.0

Lambda triggers

For apps with Lambda triggers (namely ReceiveLambdaInvocation trigger, S3BucketEventLambda trigger, and AWSAPIGatewayLambda trigger):

^l

An app can have multiple flows or handlers.

^l

When a trigger is added to other flows, a validation error indicating that other triggers are not allowed in the app is displayed.

Resource name for InvokeLambdaFunction

For InvokeLambdaFunction, you can now specify the Amazon Resource Name (ARN) from

the Input tab in addition to the Settings tab. This can be used to take the ARN from a

previous activity or trigger.

(34)

Return activity

A Return activity is not added by default. Depending on your requirements, you must add the Return activity manually. The Return activity is not added by default in the following cases:

^l

Creating a flow

^l

Adding a branch

^l

Creating error handler

^l

Importing an app

Mandatory sign

In the input mapper window, for mandatory fields, the mandatory sign (*) is now displayed before the field name instead of after the field name.

Updating GraphQL schema

You can now update the GraphQL schema without generating a new Flogo flow.

Restarting Studio after installing connectors

After installing any connector, Studio must be re-started.

Release 2.7.0

JSON string in quotes

If an input string value contains a JSON string and it is not included in quotes, a validation error is returned.

Response Type in InvokeRestService

In the InvokeRestService activity, Response type has been moved from Settings to Output

Settings. The default value of Response type is

application/json

.

(35)

Note: If you set Response type to

plain/text

and export the application from 2.6.1, after upgrading to 2.7.0, you must manually change the Response type to

application/json

.

Consistent structure across functions

The structure of Flogo Enterprise and open source Project Flogo functions is now

consistent so that the open source Project Flogo functions can be used in Flogo Enterprise and vice versa.

Redesigned error panels

The error panel is no longer displayed. Errors and warnings are now displayed on the trigger, activity, and flow UI.

DEBUG logs

The default log level of the Flogo Tester is now INFO and not DEBUG.

Release 2.6.0

The following functionality-related changes have been made in this release.

Iterator Mappings

Apps created in earlier versions of Flogo Enterprise have iterator mappings using the

$current tag. Such apps return validation errors in version 2.6. You must manually update the iterator mappings for such apps.

Also, the datatype for key attribute under $current is changed from number to string. So, any mappings that involve the key attribute must also be manually updated.

Imported Applications

It is mandatory to provide a condition on branches. If the condition is not provided, the application fails at runtime.

Application Property

(36)

If you delete an application property or the property is not configured properly, the application fails to start.

Application Property Override Using Environment Variables

The environment variable used to enable application property override using

environment variables has changed from

FLOGO_APP_PROPS_RESOLVERS=env

to

FLOGO_APP_

PROPS_ENV="{}"

.

(37)

Deprecated and Removed Features

The following features have been deprecated or removed as of this release of TIBCO Flogo® Enterprise.

When relevant, useful alternatives to the deprecated features are listed. As a deprecated feature can be removed in a future release, you must plan for discontinuing the use of the feature and avoid creating new dependencies that use the deprecated feature.

Flogo Enterprise Core

The following features have been deprecated or removed as of this release of Flogo Enterprise.

Affected Component Deprecated Feature Alternative Feature Deprecated in Release Project Flogo

contributions

Deprecated contributions:

^l Receive HTTP Message ^l REST Invoke ^l Log activity

Alternative activities and triggers:

^l Receive HTTP Message

^l Invoke REST Service ^l Log Message

2.11.0

Prometheus Metrics ^l flogo_activity_

metrics ^l flogo_flow_

metrics

^l flogo_activity_

execution_count ^l flogo_activity_

execution_duration_

msec ^l flogo_flow_

execution_count ^l flogo_flow_

2.10.0 Deprecated Features

(38)

Affected Component Deprecated Feature Alternative Feature Deprecated in Release execution_duration_

msec

(39)

Affected Component Deprecated Feature Alternative Feature Deprecated in Release

Functions boolean.true() true 2.7.0

boolean.false() false

float.float64() string.float() number.int64() coerce.toInt64() number.len() string.len() string.base64ToString

()

utils.decodeBase64()

string.stringToBase64() utils.encodeBase64() string.dateFormat() YYYY-MM-DD

string.datetimeFormat ()

YYYY-MM-DDTHH:mm:ss

string.timeFormat() HH-mm-ss string.lowerCase() string.toLower() string.upperCase() string.toUpper() string.regex() string.matchRegEx() string.length string.len()

string.tostring() coerce.toString() utility.renderJSON coerce.toString() Triggered flows Use of triggered flows

is deprecated.

2.4.0

(40)

Affected Component Deprecated Feature Alternative Feature Deprecated in Release

Flogo OSS Reply (Legacy) activity

Use the Return activity in serverless flows.

2.2.0

Affected Component

Description Deprecated

in Release

Removed in

Release

Start with Trigger

option

The

Start with Trigger

option in Flogo Enterprise Web UI when creating flows has been removed.

- 2.5.0 Removed Features

(41)

Migration and Compatibility

The following information provides migration procedures and a compatibility matrix for this release of TIBCO Flogo® Enterprise.

Release 2.13.0

TIBCO Flogo® Enterprise Core

There are no migration procedures or compatibility issues in this release.

Release 2.12.0

There are no migration procedures or compatibility issues in this release.

Release 2.11.0

There are no migration procedures or compatibility issues in this release.

Release 2.10.0

HTTP Rest Trigger Mappings

Importing an app created in a prior version of Flogo Enterprise that uses a REST Trigger and is configured with an HTTP response code breaks trigger reply mappings.

To fix this issue, export the app from the latest version and import it again.

Mappings after import

For older apps, in some cases, mappings done at parent level are displayed at the

element level after import. Note that it does not have any impact at runtime.

(42)

Release 2.9.0

Zuora App

If a Zuora app is created in a prior version of Flogo Enterprise and is then imported to the current version, mapping issues are observed on the Input tab of the Zuora

Subscription Activity for the Create Subscription operation.

Export the app without making any changes and then import it again.

Release 2.8.1

There are no migration or compatibility related changes in this release.

Release 2.8.0

There are no migration or compatibility related changes in this release.

Release 2.7.0

InvokeRESTService Backward Compatibility

After an old application JSON file is imported, if it uses the open source Project Flogo REST Invoke activity, an error is encountered.

As a workaround, import the application and delete the existing open source Project Flogo REST Invoke activity. Then, add a new REST Invoke activity from the Default category.

Array Mapper Filter

When you upgrade to 2.7.0, if you use an array mapper filter for an application created in a release prior to 2.7.0, an error is displayed during design time. To fix this, delete the old mapping and remap it from the Upstream Output section. A scoping variable is now included in the mapping.

For example, if the old mapping is:

(43)

array.forEach($flow.body.Book)

After the remap, the mapping becomes:

array.forEach($flow.body.Book, "Book")

Release 2.6.0

The following migration and compatibility related changes have been made in this release.

Flogo Enterprise Web UI

In version 2.6, due to an application model change, it is recommended that you import old apps JSON in version 2.6 and export them.

CLI Tool

When the CLI tool is used to build an application created in an earlier version of Flogo Enterprise, the application binary created might not work properly in version 2.6 due to an application model change.

To avoid errors, import and export old apps in version 2.6 before using the CLI tool.

(44)

Closed Issues

The following issues have been fixed in this release of Flogo Enterprise.

Release 2.13.0

TIBCO Flogo® Enterprise Core

The following issues have been fixed in this release of TIBCO Flogo® Enterprise.

Key Summary

FLOGO-7294 Launch configurations in the Flow tester of the source app are not seen in the target app after the app is replaced from the App Details page.

FLOGO-7060 In the InvokeRESTService activity, for existing activities, you cannot see the

Output Format

field if you select

Response Type

as

application/xml

in the

Output Settings

tab. The activity fails at runtime.

FLOGO-7022 When a new element is added to the JSON (such as a new array element in the existing schema), all mappings are cleared and the mapping must be done again. The old mapping is not retained.

FLOGO-7045 After selecting an app-level schema for an OSS trigger or activity, the schema does not appear in the dialog box until you click inside the dialog box.

FLOGO-6815 If an arithmetic operator is used inside a function argument, validation errors are returned in the mapper.

FLOGO-5869 App-level schema is not available for the request or response of Plain/text and Other types because they have a non-editable