TIBCO Flogo®

(1)

Release Notes

Software Release 2.8.1

February 2020

(2)

Important Information

SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDED OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR PROVIDE LIMITED ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THE EMBEDDED OR BUNDLED SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANY OTHER TIBCO SOFTWARE OR FOR ANY OTHER PURPOSE.

USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND CONDITIONS OF A LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE LICENSE AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USER LICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOAD OR INSTALLATION OF THE SOFTWARE (AND WHICH IS DUPLICATED IN THE LICENSE FILE) OR IF THERE IS NO SUCH SOFTWARE LICENSE AGREEMENT OR CLICKWRAP END USER LICENSE AGREEMENT, THE LICENSE(S) LOCATED IN THE “LICENSE” FILE(S) OF THE

SOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS AND CONDITIONS, AND YOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN AGREEMENT TO BE BOUND BY THE SAME.

ANY SOFTWARE ITEM IDENTIFIED AS THIRD PARTY LIBRARY IS AVAILABLE UNDER SEPARATE SOFTWARE LICENSE TERMS AND IS NOT PART OF A TIBCO PRODUCT. AS SUCH, THESE SOFTWARE ITEMS ARE NOT COVERED BY THE TERMS OF YOUR AGREEMENT WITH TIBCO, INCLUDING ANY TERMS CONCERNING SUPPORT, MAINTENANCE, WARRANTIES, AND INDEMNITIES. DOWNLOAD AND USE OF THESE ITEMS IS SOLELY AT YOUR OWN

DISCRETION AND SUBJECT TO THE LICENSE TERMS APPLICABLE TO THEM. BY PROCEEDING TO DOWNLOAD, INSTALL OR USE ANY OF THESE ITEMS, YOU ACKNOWLEDGE THE

FOREGOING DISTINCTIONS BETWEEN THESE ITEMS AND TIBCO PRODUCTS.

This document is subject to U.S. and international copyright laws and treaties. No part of this document may be reproduced in any form without the written authorization of TIBCO Software Inc.

TIBCO, the TIBCO logo, the TIBCO O logo, Two-Second Advantage, TIB, Information Bus, and Flogo are either registered trademarks or trademarks of TIBCO Software Inc. in the United States and/or other countries.

All other product and company names and marks mentioned in this document are the property of their respective owners and are mentioned for identification purposes only.

This software may be available on multiple operating systems. However, not all operating system platforms for a specific software version are released at the same time. Please see the readme.txt file for the availability of this software version on a specific operating system platform.

THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF

MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.

THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BE INCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. TIBCO SOFTWARE INC. MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED IN THIS DOCUMENT AT ANY TIME.

THE CONTENTS OF THIS DOCUMENT MAY BE MODIFIED AND/OR QUALIFIED, DIRECTLY OR INDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE,

INCLUDING BUT NOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES.

This and other products of TIBCO Software Inc. may be covered by registered patents. Please refer to TIBCO's Virtual Patent Marking document (https://www.tibco.com/patents) for details.

(3)

TIBCO Documentation and Support Services

How to Access TIBCO Documentation

Documentation for TIBCO products is available on the TIBCO Product Documentation website, mainly in HTML and PDF formats.

The TIBCO Product Documentation website is updated frequently and is more current than any other documentation included with the product. To access the latest documentation, visit https://

docs.tibco.com.

Documentation for TIBCO Flogo^® Enterprise is available on the TIBCO Flogo^® Enterprise Product Documentation page.

Product-Specific Documentation

The following documents for this product can be found on the TIBCO Documentation site:

● TIBCO Flogo^® Enterprise Installation

● TIBCO Flogo^® Enterprise User's Guide

● TIBCO Flogo^® Enterprise Release Notes

● TIBCO Flogo^® Activities and Triggers Guide

How to Contact TIBCO Support

You can contact TIBCO Support in the following ways:

● For an overview of TIBCO Support, visit http://www.tibco.com/services/support.

