TIBCO Flogo® Enterprise Release Notes

(1)

Release Notes

Software Release 2.6.0

May 2019

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

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.

(6)

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

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 app and manage it using external stores, so that you can deploy the same app in multiple environments without making any changes to the app. 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 app

configuration. This release also adds the ability to export application properties from the app binary in a JSON file, or as environment variables. If you use application properties for configuring secrets in your app, such as database passwords, you can now generate obfuscated values for the secrets.

Application Logging

This release adds support for the Zap library for app logging. Zap aims to provide fast, structured, and leveled logging. You can switch to the Zap logger for your app 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

(7)

This release provides the ability to collect flow and activity metrics for monitoring your app using a REST API. You can now enable collection of app 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 app using the REST API.

Subflows

This release adds support for creating a subflow and calling the subflow from other flows in your app.

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

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

(8)

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.

(9)

Changes in Functionality

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 Apps

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

Application Property

This release of Flogo Enterprise provides additional validations for app properties. If you delete an app property or the property is not configured properly, the app 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="{}"

(10)

Deprecated and Removed Features

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

Release 2.6.0

● No features have been deprecated or removed in this release.

Release 2.5.0

● 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

● No features have been deprecated or removed in this release.

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.

(11)

Migration and Compatibility

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 app created in an earlier version of Flogo Enterprise, the app 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.

(12)

Closed Issues

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

Release 2.6.0

Key Description

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

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

FLOGO-2512 Summary: If you created a Flogo app 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 app was created successfully.

FLOGO-2403 Summary: 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 Summary: If you imported an app that contained a connection extension, the app got imported without errors, but you had to recreate the connection after importing the app. The connection detail are now preserved except for the password which must be reset in the imported app.

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

(13)

Release 2.4.0

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

FLOGO-2022 Summary: Flogo Enterprise now supports nested ternary operators.

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

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

FLOGO-1925 Summary: 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 Summary: The xpath expression count() which is used to get the number of array items is now available for Flogo apps.

FLOGO-1723 Summary: Fixed an issue when running run-studio.sh as a regular user, you received a "permission denied" error.

FLOGO-578 Summary: When using branches conditions in Flogo apps, 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 Summary: 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 app 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 Summary: When uploading an app that contained a subflow, the subflow- related configurations did not get imported. This has now been fixed.

Release 2.3.0

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

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

(14)

FLOGO-325 Summary: When uploading an app that contains an iterator, the iterator-related configurations did not get imported. This has now been fixed.

FLOGO-313 Summary: When uploading an app that contained app properties, the app properties related configurations did not get imported. This has now been fixed.

(15)

Known Issues

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

FLOGO-3204 Summary: Flogo apps exported from Project Flogo^™ version 0.9.0 can not be imported into Flogo^® Enterprise 2.6.0.

Workaround: Open the <application>.json file in a text editor and change

version from 0.0.1 to 1.1.0.

FLOGO-3162 Summary: In Lambda apps, if you use an application property when configuring the Execution Role Name field, you will be unable to push your app. You get an error, Execution role name [=$property

["execRoleName"] ]Execution role name [=$property

["execRoleName"] ]ValidationError: The specified value for roleName is invalid.

Workaround: Do not use an application property when configuring the Execution Role Name field.

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

Workaround: Re-enter your credentials. If your credentials are valid, the Connections page opens.

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-3154 Summary: Failed to get data from Marketo Upsert or Delete activity's output errors field.

Workaround: Get the value from the Marketo Upsert activity output field.

FLOGO-3152 Summary: On Windows plaforms, you cannot uninstall FE using the

installmgr script.

Workaround: Delete <version> folder and ^data folder manually and rename backed up /data folder to ^data.

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

Workaround: None

FLOGO-3136 Summary: On importing a Lambda Trigger app, Reply Data schema (in the Reply Settings tab in Receive Lambda Invocation Trigger) is lost.

Workaround: Manually enter the schema.

(16)

FLOGO-3133 Summary: After upgrading Flogo Enterprise from 2.x to 2.6.0, if the app has an OSS activity, the Flogo tester fails to run and displays the following error message:

Failed to create engine: %!s(MISSING) error unmarshalling flow: activity '#error' not imported.

Workaround: Export and import the same app to resolve this issue. You may need to reconfigure some Project Flogo activities.

FLOGO-3124 Summary: After importing a Flogo app, an extra return activity is added if the flow has no return activity.

Workaround: Manually delete the extra return activity.

FLOGO-3117 Summary: In branch condition, if you compare a string type variable with a number, a validation error is not displayed at design time and the flow does not get executed at runtime.

Workaround: Compare a string type variable with a string value.

FLOGO-3099 Summary: If any string in a mapper starts with =, the flow fails at runtime.

Workaround: Avoid using = as the first character in a string.

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

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-2676 Summary: On Linux platforms, the Flogo Enterprise Web UI does not launch after connecting to VPN.

Workaround: Disconnect the VPN and re-launch or refresh the Flogo Enterprise Web UI.

(17)

FLOGO-2594 Summary: Currently, 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-2466 Summary: Use of any "trigger output" is not supported in "trigger output" to

"flow input" array mappings. Also, use of "flow output" is not supported in

"flow output" to trigger reply array mappings.

Workaround: Use ^$flow instead of ^$ in the mapping.

FLOGO-2432 Summary: After upgrading a connector, if you try to uninstall the connector, you get an error saying bash: ./installmgr.sh: No such file or directory.

FLOGO-2344 Summary: When you use the Iterator key as an array index, the following error is displayed and the flow execution fails:

index based access expected for an array

Workaround: Ignore the UI validation error and build it.

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-2187 Summary: When using an iterator to loop over an array or to invoke an activity a certain number of times, if you access the iterator value and index using $current.iteration.value or $current.iteration.key you encounter an error such as "index based access expected for an array".

Workaround: None. This is not currently supported.

(18)

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

FLOGO-1684 Summary: When accessing the Flogo Enterprise Web UI, you get a "502 Bad Gateway" error if your machine is configured with a static IP address.

Workaround: Configure your machine IP address as dynamic.

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 will be prompted to enter username and password for your Chargify account instead of getting an error.

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

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

Workaround: None.

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 FLOGO OSS applications imported into Flogo Enterprise.

FLOGO-389 Summary: FLOGO does not support anonymous arrays.

Workaround: Add a root element to the array.

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 will fail resulting in a Mounts denied error.

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

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

(19)

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. As such, this document does not go at lengths describing parameters and their elements constituting each clause in the grammar, instead it assumes familiarity and understanding of these constructs from the user. Nevertheless, the user may consult PostgreSQL documentation on the Web for detailed description if they so may desire.

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

(20)

Key Description All DB Connectors

Following SQL functions are currently not supported:

CONCAT

TIBCO Flogo® Enterprise Release Notes

Release Notes

Software Release 2.6.0

May 2019

Contents

TIBCO Documentation and Support Services

New Features

Changes in Functionality

Deprecated and Removed Features

Migration and Compatibility

Closed Issues

Known Issues