2024

Display of a yellow alert icon on inactive steps within For Each in a Diagram-type flow

We fixed an issue that occurred when trying to import a valid OpenAPI 3.0.0 file to create a REST API connector.

We fixed an issue where, during the redeployment routine, flows with environment variables did not preserve the data of these variables.

New Camel components released

Release of the EIP Process

We fixed an issue that occurred when deploying a flow with an empty file in the Resources folder.

We fixed an issue where some integrations would remain with the "Deploying" status due to duplicated scripts in .yaml files.

We fixed an error where, in a flow containing a For Each within another For Each, the iteration over items in the second list was not occurring correctly.

We fixed an issue related to the use of the HTTPS component in integration scripts that required a trailing slash (/) at the end of the URI for validation.

We fixed an error that occurred when executing a Diagram flow with the JSON Transformation v2 step, where JSONata could not locate the file containing the JSONata script.

We fixed an issue where edits made to a script in a Source flow were lost in the following scenario:

We fixed a bug that occurred when creating an instruction for a database connector, which used properties received from the REST trigger. The bug also affected other technical connectors, as well as data mappings for traditional REST connectors.

We fixed an issue where, when using the “Concat” function with the full payload in a connector data mapping, the system was altering the content format instead of preserving it in the original format (JSON).

Adjustment of the "fit view" button in the visualization of steps in a subflow

We fixed an issue where, when performing a search on the Executions screen using filters, the previous search was not cleared when clicking CLEAR. Now when clearing the filters, the previous search will be correctly removed.

We fixed an issue in which we changed the environment variable values at deployment time, but the new values were not applied.

Display of EIPs To, ToD, and Wiretap when no component is specified in the URI

Display of the Direct EIP in diagram view mode

New connector

We fixed an issue where expressions with line breaks used in the data mapping of a connector were improperly treated as invalid.

Display of the doTry EIP with doCatch and doFinally in diagram view mode

Display of the Multicast EIP in diagram view mode

Error message about inserting query parameters in the URI

We fixed a problem that was preventing the validation of scripts referencing resources, resulting in errors.

Compatibility of Diagram-type flows with Camel-K 2.4

We fixed an issue where, when creating a Source-type integration, the absence of a slash in the URI of the REST trigger caused the generated URL in the deployment to not display the integration route. Now, it is possible to register an integration without a slash in the URI, and the URL will show the address with the complete route.

We fixed an issue that caused an error in the HTTP validation of a component when adding a variable in the integration script.
Now, the URI specified by the EIP toD can reference previously configured properties without errors.

We fixed an error that occurred when validating a script in which the user was using fields that were not compatible with Camel DSL.

Display of the Choice EIP in diagram view mode

Display of EIPs with subflows in diagram view mode

Error message in YAML syntax

We fixed an error that occurred when creating and saving an integration with the Timer component. Previously, the validation of the main.yaml file indicated an error in the period property in the bean, preventing the process from completing.
Now, the validation is working correctly, allowing integrations to be saved without issues.

We fixed an issue occurring in Diagram-type flows, when using the For Each tool. When adding any connector within a For Each, the screen would turn blank, the added connector would disappear, and the integration page would reload.
This functionality is now working correctly.

We fixed an issue where the validation feature of the main.yaml file did not accept dynamic parameters in the toD component, resulting in incorrect errors.
Now, the parameters will be accepted, ensuring that valid codes do not generate errors.

New Camel component released

Visualization of Source-type flows in diagram format

We optimized the update time of the integration deployment status, speeding up the transition from “Deploying” to “Error,” which previously experienced delays.

New expression languages available

We fixed an error related to the validation of cron expressions that occurred due to discrepancies between the validation libraries in the front-end and back-end. To configure a cron expression, access the page Scheduler Trigger.

We fixed an issue that occurred during the deployment of a Source-type flow when environment variables were missing double quotes (").

We fixed an error that occurred when saving a Source-type flow. The error was related to the use of the JSONPath expression language and returned status code 3001 without specifying the error in the structure. Now, the product explicitly indicates which error in the code structure was identified, allowing the user to adjust the configuration before saving the integration.

We fixed an issue where, when deleting the content of a Source-type integration and saving it, the operation returned a 200 status code, but the file was not saved correctly. Now, the file is saved even when empty.

We fixed an issue where a deployment was recorded with the status DEPLOYMENT_REQUESTED even when the request had not been sent to the data plane.

We improved error handling for integration files with invalid formatting. Now, the system will display a warning indicating that the file is not in the expected format and will mark the flow as inconsistent, allowing for more efficient correction and preventing unexpected failures.

Viewing execution logs of Source-type flows in Sensedia Analytics

We fixed an issue that occurred when deploying a Source-type flow, where the trigger’s parameters were lost in the script. Now, they are correctly preserved, ensuring the expected integrity and functionality of the flow.

We fixed a timeout error that occurred when performing a search on the Executions screen. Now, if the filter returns more than one hundred thousand records, a message will be displayed requesting the refinement of the search criteria.

New Camel components released

Previously, when adding a new step to the canvas, it was always inserted in a default position, regardless of the flow’s arrangement. Now, when you add a new step, it will be positioned in the center of the screen, facilitating immediate visibility and improving usability.

We fixed an error that prevented saving the OAUTH2 - Client Credentials authorization update.

New connectors

New general tool

We fixed an issue that prevented saving an integration flow with the step Choice v2. This problem occurred in the Input Data field in Choice v2 when selecting a step named with certain special characters, such as the hyphen "-".

Get to know the interface and screen elements.

Follow the step-by-step guide to create and deploy an integration flow.

Learn how to build routes with Camel: components, EIPs, and restrictions.

See examples:

For Each request logs visualization

New connector

New connector

New connector

JSON Transformation and Choice v2 request logs visualization

New connector

REST trigger request logs visualization

New connector

For Each

Connectors

Connector request logs visualization

REST API connector

New general tool

New connectors