● For accessing the Support Knowledge Base and getting personalized content about products you are interested in, visit the TIBCO Support portal at https://support.tibco.com.

● For creating a Support case, you must have a valid maintenance or support contract with TIBCO.

You also need a user name and password to log in to https://support.tibco.com. If you do not have a user name, you can request one by clicking Register on the website.

How to Join TIBCO Community

TIBCO Community is the official channel for TIBCO customers, partners, and employee subject matter experts to share and access their collective experience. TIBCO Community offers access to Q&A forums, product wikis, and best practices. It also offers access to extensions, adapters, solution accelerators, and tools that extend and enable customers to gain full value from TIBCO products. In addition, users can submit and vote on feature requests from within the TIBCO Ideas Portal. For a free registration, go to https://community.tibco.com.

(5)

New Features

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

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

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:

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

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

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

(6)

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

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

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

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

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

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

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

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

● 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

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

(7)

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

● Google Cloud Run

● 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:

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

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

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

● 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

● 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 flows for a single trigger.

● Errors and warnings:

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

— 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:

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

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

Mapper Functions

(8)

● This release of Flogo Enterprise adds support for mapper function contributions giving you flexibility to create custom mapper functions, install them as extensions and use within the mapping expressions.

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

● The array.foreach() function now supports passing of an argument for filtering array elements to return only the matching elements.

Extensibility

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

● 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

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

(9)

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.

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.

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

(10)

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.

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.

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.

Runtime Statistics

(11)

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

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

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

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 Flogo^® Enterprise (or TIBCO Cloud^™ Integration - Flogo^®). Starting with this release, Flogo^® Enterprise will pick the most current stable release of the open-source Project Flogo^™ and be 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.

(12)

Changes in Functionality

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

Release 2.8.1

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

● An app can have multiple flows or handlers.

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

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:

● Creating a flow

● Adding a branch

● Creating error handler

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

(13)

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.

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

This release of Flogo Enterprise provides additional validations for application properties. 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="{}".

(14)

Deprecated and Removed Features

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

Release 2.8.1

No features have been deprecated or removed in this release.

Release 2.8.0

Release 2.7.0

The following functions have been deprecated in this release.

Deprecated Function New Function

boolean.true() true

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() Release 2.6.0

No features have been deprecated in this release.

Release 2.5.0

(15)

The ‘Start with Trigger’ option in Flogo Enterprise Web UI when creating flows has been removed in Flogo Enterprise 2.5.0 release.

Release 2.4.0

Use of triggered flow is deprecated in Flogo Enterprise 2.4.0 and the UI support for creating such flows will be removed in a future release.

Release 2.3.0

Release 2.2.0

The Flogo OSS Reply(Legacy) activity is now deprecated. Do not use this activity in your applications. Instead, use the ^Return activity in serverless flows.

(16)

Migration and Compatibility

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

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:

array.forEach($flow.body.Book)

After the remap, the mapping becomes:

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

Release 2.6.0

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.

(17)

Closed Issues

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

Release 2.8.1

Key Description

FLOGO-4582 Summary: A TCM Subscriber Content Matcher was not saved after importing the app. This has now been fixed.

FLOGO-4573 Flogo Enterprise did not handle special variables containing bracket notation, such as 'address[line1]'.

FLOGO-4489 When an app property was bound to a trigger handler configuration and the app was exported, the name of the property was lost and was not displayed in the design-time model after the app was imported into Flogo Web UI. The app failed at runtime.

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

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

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

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

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

FLOGO-4315 You could import 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. A validation error was not returned at design time and the app failed at runtime.

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

FLOGO-3910 For an app, when a child element was added as a filter to the parent array mapping, an index was not added.

FLOGO-3908 While mapping arrays, an extra element was added as a null value for missing elements in the array. For example, if the first element in an array had 3 fields and the second element had only 1 field, 2 fields were added as null for the second element.

FLOGO-389 Anonymous arrays are not supported.

You can add a root element to the array.

(18)

