Introducing the all-new TIBCO Community site!

For current users, please click "Sign In" to reset your password and access the enhanced features. If you're a first-time visitor, we extend a warm welcome—click "Sign Up" to become a part of the TIBCO Community!

If you're seeking alternative community sites, explore ibi, Jaspersoft, and Spotfire.

Jump to content
  • Develop / TIBCO Flogo® Known Issues


    Ana Bahr

    To access release notes see: TIBCO Cloud? Integration Release Notes at https://community.tibco.com/s/article/TIBCO-Cloud-Integration-Release-Notes.

    To access Known Issues for other TIBCO Cloud ? Integration capabilities see TIBCO Cloud ? Integration Known Issues at https://community.tibco.com/s/article/tibco-cloud-tm-integration-current-known-issues

    FLOGO-592 / IPAS-4946

    Summary: In Web Integrator, when a RESTTrigger is created from a schema or JSON sample data containing Date and DateTime type attributes, the Date and DateTime DataTypes are shown as a string in the output tab of POST/PUT Operations and Input of ReplyToHTTPMessage Activity. Also, for the double data type, is shown as a number, and the null data type is shown as a blank icon in the mapping input tab.

    Workaround: None.

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

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

    Workaround: None.

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

    Summary: When a value that 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-1757

    Summary: JSON schema with cyclic references is not supported.

    Workaround: Remove the cyclic references from the schema.

    FLOGO-2720

    Summary: You cannot export app properties from a binary that has an API Gateway or S3 trigger.

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

    Summary: TIBCO Flogo® does not support uploading Swagger specification definitions that have a cyclic dependency.

    Workaround: None.

    FLOGO-3393 

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

    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.

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

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

    Workaround: None.

    FLOGO-4127

    Summary: App properties of type INTEGER are not supported.

    Workaround: None.

    FLOGO-4255

    Summary: While starting a gRPC app binary that 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-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-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-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-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-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-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-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-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 change $loop["fieldName"] to $loop["ScopeName"]["fieldName"].

    FLOGO-4661

    Summary: Single quotes are not supported in mapper variables.

    Workaround: None.

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

    Summary: Not able to invoke BusinessWorks service returning string response through InvokeRestService.

    Workaround: None.

    FLOGO-5361

    Summary: For Flogo apps with no public endpoints, such as apps with triggers other than REST or GraphQL, the set endpoint visibility option displays in the User Interface.

    Workaround: This can be ignored.

    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-5904 / IPAS-10432

    Summary: TIBCO Flogo® app properties do not work with the port field on REST and GraphQL triggers.

    Workaround: Port does not support app property, manually change the port when needed.

    FLOGO-6067

    Summary: In TIBCO Flogo, when app ownership is transferred to a Read-Only user, passwords are not preserved. 

    Workaround: None.

    *FLOGO-6208

    Summary: For a Flogo app pushed using the TIBCO Cloud Integration - Command Line Interface, the connection is not shown in your flow activities if the associated connection is not already present in the Connections page in the TIBCO Cloud Integration user interface.

    Workaround: None. Since the app implementation is read-only, you do not need to select the missing connection in your flow activities. At runtime, it does not report any errors.

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

    Summary: For undeployed Flogo apps, updating engine variables from the Environment Controls section changes the  app status to Stopped in the App Details page.

    Workaround: Update engine variables after the app is deployed.

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

    Summary: There is no validation for connection names, which allows a user to create or promote a connection to the organization level with the same name as an existing organization level connection. 

    Workaround: None.

    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.

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

    Summary: You can create and promote a connection with the same name as an org-level connection. 

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

    Summary: The order of elements in an object in a JSON file is not maintained when the file is processed. 

    Workaround: None.

    FLOGO-6819

    Summary: When running in the debugger, if you provide a value that is a string or object data type for a field that is a number data type, or a value that is a number data type for a field that is a string or object data type, no error message is displayed. 

    Workaround: None.

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

    Summary: The Connectivity issue prompt appears when the source mesh service is not available in the environment. 

    Workaround: Click the Back button on the left corner of the service picker dialog and choose a new service from the list. 

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

    Summary: When the InvokeRestService activity is configured with an Open API spec, the response headers are converted to JSON Data instead of JSON Schema in the InvokeRest Output settings.

    Workaround: None.

    FLOGO-6951

    Summary: Password type app properties do not support encrypted values during design time.

    Workaround: None.

    *FLOGO-6989

    Summary: When invoking a service via an Activity, the XML to JSON conversion is incorrect. 

    Workaround: None.

    FLOGO-7012

    Summary: When a Swagger 2.0 app is renamed and re-pushed, the Swagger checksum changes.

    Workaround: None.

    FLOGO-7062

    Summary: After upgrade, existing apps show the Retry on Error tab, but the tab does not show the Count and Interval fields.

    Workaround: To use retry on error at activity level, export and import app or create a new app.

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

    Summary: If you install a TIBCO Flogo app configured with an organization level connection from the Marketplace, a corresponding organization level connection is created in your organization each time you install that app. 

    Workaround: None.

    FLOGO-7320

    Summary: If you GET a private/public marketplace app listing which has a connection used in it, a new connection is not created under the connections tab.

    Workaround: User needs to create and configure a connection manually.

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

    Summary: Runtime validation error is observed for filecontent type data 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-7539

    Summary: When Configure Response Codes is set to true in the InvokeRestService Activity Output Settings, only application/JSON and string response types are supported.

    Workaround: If you get a response content type other than application/JSON or string, then set the Configure Response Codes to False and select the Response type from the drop-down.

    FLOGO-7582

    Summary: The request body given for the application/JSON request type appears in the API Swagger page along with multipart data parameters if the request was later changed to multipart data from application/JSON.

    Workaround: Remove the request schema from the Output settings, save the trigger, and change the Request type to multipart/form-data.

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

    Summary: Instrumentation metrics data is not available for an app and a Hybrid Agent deployed on AWS Fargate.

    Workaround: None.

    FLOGO-7684

    Summary: If you drag an array from Available data to the mapper text area that already has an array.forEach function, the array is mapped again as an array.forEach function (instead of being added to the existing array.forEach function).

    Workaround: None.

    FLOGO-7744

    Summary: In TIBCO Cloud Integration, the Enable secure connection option is not available for the Receive HTTP Message Trigger.

    Workaround: None.

    FLOGO-7803

    Summary: In TIBCO Cloud Integration, the custom go code supporting feature is not available.

    Workaround: None.

    FLOGO-7868

    Summary: [Microsoft Azure] When building an app binary, build process messages are not shown on the User Interface immediately. They are shown only after the build process is completed.

    Workaround: None.

    FLOGO-7927

    Summary: When you specify a filter as the third argument in the array.forEach() function, $loop is not evaluated automatically when you drag-and-drop a child element. Instead, the whole path is populated.

    Workaround: Manually edit it and replace the parent path with the $loop expression.

    FLOGO-8007

    Summary: When a key-value pair is provided as an array in the Request schema for the Request type Form-urlEncoded in the ReceiveHTTPMessage trigger, the endpoint is not generated.

    Workaround: Do not provide a key-value pair as an array object. Instead, provide it as a JSON object.

    FLOGO-8107

    Summary: If you map an array to an array using the array.forEach function and specify a scoping variable in a nested array,  [<<index>>] is not shown while mapping child elements and generates an error in activity. 

    Workaround: None.

    FLOGO-8258

    Summary: The Protobuf2JSON activity shows a design-time error when you refresh the browser. No error is reported during runtime.

    Workaround: Click Validate.

    FLOGO-8287

    Summary: If a root or parent array is not mapped, the Add condition menu is wrongly displayed in the mappings of the array children and the mapper hangs. 

    Workaround: Close and reopen the activity configuration. Map the root or parent array.

    FLOGO-8300

    Summary: When a condition is added to the data mapper, the mapper does not automatically open the input mapping field.

    Workaround: Scroll down to view the newly added condition and then manually open the input field.

    FLOGO-8349

    Summary: If an activity has an empty or incorrect input, a validation error is indicated by a red error icon. Even when the erroneous condition is removed, the error icon continues to be displayed. 

    Workaround: Click Validate.

    FLOGO-8350

    Summary: When a gRPC activity is used in an app and the app is started, the following warning is displayed:

    WARNING: Package "github.com/golang/protobuf/protoc-gen-go/generator" is deprecated.WARNING: Package "github.com/golang/protobuf/protoc-gen-go/generator" is deprecated. A future release of golang/protobuf will delete this package, which has long been excluded from the compatibility promise.

    Workaround: Ignore the warning.

    FLOGO-8413

    Summary: After adding multiple If/Else conditions in a mapper, the new conditions are not visible on the UI immediately and there is a minor delay before they are available for viewing. 

    Workaround: None.

    FLOGO-8432

    Summary: Mapping child elements using $loop in an array.forEach function results in a mapper validation error. No error is reported during runtime.

    Workaround: None.

    FLOGO-8476

    Summary: If a mapping variable has a ?-? in the name, flow fails to execute at runtime.

    Workaround: None.

    FLOGO-8479

    Summary: If you rerun an activity using the Rerun flow from this activity button on the Executions page, the Completed count displayed on the Metrics page > Flow tab > Activity Execution (count) does not include the rerun of the activity from which the rerun is performed.

    Workaround: None.

    FLOGO-8476

    Summary: If a mapping variable has a ?-? in the name, flow fails to execute at runtime.

    Workaround: None.

    FLOGO-8535

    Summary: When the Coerce with schema option is used, data of type ANY is not converted to OBJECT type upon save or sync. 

    Workaround: Switch between tabs and the data gets converted.

    FLOGO-8711

    Summary: When the environment is upgraded from a previous version, the Set-Cookie header does not appear in the output of InvokeRESTService activity.

    Workaround: None.

    FLOGO-8740

    Summary: When you try to change an existing cron expression to default by using one of the following methods, the Save and Discard buttons in the cron expression builder are disabled:

    • switching to cron builder and accepting the pop-up

    • switching from timer to cron

    Workaround: Click on a cron expression field and then click outside the cron expression builder. The Save and Discard buttons are enabled.

    FLOGO-8778

    Summary: Importing an app in an environment where the Execute JavaScript activity does not exist,  returns an error indicating that the activity is missing in the error Handler flow.

    Workaround: None.

    FLOGO-8823

    Summary: When an app is pushed using the TIBCO Cloud - Command Line Interface or the TIBCO Cloud Integration API, the app status is shown as Running instead of Scaling. 

    Workaround: None.

    FLOGO-8844

    Summary: When creating an app, if you upload a large-sized API specification file, the page becomes unresponsive. 

    Workaround: None.

    FLOGO-8848

    Summary: For an Apache Kafka app with AVRO schema, a validation error symbol is displayed in the consumer trigger. 

    Workaround: None.

    FLOGO-8896

    Summary: An API spec with the  keyword 'allOf' does not work as expected. 

    Workaround: None.

    FLOGO-8912

    Summary: If you configure a new connection to an on-premises database, it generates errors with error code 400.

    Workaround: Disable and re-enable the database service from the Hybrid Database connection page.

    FLOGO-8933

    Summary: If you rename a connection and then select the Create new connection option while importing an app, connection names are not created correctly.

    Workaround: None.

    FLOGO-8936

    Summary: If an app has an InvokeRESTService activity that invokes a TIBCO Cloud Mesh Service, and you navigate inside the flow details page or reload the flow canvas page, validation hangs. 

    Workaround: Wait until the 'Validate' button is enabled and then click it to validate the flow.

    FLOGO-8988

    Summary: Error propagated from the trigger does not trigger error handler flow.

    Workaround: None.

    FLOGO-9142
    Summary: If an activity is executed in a loop, on the Execution History tab, the Completed count is more than the Started count.
    Workaround: None.

    FLOGO-9159

    Summary: If a REST trigger has an app schema and it is attached to the Request or Response schema and later reconfigured using an API spec, a ?Bad gateway? error is observed.

    Workaround: Detach the app schema from the Request or Response schema before configuring the trigger using an API spec.

    FLOGO-9160

    Summary: In certain subscriptions, the Flogo app Id is not appended to AWS Lambda function name when AWS Lambda trigger app is pushed to TIBCO Cloud Integration.

    Workaround: None.

    FLOGO-9204

    Summary: If an app property value is set to empty and the TIBCO Cloud Command Line Interface is used to deploy the Flogo app, the default value of the app property from the flogo.json file is used instead of the value in the app.properties file.
    Workaround: None.

    FLOGO-9370

    Summary: A Mapper activity returns an empty array as output, on mapping multiple items and providing a single array element as input.

    Workaround: None.

    FLOGO-9373

    Summary:  Unit test execution fails if a TIBCO Flogo app is using a user supplement.

    Workaround: None.

    FLOGO-9381

    Summary: Unit test case execution is skipped if an error or exception is reported at runtime.

    Workaround: Handle the error or exception in the error handler flow.

    FLOGO-9394

    Summary: After clearing a mapping and adding an item, the item is not added the first time. 

    Workaround: Click 'Add item' multiple times.

    FLOGO-9449

    Summary: The Lambda trigger apps are not getting updated when redeployed. The error message ?An update is in progress? is displayed in the logs.

    Workaround: Delete the previous deployed version and deploy a new Lambda app.

    FLOGO-9517
    Summary: When an API spec file is uploaded in the InvokeRest activity or the REST trigger, common parameters for all operations at the path level are not displayed in the Input Settings tab.

    Workaround: Define the common parameters separately for each operation. The parameters are displayed in the Input settings tab.

    FLOGO-9556

    Summary: When using the Flow Tester, if a null value is passed in the schema at the object level, a validation error is returned and the test does not run. 

    Workaround: None.

    FLOGO-9583

    Summary: In an activity configuration, when mappings are cleared in the input mapper using "Clear Mappings", the mappings are cleared, but the items are still visible. If you close the activity configuration and return to the input mapper, the items are no longer visible.

    Workaround: None.

    FLOGO-9586

    Summary: On importing a flogotest file with matching unit test data, a copy of existing test cases and test suites is created with new names.

    Workaround: Delete the newly added copy of test cases and test suites manually.

    FLOGO-9771

    Summary: If you make changes to a pinned app, push it, and then restore the pinned app, the changes are not reflected on the User Interface. 

    Workaround: To verify whether the app was restored, rescale the app.

    FLOGO-9821

    Summary: For remote apps, when you override an app property on the TIBCO Cloud Integration UI, the FLOGO_APP_PROPS_ENV=auto engine variable is displayed in read-only mode.

    Workaround: None.

    FLOGO-9990

    Summary: Trigger panel inside a flow does not open when we add a trigger from the flow list page.

    Workaround: Click the Add trigger on a flow, followed by the Trigger button in the Control panel and now you can add any trigger.

    FLOGO-10038

    Summary: If you have mocked an activity and later try to reset it to default by switching back to Assert mode without adding any assertions, then the activity displays in the test run results.

    Workaround: Clear the mappings from the mock data, save it, and select assert mode again.

    FLOGO-10047

    Summary: If the mappings in the unit testing Mock feature for an activity in a Flogo flow are not correct, the activity will not be mocked and will not fail at run time.

    Workaround: Correct the mappings in the Mock data. 

    FLOGO-10052

    Summary: The  Lambda trigger does not work when using ?Default Credentials Chain? authentication. 

    Workaround: None. 

    FLOGO-10055

    Summary: Changes to Flogo apps that use the BuildCreateLeadInput activity and have conditional mapping on tag input, cannot be pushed. 

    Workaround: remove conditions from Tag input. 

    FLOGO-10082

    Summary: Imported flows configured with fields that take values from two places, such as Activity Settings and Inputs, continue to use the value at runtime, even if that value has been removed. 

    Workaround: None.

    FLOGO-10169

    Summary: The Application Service Registry (ASR) dialog displays the error message "Service not found" if you have imported an ASR client app and then try to select a different ASR service. 

    Workaround: Refresh the browser page.

    FLOGO-10233

    Summary: If you attempt to change the owner of an app and the change fails, flows contained in the app are lost. 

    Workaround: None.

    FLOGO-9905

    Summary: When we search for any property, we see the appropriate list of properties as per its name, along with the ones which have no value.

    Workaround: None.

    FLOGO-10019

    Summary: While running a flow from flow tester, if we want to run a test on the activity, the activity is not highlighted in any color.

    Workaround: None.

    FLOGO-10300

    Summary: When there is a large flow and we want to connect many activities together,  then drawing the  connection lines must auto scroll the page.

    Workaround: Zoom out the flow canvas by clicking the zoom in and out button and then connect the activities.

    FLOGO-10350

    Summary: When we open a flow and click an activity, sometimes it does not open with a single click and a message, saving changes, is displayed.

    Workaround: None.

    FLOGO-10419

    Summary: The branching mapping window closes directly after clicking the Save button. There is no Close option.

    Workaround: None.

    FLOGO-10456

    Summary: If an activity is added and not connected to any branch or activity, and later exported and imported back, then this added activity is not seen.

    Workaround: None.

    FLOGO-10459

    Summary: Full name of the activities is not displayed on the canvas.

    Workaround: Hover over the activity tile to view the full name.

    FLOGO-10499

    Summary: When creating an app, if the app has used schema where the correct type or value has not been defined for the attribute  "xml", the following error is displayed: 
    ?xml has type or value wrong?.

    Workaround: Define the type or value for the attribute correctly.

    FLOGO-10523

    Summary: If we make a copy of an app created in TCAM, then we are not able to see its entry in the TIBCO Cloud? Integration - API Modeler create Flogo app section.

    Workaround: None.

    FLOGO-10529

    Summary: When an API specification is renamed, the renamed API specification is not reflected in the Browse File option of the Trigger Setting upon clicking the Refresh icon in a REST trigger..

    Workaround: Manually export the API specification  from the TIBCO Cloud? Integration - API Modeler and re-import it in the Trigger Setting.

    FLOGO-10565

    Summary: When we upload an API specification  which has constructs that are not supported in Flogo, like Option method and Common Parameters, a warning must be displayed.

    Workaround: None.

    FLOGO-10567

    Summary: The validation error symbol is not present in the  Settings or the Input tab if we switch to another activity without closing the previous activity configuration settings.

    Workaround: Close the activity configuration and then switch to another activity.

    FLOGO-10572

    Summary: When creating an app from TCAM/API modeler, a meaningful error is not returned if the API specification has a cyclic redundancy.

    Workaround: None.

    FLOGO-10576

    Summary: The Refresh icon in a REST trigger vanishes if you discard changes, close the pop-up in the flow list page and trigger configuration in flow details page.

    Workaround: Refresh the page either by reloading it or navigating from the flow list page to the flow details page.

    FLOGO-10609

    Summary: After importing old Flogo projects, this message is displayed -  "One or more activities are not connected".

    Workaround: None.

    FLOGO-10617

    Summary: When we use special characters in the SQL Editor, an auto suggestion feature is showing up.

    Workaround: None.

    FLOGO-10620

    Summary: The connection line highlights vanish after switching the tab from the main flow to the error handler flow while running through the flow tester.

    Workaround: Notice that there are activity highlights that indicate the particular activities to be executed.

    FLOGO-10628

    Summary: When we modify the API specifications,  the Refresh icon must pop-up after opening the Trigger Setting. However, there is some delay for the Refresh icon to be visible.

    Workaround: None.

    FLOGO-10707

    Summary: When trying to execute the branch merging process, ?Run test from this activity" button in flow tester does not work. The flow gets blocked due to this.

    Workaround: None.

    FLOGO-10732

    Summary: In cases where there is only one successful branch or a branch with one true condition in the flow tester, it results in all the branches getting highlighted. This happens irrespective of whether the other branches include false conditions or error.

    Workaround: None.

    FLOGO-10753

    Summary: Branch error icon is not displayed properly in certain circumstances. For example, it is not shown properly for the upgraded and imported apps having multiple branches, even  if one of the branches has any error in the condition. If activities are closer to each other then the branch error icon gets hidden behind the branch label.The branch icon is not aligned in the middle on the connection line.

    Workaround: Branch error is seen after moving the activity from its current position.

    FLOGO-10803

    Summary: When you add App Schema and click Rest Trigger, the UI becomes unresponsive. The trigger is removed after you refresh the page.

    Workaround: Refresh the page to reload the UI and add the trigger manually.

    FLOGO-10808

    Summary: Flow Design page UI crashes if there is a dangling branch in the flow.

    Workaround: Export and then reimport the app.

    FLOGO-10821

    Summary: All the references matching with an activity name get updated if any upstream activity is renamed..

    Workaround: None.


    FLOGO-10834

    Summary: References are not auto-updated if a group name is updated in the application properties.

    Workaround: References need to be manually updated after renaming any group of app properties.


    FLOGO-10837

    Summary: Activities are not aligned linearly when the app is pushed from PAPI or tibcli.

    Workaround: None.

    FLOGO-11099
    Summary: Formatted Text is not supported in Notes. 
    Workaround:  Copy the text and paste it in the text editor. Then copy the non-formatted text and paste it in the Notes text area.


    FLOGO-10837
    Summary: Activities are not aligned linearly when the app is pushed from PAPI or tibcli.
    Workaround: None.


    FLOGO-10834
    Summary: References are not auto-updated if a group name is updated in the application properties.
    Workaround: References need to be manually updated after renaming any group of app properties.


    FLOGO-10821
    Summary:  All the references matching with an activity name get updated if any upstream activity is renamed.
    Workaround: None


    FLOGO-10803
    Summary: UI hangs after adding the app schema. When we click the Rest trigger, the trigger is not there after you refresh the page. 
    Workaround: Refresh the page to reload the UI. Although the  trigger added in the flow is lost. 

    FLOGO-10802
    Summary: The field with space is not working in the filter expression of the for-each function. 
    Workaround: You must insert an additional identifier ["<loopName>"] in the $loop expression. For example,
    array.forEach($activity[Mapper].output.data, "data",$loop{color:#de350b}["data"]{color}["First Name"]=="Jones")


    FLOGO-10567
    Summary: Validation error symbol is not observed at the Settings and the Input tab for an activity if we switch without closing the previous activity configuration window.
    Workaround: Close the activity configuration and then switch to another activity.


    FLOGO-10356
    Summary: Close button disappears when there are many activities open and we expand one of them. 
    Workaround: Zoom out the panel to find the close icon. 

    FLOGO-10958
    Summary: The enum value dropdown is unavailable for the array child elements.
    Workaround: None.


    FLOGO-11199
    Summary: The test result window is hidden when we open the activity assertion or mock window. 
    Workaround: Close the assertion or the mock panel of the activity,  if opened.


    FLOGO-11126
    Summary: Due to deprecation of custom access key, Modify DB service API is to be removed. Along with this the Hybrid Agent access key field from the Enable DB service API  will also be  removed.
    Workaround: None


    FLOGO-11274 
    Summary: When DB Service is enabled, a message is displayed that says that the service is disabled successfully.  
    Workaround: Refresh the page to see the DB Service enabled status. 

    FLOGO-11219
    General category activities and triggers are missing in the flows on upgrade to TCI 3.9.0
    Workaround: None

    FLOGO-11239
    Summary: Let us say there is a Flogo app with a large number of flows and activities. Enable the execution history and then, upon completion of the execution, go back to the Execution History page.  After this, open an execution instance and when we click the View Details button, we do not see the list of activities that have been executed. Instead, we see a  message that says that the Execution History is not enabled for the organization. 
    Workaround: None.


    FLOGO-11122
    Summary: If you have read-only access, the 'Navigate to subflow' icon is not visible on 'StartaSubflow? Activity tile. 
    Workaround: None. 

    FLOGO-11119
    Summary: For Read Only user and users roles, ?Open Subflow? button is not present inside the StartaSubflow activity.
    Workaround: Click the Input or Output tab and click the Settings tab. The ?Navigate to subflow? button becomes visible.

    FLOGO-11100
    Summary: References are not updated for the General category activities and triggers for the existing apps which are exported after the upgrade from PAPI. 
    Workaround: None

    FLOGO-11072
    Summary: When mapping unmapped arrays,  the 'Filter by' value gets populated in the 'Configure with Value' input mapper after clearing the source mapping and switching to 'Configure with Value' option.
    Workaround: Select a different non-array node and select the array node again.


    FLOGO-11020
    Summary: The flow note added in main flow is not there when we switch to error handler flow.
    Workaround: There are different flow notes available for Main flow and the Error Handler flow. 

    FLOGO-11030
    Summary: While creating test cases, if you change the mode from mock to assert, or conversely, the Save and Discard buttons are disabled.
    Workaround: To save the mode, you have to enter/edit the assertion expression/mock data.


    FLOGO-10961
    Summary: When a flow is copied, the notes icon is not highlighted on the copied Activities which have notes added in it. If the notes icon is clicked, it opens an additional Notes box. 
    Workaround: For the  copied Activity, the notes available on the Activity tile must be in pink colour.

    FLOGO-10888
    Summary: Unpushed apps are not getting copied from tibcli. 
    Workaround: None.

    FLOGO-10886
    Summary: During mapping of arrays, on double clicking the source array, the mapping is added in the 'Filter by' field.
    Workaround: Instead of double clicking on source node, drag the source node to update the source.

    FLOGO-10839
    Summary: During mapping of arrays, we are not able to select the 'Configure with source' option after clearing the  mappings.
    Workaround: Close the activity panel. Then, open it again and try to map the node.


    FLOGO-11262
    Summary: If we try to open the mapper activity which has an array with large records mapped with an array type, then the browser becomes unresponsive and validation goes into an Infinite loop. 
    Workaround:  Instead of using an array with large records directly into the Mapper activity input, map it with the output of some other activity.

    FLOGO-11419
    Summary: Discard button does not work for connectors where auto population is introduced.
    Workaround: Switch the tab in order for the discard option to work.

    FLOGO-11424 
    Summary: For Database connectors, the schemas having a huge number of tables and columns fails to fetch the metadata.
    Workaround: Copy and paste the query in the query editor instead of typing it manually.

    FLOGO-11650
    Summary: While dealing with an OSS activity in your Flogo app, you can update the trigger configurations with the ?Coerce with Schema? option. When you pick a configured schema, and then discard it to close the triggered configuration screen. The UI gets stuck.
    Workaround: You need to refresh the page or click the apps tab to start again.

    FLOGO-11944
    Summary: While running any test cases in unit testing mode, if you clear mappings in any flow inputs, the assertions remain the same in the flow output.
    Workaround: None


    User Feedback

    Recommended Comments

    There are no comments to display.


×
×
  • Create New...