The following issues exist in this release of TIBCO Flogo® Enterprise.
Flogo Enterprise Core
The following issues exist in this release of Flogo Enterprise.
Key Description
FLOGO-7968 Summary: If you have defined the multipart form data field as filecontent but provide string in the input, multipart form data is returned as a string instead of a file.
Workaround: Use array.create("string") while passing multipart content.
FLOGO-7967 Summary: If you have defined a filecontent type multipart form data field, you cannot provide a filename as input.
Workaround: None
FLOGO-7868 Summary: [Microsoft Azure] When building an app binary, messages of the build process are not shown on the UI immediately. They are shown only after the build process is completed.
Workaround: None
FLOGO-7810 Summary: When the ReplyToTrigger activity is used in a flow, the following warning related to the Return activity is incorrectly displayed:
Flow output is defined but not configured. To set flow output, add Return activity from Default category.
Workaround: Ignore the warning. It does not impact run time.
FLOGO-7665 Summary: Instrumentation metrics data is not available for an app and tibagent deployed on AWS Fargate.
Key Description
Workaround: None
FLOGO-7657 Summary: When adding a description for an app, the "This field is required" message is displayed and the cursor moves in front of the message when you start typing the description. The message does not go away until you go inside the flow. The Back button is also disabled.
Workaround: None
FLOGO-7600 Summary: For Project Flogo extensions, configuration UI is disoriented after clicking on the Discard button and requires a browser refresh. If you click the Discard button, the UI for FIELDS is transformed to basic type inputs
(input=text).
Workaround: None
FLOGO-7572 Summary: When you upload a contribution with a Default category (display.category set to Default), an error message is not displayed.
Workaround: None
FLOGO-7491 Summary: REST trigger settings UI hangs when an app is created from Open API spec 3.0 with Object type in multipart/form-data request.
Workaround: Change the Object type multipart data to string in the API spec and then create the Flogo app from the API spec.
FLOGO-7464 Summary: The Multipart/form-data table does not sync properly when API spec is uploaded in the InvokeRestService activity.
Workaround: Refresh the page after uploading the API spec and saving the settings in the InvokeRestService activity. Then, the table or schema is populated.
FLOGO-7436 Summary: Runtime validation is not enabled for Required Form Params. Workaround: None
FLOGO-7421 Summary: Runtime validation error is observed for filecontent type data
Key Description
when Output Validation is set to true in the REST trigger.
Workaround: Do not enable Output Validation when the Request type is multipart/form-data in the REST trigger.
FLOGO-7411 Summary: Overriding app property names with (secs) for the deployed Lambda functions from the command line is not supported.
Workaround: Remove the app property name with (secs) from the property file.
FLOGO-7405 Summary: If you use a function as a source array for array.foreach(), Studio cannot determine the array element schema and throws a design-time validation error.
Workaround: Use the mapper to define the function output schema and then use it in the array.foreach() source array.
FLOGO-7269 Summary: On the flow list page, a "missing extension" validation error is shown for each flow even after installing the missing extension.
Workaround: Validate each flow to remove the validation error for that flow.
FLOGO-7031 Summary: When building an app binary from builder CLI with Golang version 1.15.x, the gRPC activity fails to send a request and displays the following error:
authentication handshake failed: x509: certificate relies on legacy Common Name field, use SANs or temporarily enable Common Name matching
Workaround:
1. Downgrade the Golang version to 1.14.x.
2. Run the binary with the option GODEBUG=x509ignoreCN=0 as follows:
GODEBUG=x509ignoreCN=0 ./binary
FLOGO-6951 Summary: Password type app properties do not support encrypted values during design time.
Key Description
Workaround: None
FLOGO-6950 Summary: If an app is created with app property type as password and double quotes are used in the value of the password, the app fails.
Workaround: Avoid using double quotes in the password.
FLOGO-6904 Summary: When the InvokeRESTService activity is used with the HTTP Client Authorization Configuration connection and OAuth2 Authorization type, it fails to auto-refresh the token if the expired or invalid token response does not have the status code as 401.
Workaround: Use another InvokeRESTService activity to get the new token and use the new token in InvokeRESTService activity.
FLOGO-6847 Summary: If a database connector activity has a design time error, the message incorrectly disappears after clicking the Clear Table link.
Workaround: None
FLOGO-6586 Summary: The value of BIGINT data type is converted to an incorrect value.
Workaround: If possible, use a STRING data type instead.
FLOGO-6552 Summary: The resource path of a previous specification is shown in the Resource path list even after deleting the specification file and uploading a new specification file.
Workaround: Select the resource path from the Resource path list even if it shows paths of previous specifications. Even though the specification displayed is incorrect, the new path is loaded.
FLOGO-6542 Summary: If you upload an OpenAPI Specification (OAS) file in the
InvokeREST activity and later upload an updated version of the same OAS, the changes to the schema are not reflected in the associated parameters and request/response schemas.
Workaround: Delete the original specification and upload the new OAS again.
Key Description
FLOGO-6458 Summary: If you use the Cisco AnyConnect VPN client and then use the InvokeRESTService in the debugger to call a service, it fails.
Workaround: Use any VPN client other than Cisco AnyConnect. Alternatively, restart the UI after disconnecting the VPN.
FLOGO-6383 Summary: When the REST trigger (ReceiveHTTPMessage) or
InvokeRESTService activity is configured with Swagger/Open API Specification, any manual changes to the configuration are reset when the specifications are uploaded again.
Workaround: None
FLOGO-6237 Summary: Using literal values in the string.join function in a Flogo app fails both at design and run time.
Workaround: None
FLOGO-6031 Summary: In the InvokeRestService activity, the application level schema toggle is displayed for plain/text and other type request and response.
Workaround: None
FLOGO-5400 Summary: While running an app in flow tester, if you provide a JSON schema with a nested array, it returns an error at design time.
Workaround: None
FLOGO-5267 Summary: The ConfigureHTTPResponse activity is not updated correctly when reply settings are changed.
Workaround: Trigger a save operation by re-doing or undoing some of the mapper mappings on the ConfigureHTTPResponse activity.
FLOGO-5133 Summary: In the ReceiveHTTPMessage trigger and InvokeRestService service, you cannot select an app-level schema if the trigger or activity has multiple responses.
Workaround: None
Key Description
FLOGO-4936 Summary: Boolean data type and null data type are not supported in TIBCO Cloud Messaging.
Workaround: None
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-4716 Summary: If required elements of a request schema are not provided, the runtime provides a response but the tester returns a validation error.
Workaround: None
FLOGO-4661 Summary: Single quotes are not supported in mapper variables.
Workaround: None
FLOGO-4659 Summary: If you use 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
Key Description
change $loop["fieldName"] to $loop["ScopeName"]["fieldName"]. FLOGO-4653 Summary: An unsupported data type in the request or response schema is not
converted to a supported one.
Workaround: In the API Spec, change the type to the supported data type. For example, change Float and long data type to Integer.
FLOGO-4628 Summary: If a Swagger specification file is modified 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.
Workaround: None
FLOGO-4583 Summary: A TIBCO Cloud™ Messaging 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.
Workaround: None
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.
Workaround: None
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.
Key Description
FLOGO-4363 Summary: When an app with different trigger and handler settings is
imported, trigger and handler settings are not replaced after selective import.
Workaround: None
FLOGO-4255 Summary: While starting a gRPC app binary which has a gRPC trigger and gRPC activity using the same proto file, duplicate proto type registered message was returned.
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.
Workaround: None
FLOGO-4164 Summary: While starting a gRPC app binary that 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-3906 Summary: After mapping array root nodes, when a child node mapping is updated, only a mapped child node is returned at run time.
Workaround: None
FLOGO-3821 Summary: When configuring a response code in a REST trigger, the response body and response header must follow the same input schema type.
Workaround: Ensure that the response body and response header is of the same type, either JSON data or JSON schema.
Do not use ConfigureHTTPResponse in the RESTInvoke flow.
Key Description
FLOGO-3393 Summary: If a Kafka producer produces a JSON string, the Kafka consumer does not receive any data.
Workaround: None
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: You cannot upload Swagger specification definitions which have a cyclic dependency.
Workaround: None
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
Workaround: None
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
Workaround: None
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.
Workaround: None
Key Description
FLOGO-2720 Summary: You cannot export app properties from a binary that has an API Gateway or S3 trigger.
Workaround: None
FLOGO-2594 Summary: Deploying Lambda apps on AWS using the Flogo engine binary is not supported.
Workaround: None
FLOGO-1757 Summary: JSON schema with cyclic references is not supported.
Workaround: Remove the cyclic references from the schema.
FLOGO-1727 Summary: When a value which starts with 0 is assigned to a field of integer type, the mapper throws a validation error.
Workaround: Define such values as a string and then use coerce.toint() for integer values.
FLOGO-1684 Summary: When accessing the UI, a "502 Bad Gateway" error is returned if the machine is configured with a static IP address.
Workaround: Configure the machine IP address as dynamic.
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 box and reenter the valid API Key. This is a third-party issue.
FLOGO-814 Summary: In the flow error handler, $error.data and $error.code are not supported in the mapper.
Workaround: If you import an open source Project Flogo app, manually delete
$error.data and $error.code from the mappings.
FLOGO-358 Summary: On macOS, if you run the run-studio.sh installer from a directory
Key Description
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.