FLOGO-3741 If you upgraded to Flogo Enterprise 2.7.0 and then tried to build a binary for an app with a Lambda trigger, building the binary failed with an error.

FLOGO-3650 Building an app using the builder CLI resulted in an issue for an app exported before 2.6.0.

You can import the app into the latest version of Flogo Enterprise and export it again.

FLOGO-3561 Logs were not visible in Flow Tester and the following error was displayed:

Debugger failed to start as the test engine is currently being built. Please try again after sometime. For more information check builder.log.

FLOGO-3520 For the InvokeRestService activity, if you selected Response type as ^text/

plain or ^Other in the Output settings tab, the Response schema was not refreshed.

FLOGO-3375 On re-importing an app, single quotes were replaced by double quotes in a JSON string field.

FLOGO-2676 On Linux platforms, the Flogo Enterprise Web UI was not launched after connecting to VPN.

You can disconnect the VPN and re-launch or refresh the Flogo Enterprise Web UI.

FLOGO-2451 After importing a Flogo app, an extra return activity was added if the flow had no return activity.

FLOGO-1684 When accessing the Flogo Enterprise Web UI, a "502 Bad Gateway" error was returned if the machine was configured with a static IP address.

You can configure your machine IP address as dynamic.

Release 2.8.0

FLOGO-4322,

FLOGO-4298 You could not filter an array based on a condition on the child element of the object in that array.

FLOGO-4262 When ternary operators were used with the array.count() function an error was displayed at design time.

FLOGO-4161 False validation errors were reported in case of nested array fields mapping from different sources.

FLOGO-4129 You could not throw the error caught in a subflow to the main flow and stop the execution of main flow when an error occurs.

(19)

FLOGO-4056 When the URL of a big-sized Github repo (which did not have the expected structure of extensions) was provided to extensions downloaded from Github, a new app could not be created.

FLOGO-3912 For a child array filter mapping, when only a parent element was used in the filter expression, activities and flow showed a false validation error. Even if the activities show a red mark on the UI, the required results were shown at runtime. You can ignore the red marks.

FLOGO-3878 If a Flogo app had a RESTInvoke activity which called a REST service created in Flogo and which used ConfigureHTTPResponse, the RESTInvoke flow failed if it used ConfigureHTTPResponse whose input was mapped from REStInvoke output.

FLOGO-3858 If an array inside an array was mapped to root, the child elements were not upgraded to ^$loop. Instead, they were mapped using $ only for hybrid mappings.

FLOGO-3856 If you mapped an array to an array and its child elements, an error was displayed at the trigger and activity level even though mappings were correct.

FLOGO-3754 When importing an app, if the app used an extension that was not present in the environment, the import process hanged.

FLOGO-3742 After upgrading to 2.7.0, if you uninstalled the dbservice and then installed it again, the following error was displayed:

Failed to install service

FLOGO-3595 When a Flogo application was created by importing a Swagger specification with multiple response codes, the Message field was displayed in Map from Flow Outputs even after adding a Response body in Reply Settings.

FLOGO-3561 Logs could not be seen in the Flow Tester.

Release 2.7.0

FLOGO-3304 An application that used an open source Project Flogo REST trigger or REST Invoke activity did not work in the Flow tester or with the binary.

FLOGO-3235 An error in a condition was not shown anywhere in the flow except on the condition definition page.

FLOGO-3209 When you import an application created in open source Project Flogo into Flogo Enterprise, the data type of the code field in the REST trigger was not displayed.

(20)

FLOGO-3162 In Lambda applications, if you used an application property when configuring the Execution Role Name field, you could not push the application. The following error was displayed:

Execution role name [=$property ["execRoleName"] ]Execution role name [=$property ["execRoleName"] ]ValidationError: The

specified value for roleName is invalid.

FLOGO-3136 On importing a Lambda Trigger application, Reply Data schema (in the Reply Settings tab in Receive Lambda Invocation Trigger) was lost.

FLOGO-3131 In a condition, you could not check whether an object was empty or null.

FLOGO-3121 Creating a Flogo application from an API specification resulted in a validation error during application creation.

FLOGO-3117 In branch condition, if you compared a string type variable with a number, a validation error was not displayed at design time and the flow did not get executed at runtime.

FLOGO-3102 An error was not displayed for an empty condition on the UI.

FLOGO-3099 If a string in a mapper started with =, the flow failed at runtime.

FLOGO-2863 You could not create a Flogo application from an API specification that had a 400 response code with a schema response.

FLOGO-2855 A flow was unable to capture the body of the response when Invoke API returned a 400 error.

FLOGO-2466 Use of any "trigger output" was not supported in "trigger output" to "flow input" array mappings. Also, use of "flow output" was not supported in "flow output" to trigger reply array mappings.

FLOGO-2432 After upgrading a connector, if you tried to uninstall the connector, the following error was displayed:

bash: ./installmgr.sh: No such file or directory.

FLOGO-2187 When the Iterator key was used as an array index, the following error was displayed and the flow execution failed:

index based access expected for an array

FLOGO-2171 Application properties updated in the AWS Parameter Store were not propagated to Lambda functions when self deploy (./App --deploy) mode was used. The flow continued to use the default value for such properties.

FLOGO-646 Formatting and parsing of date and time to a MM-DD-YYYY format was not supported.

(21)

Release 2.6.1

FLOGO-3204 Flogo applications exported from Project Flogo^™ version 0.9.0 could not be imported into Flogo^® Enterprise 2.6.0.

FLOGO-3186 You were not able to import a Swagger specification which did not have any unsupported methods or paths while creating flows. This has been fixed.

FLOGO-3160 Flogo Enterprise Web UI did not return a validation error for invalid credentials in Connections.

FLOGO-3154 Failed to get data from Marketo Upsert or Delete activity's output errors field.

FLOGO-3152 On Windows plaforms, you were not able to uninstall Flogo Enterprise using the ^installmgr script.

FLOGO-3141 When an app was imported, input data (string) in a subflow activity was lost.

FLOGO-3133 After upgrading Flogo Enterprise from 2.x to 2.6.0, if the application had an OSS activity, the Flogo tester failed to run and displayed the following error

message:

Failed to create engine: %!s(MISSING) error unmarshalling flow:

activity '#error' not imported.

Release 2.6.0

FLOGO-2923 For an empty condition, an error was not returned and the condition was evaluated as true at runtime.

FLOGO-2695 Building a Flogo application binary through UI and testing the Flogo application through Flogo tester did not work.

FLOGO-2512 If you created a Flogo application from an API specification, the flows for the REST methods that had ^query or ^path parameters of type ^integer or ^long were not created even though the application was created successfully.

(22)

FLOGO-2403 To run Flogo Enterprise on the Docker toolbox, you had to do the following:

● provide the virtualbox read/write access if it was installed in any directory other than the home directory hierarchy.

● make the following changes in the bash script file:

SET DATA_DIR="/c/Users/<username>/

customer_docker_18.09.01_toolbox/flogo/data"

SET FLOGO_HOME="/c/Users/<username>/

customer_docker_18.09.01_toolbox/flogo/2.3"

SET TOOLS_DIR="/c/Users/<username>/

customer_docker_18.09.01_toolbox/flogo/tools"

SET SERVICES_DIR_LOCAL="/c/Users/<username>/

customer_docker_18.09.01_toolbox/flogo/services"

ECHO %DATA_DIR%

ECHO %FLOGO_HOME%

ECHO %TOOLS_DIR%

ECHO %SERVICES_DIR_LOCAL%

Release 2.5.0

FLOGO-2404 If you imported an application that contained a connection extension, the application got imported without errors, but you had to recreate the connection after importing the application. The connection detail are now preserved except for the password which must be reset in the imported application.

FLOGO-2396 When invoking a Flogo service from LiveApps, LiveApps didn't get response from the Flogo service. This issue has now been fixed.

Release 2.4.0

FLOGO-2103 If the InvokeRESTAPI activity URL contained "--", it gave an error at design time for Flogo applications. This has now been fixed.

FLOGO-2022 Flogo Enterprise now supports nested ternary operators.

FLOGO-2021 If you removed the array.forEach() from the root element, all the mappings underneath would get deleted. This issue is now fixed.

FLOGO-1999 On certain Windows machines, the uninstall service would fail. This issue has now been fixed.

FLOGO-1925 When overriding a property from the CLI using the

FLOGO_APP_PROPS_OVERRIDE environment variable, if your value was a query that used the comma delimiter, you encountered an error. This issue has now been fixed.

FLOGO-1833 The XPATH expression count() which is used to get the number of array items is now available for Flogo applications.

(23)

FLOGO-1723 Fixed an issue when running run-studio.sh as a regular user, you received a

"permission denied" error.

FLOGO-578 When using branch conditions in Flogo applications, you received error messages when the conditions contained special characters (Expected "(",

",", ".", "/*", "//", ";", "[", comment, end of line, or whitespace but "<" found.) but the condition would work and the flow executed as per the condition provided.

FLOGO-368 If the schema entered in the Input and/or Output tab of a REST activity or trigger contains reserved names in the schema attributes, after the application is imported into Flogo Enterprise Flogo Enterprise, such attributes get treated as special characters which results in runtime errors. The reserved names to avoid in schemas is now documented in the product documentation under the

"Mapper" section.

FLOGO-324 When uploading an application that contained a subflow, the subflow-related configurations did not get imported.

Release 2.3.0

FLOGO-1443 Fixed an issue where if your Flogo application used any Flogo connector using OAUTH for authentication, the application binary built using the Flogo CLI tool did not work at runtime.

FLOGO-1405 Flogo applications exported from prior versions such as 2.0.0 or 2.1.0 were not compatible with the Flogo CLI tool.

FLOGO-325 When uploading an application that contains an iterator, the iterator-related configurations did not get imported.

FLOGO-313 When uploading an application that contained application properties, the application properties related configurations did not get imported.

(24)

Known Issues

The following issues exist in this release of TIBCO Flogo^® Enterprise.

FLOGO-4855 Summary: If you upgrade from Flogo Enterprise 2.8.0 to 2.8.1, the following error message is displayed:

"'o' is not recognized as an internal command

or 'things' is not recognized as an internal command"

Workaround: Ignore the error. The upgrade happens correctly despite the error.

FLOGO-4842 Summary: If you upgrade from Flogo Enterprise 2.x.x to 2.8.1, binaries of an app cannot be generated.

Workaround: Before upgrading from 2.x.x to 2.8.1, manually delete the

<FLOGO_HOME>/2.8/lib/core directory.

FLOGO-4840 Summary: If you upgrade from Flogo Enterprise 2.x.x to 2.8.1, the Flow Tester does not work.

Workaround: Before upgrading from 2.x.x to 2.8.1, manually delete the

<FLOGO_HOME>/2.8/lib/core directory.

FLOGO-4717 Summary: When a Swagger specification file of size 2.5 MB or more is used for creating an app or uploaded using the REST trigger configuration, the app is not deployed to TIBCO Cloud.

Workaround: Use a Swagger specification file of a smaller size.

FLOGO-4659 Summary: When using a field name that contains special characters, the

array.foreach mapping fails with the following error:

eval expression failed to resolve Loop: 'field name', ensure that Loop is configured in the application

Workaround: Add a scope name before the field name. For example, manually change $loop["fieldName"] to $loop["ScopeName"]

["fieldName"].

FLOGO-4628 Summary: If changes are made to a Swagger specification file and the file is saved with a different name, the changes are not reflected in the app even if you click the Sync Schema button.

Workaround: None

FLOGO-4625 Summary: If there are changes in an uploaded Swagger file, a warning message is not displayed requesting the user to update the activity mappings.

As a result, you need to navigate to each downstream activity to check for changes in the schema.

(25)

FLOGO-4583 Summary: A TCM Subscriber app of type Durable with Content Matcher fails to start, if an app with the same Durable name and Content Matcher was pushed before.

FLOGO-4570 Summary: If an array name has ^$ or ^- in it and the flow output is mapped to the Return activity, ^$ or ^- is removed from the array name in the Input field.

FLOGO-3393 Summary: If a Kafka producer produces a JSON string, the Kafka consumer does not receive any data.

FLOGO-4492 Summary: When an app property is bound to a trigger handler configuration and the same trigger is used in another flow, the same app property is used in the new trigger handler.

Workaround: Manually unbind the app property in the new trigger handler.

FLOGO-4420 Summary: While mapping arrays, validation errors are displayed on the UI when the source array comes from a fixed array child such as:

$flow.input[0].test.arraysource. Workaround: None

FLOGO-4416 Summary: When using the isdefined() function in a mapper, if you want to validate whether an array is empty or not, on clicking the array in the Activity Input section on the left side, array.foreach() appears in the mapper on the right side and it fails at runtime.

Workaround: Remove array.foreach() manually and run the app.

FLOGO-4387 Summary: An activity throws a mapper error if the mapped object does not exist, as the FLOGO_MAPPING_SKIP_MISSING environment variable cannot be set in the flow tester.

FLOGO-4375 Summary: When a Kafka app created in a previous release is imported in the current release, and you click Edit in the Connections tab, the Use Schema Registry option is not available in the Apache Kafka Client Configuration dialog box.

Workaround: Create a new connection and use the connection in the app.

FLOGO-4363 Summary: When an app with different trigger and handler settings is

imported, trigger and handler settings are not replaced after selective import.

(26)

FLOGO-4255 Summary: Getting duplicate proto type registered message while starting gRPC app binary which has gRPC trigger and gRPC activity using the same proto file.

Workaround: Change the package name to a different one to make sure gRPC trigger and gRPC activity use the different package name in proto file

FLOGO-4188 Summary: For OpenTracing, even after terminating an app, recurring warnings are displayed in JaegerUI.

FLOGO-4164 Summary: While starting a gRPC app binary which has a gRPC trigger and gRPC activity using the same proto file, the following error message is displayed:

Duplicate enum registered

Workaround: Change the package name to a different one to make sure gRPC trigger and gRPC activity use the different package name in proto file.

FLOGO-4104 Summary:When Project Flogo apps are imported into Flogo, the Input/Output mappings are lost after the Sync Schema option is used.

FLOGO-3624 Summary: If a field in the mapper of an activity is mandatory and you have not provided a value, an error is not displayed on the activity or flow canvas.

FLOGO-3155 Summary: If there is no activity on the UI for some time, the UI is redirected to http://localhost:<port>/undefined/idm/logout-request.

Workaround: Change the URL and access it again:

http://localhost:<port>/

FLOGO-2888 Summary: Flogo does not support uploading Swagger specification definitions which have a cyclic dependency.

FLOGO-2886 Summary: Depending on your machine configuration and browser

configuration, you might not be able to upload a large Swagger API definition JSON file or the browser might become unresponsive. The following error message is displayed on the Network tab and the file is not uploaded:

Request entity too large

FLOGO-2861 Summary: When uploading custom schema for GraphQL, if the custom schema has a cyclic dependency, the following error is returned and the upload fails:

Maximum call stack size exceeded for circular reference

(27)

FLOGO-2844 Summary: 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.

FLOGO-2594 Summary: Deploying Lambda apps on AWS using the Flogo engine binary is not supported.

FLOGO-2536 Summary: Importing a Flogo app using Salesforce activities with no

connection set in connections page takes longer than expected time to import.

FLOGO-2224 Summary: In a REST trigger, when the endpoints have the same base path but different wildcard in path parameters, the app fails to run resulting in a path conflict error.

Workaround:

Change the wildcard names such that they match. For example, if you have the following endpoints:

/books/{name}/id and /books/{name2}/id2

you must change them to either /books/{name}/id and /books/

{name}/id2 or /books/{name2}/id and /books/{name2}/id2

FLOGO-2223 Summary: When there is a conflict in the path parameters wildcards, even though you see an error in the logs, the app proceeds to run.

Workaround: Change the wildcard names.

FLOGO-1488 Summary: Mandatory fields in all the AWS Kinesis activities are not displayed as mandatory in the Web UI.

Workaround: Refer to the AWS Kinesis documentation for mandatory fields.

FLOGO-992 Summary: If you enter an invalid API Key when creating a Chargify connection, you are prompted to enter username and password for your Chargify account instead of an error being displayed.

Workaround: Cancel out of the username/password dialog and reenter the valid API Key. This is a third-party issue.

FLOGO-836 Summary: You can, erroneously, scale a Lambda app to more than one instance.

FLOGO-814 Summary: In the flow error handler, $error.data and $error.code are not supported in the mapper.

Workaround: Manually delete them from mappings from any open source Project Flogo apps imported into Flogo Enterprise.

(28)

FLOGO-358 Summary: On Macintosh platform, if you run the run-studio.sh installer from a directory that is not shared with the Docker container, the installation fails and the following error is displayed:

Mounts denied

Workaround: Configure the path to the run-studio.sh file in Docker >

Preferences > File Sharing before running the run-studio.sh command.

(29)

WIDBSV-37 Summary: The following sections specify the grammar supported by Flogo DB Service 2.0.1 for SQL SELECT, INSERT and DELETE statements. The grammar follows the standard normative form as described in PostgresSQL documentation available on the web.

SQL Statement

The following grammar is supported for SQL SELECT queries:

[ WITH with_query [, ...] ] SELECT [

[ * | expression [ [ AS ] output_name ] [, ...] ] [ FROM from_item [, ...] ]

[ WHERE condition ]

[ GROUP BY grouping_element [, ...] ]

[ { UNION | INTERSECT | EXCEPT } [ ALL ] select ] [ ORDER BY expression [ USING operator ] ] [, ...] ] table_name ]

In general, the following clauses/parameters are not supported:

[ RECURSIVE ] ]

[ HAVING condition ]

{ RANGE | ROWS | GROUPS } frame_start [ frame_exclusion ] { RANGE | ROWS | GROUPS } BETWEEN frame_start AND

frame_end [ frame_exclusion ] [ DISTINCT ]

FIRST | LAST } ] ]

[ LIMIT { count | ALL } ] [ OFFSET start [ ROW | ROWS ] ]

[ FETCH { FIRST | NEXT } [ count ] { ROW | ROWS } ONLY ] [ FOR { UPDATE | NO KEY UPDATE | SHARE | KEY SHARE } [ OF [ NOWAIT | SKIP LOCKED ] ]

INSERT Statement

The following grammar is supported for SQL INSERT statement:

INSERT INTO table_name [ ( column_name [, ...] ) ]

{ VALUES ( { expression } [, ...] ) [, ...] | query } [ RETURNING * | output_expression ]

[ WITH [ RECURSIVE ] with_query [, ...] ] [ OVERRIDING { SYSTEM | USER} VALUE ] { DEFAULT VALUES ( { DEFAULT } ) }

[ ON CONFLICT [ conflict_target ] conflict_action ] [ [ [ AS ] output_name ] ]

DELETE Statement

The following grammar is supported for SQL DELETE statement:

DELETE FROM table_name [ * ] [ USING using_list ] [ WHERE condition ]

[ RETURNING * | output_expression ]

[ WITH [ RECURSIVE ] with_query [, ...] ] [ ONLY ] [ [ AS ] alias ]

[ WHERE CURRENT OF cursor_name ] [ [ [ AS ] output_name ] [, ...] ]

SQL Functions

The CONCAT SQL function is currently not supported for all database connectors.

TIBCO Flogo®

Release Notes

Software Release 2.8.1

February 2020

Contents

TIBCO Documentation and Support Services

New Features

Changes in Functionality

Deprecated and Removed Features

Migration and Compatibility

Closed Issues

Known Issues