Skip to Content

Release notes for Jitterbit Wevo iPaaS

Overview

Wevo iPaaS is Jitterbit's integration platform for Latin America (LATAM), accessible at https://app.wevo.io/. The version of Wevo iPaaS is updated automatically. Each version number corresponds with that of a Harmony release (Jitterbit's global integration platform).

You can sign up for Wevo iPaaS release and maintenance notifications at Jitterbit's system status site by subscribing to LATAM Wevo iPaaS components.

Releases

11.45

June 18, 2025 (7 - 11 PM BRT)

Enhancements

  • On-premise agents have improved logs for tracking and better analysis of problems, including identification in the application ID logs, and in some cases IP and port logs, to know which host/port is unstable and affecting other applications.

    Note

    To install this update, contact Jitterbit Support.

Fixes

  • The Builder > Templates page now loads all templates as expected. Previously List not found was sometimes being displayed.

  • The Data Types page has these fixes:

    • A bug that prevented saving after adding a new column to a data type has been fixed. It is now possible to add and remove columns without any errors.
    • An issue where the Text Qualifier value was not being persisted when the delimiter type was set to Other has been corrected. The value is now properly saved and restored when the configuration is displayed.

  • During flow execution, an error no longer occurs when a Webhook trigger does not have the Prevent execution if request's body is empty option selected.

  • When there is instability in the dynamic accounts update routine, it now tries to recover. In addition, internal cache update failures are prevented from impacting future executions of flows that use dynamic accounts.

11.44

May 29, 2025 (7 - 11 PM BRT)

Enhancements

  • The Builder > On-Premise Agent page now has the option to view the flows for a specific application. This provides more refined visibility and control over flows associated with on-premise agents by application.

  • The SOAP connector has the following enhancements:

    • The Invoke in batch parallel action has a new Delay between calls (ms) parameter in its Configurations tab.

    • The Invoke in batch parallel and [Invoke] Invoke Method in Batch actions no longer show the Use Custom Header parameter. This parameter was previously unused; its removal does not affect the use of custom headers.

  • The IBM MQ connector's polling trigger is now designed to recover on its own in case of interruption.

  • The ProcessQueue pages are accessed at a new URL path containing /processqueue/ in place of /iomanager/. If attempting to access the former URL path (now deprecated), you will be redirected to the new one, retaining correct parameters.

  • The process queue option Send to Email now generates two layers of ZIP files that must be decompressed to extract the CSV data files. The changed structure is described here.

    Important

    The changed file generation structure is being applied on a tenant-by-tenant basis as communicated directly.

Fixes

  • When registering an on-premise agent application, an issue no longer occurs where users could create multiple applications simultaneously, without waiting for the previous one to finish saving. This could cause duplicate entries or unexpected overwrites of existing applications. Now, the system ensures that only one application save operation can occur at a time, preventing conflicts or data corruption. This increases reliability and consistency when managing application data.

  • When searching execution logs in a flow using the Loop tool and the searchable value is in an action that is within the loop scope in a specific iteration, the loop iteration link now goes to the correct loop iteration.

  • In the Enqueue Items tool's Configurations tab, the Process Queue field's shortcut now loads the process queue as expected.

  • A user's Last login date shown in the Manager > Accounts > Users page is now accurate.

11.43

May 7, 2025 (7 - 11 PM BRT)

Enhancements

  • The ProcessQueue connector has a new v2.0 version of the Change Status action that performs status changes more efficiently, with a performance gain of almost 90% and 9× faster speed.

Fixes

  • The Salesforce Marketing Cloud connector now allows users to map the input for the [Data] Send Data Extensions action. The action input fields are now displayed in the action's Mapping tab and support mapping the input in Direct, Function, and Dynamic modes.

  • The Flat File connector's Write Flat File action now works as expected.

11.42

April 16, 2025 (7 - 11 PM BRT)

Enhancements

  • The following module applications now use the new Message Broker (High Availability) cluster:

    • Dealer
    • Process Queue
    • Metrics
    • iPaaS Integration Engine modules

Fixes

  • The structure of the VTEX connector's Send Specification action no longer includes the erroneous field OutputStatus.

  • The following MySQL connector actions now generate the correct SQL query based on the input provided:

    • [Query] Upsert Row
    • [Query] Update Rows
    • [Query] Upsert Rows in Batch

  • The count of the pod quantity and pod types on the Flow Monitor and Dashboard screens is now accurate.

  • The following fixes have been made related to flow versioning:

    • Attempting to create a new version of certain flows no longer results in an error.
    • Attempting to remove a flow version no longer results in an error.

11.41

March 26, 2025 (7 - 11 PM BRT)

Enhancements

  • The Oracle Database connector has a new trigger, Watch changes in a table, that can be used to get new inserted or updated rows in a table.

  • The Webhooks trigger configuration dialog has a new Return raw body option in its Configurations > Advanced tab. The new option can be used to return the raw body in the webhook output to allow a hash calculation of the request body.

  • The SOAP connector has improved performance for batch processing.

  • The algorithm for exporting and importing flows has changes that improve the performance and security of the platform.

    Breaking changes to exporting and importing flows

    If you have any flow export files created prior to this release, you will not be able to import them after this release.

    We recommend importing any pre-11.41 export files before March 26, 2025 to avoid any impact on your work.

    Once the 11.41 release occurs, you will be able to export and import flows created after this date.

    If you have any questions, contact your Customer Success Manager (CSM) or LATAM Support.

Fixes

  • An issue has been resolved with dragging a flow from a folder to the root level in the flow monitor.

11.40

March 5, 2025 (7 - 11 PM BRT)

Enhancements

  • To prevent system overload and improve performance, a default limit of 10,000 iterations is now imposed for loops within the same flow execution. Existing flows that have been turned off and on again will also be subject to the new limit. A specific loop can be exempted from the limit by configuring it using a new checkbox in the loop's configuration dialog. The default limit can be changed by contacting your Customer Success Manager (CSM) or LATAM Support.

Notices

  • In the upcoming 11.41 release (March 26, 2025), we will be making breaking changes to the algorithm for exporting and importing flows to improve the performance and security of the platform. If you do not use this feature, you can ignore this notice.

    Upcoming breaking changes to exporting and importing flows

    If you have any flow export files created prior to the 11.41 release, you will not be able to import them after the 11.41 release.

    We recommend importing any pre-11.41 export files before March 26, 2025 to avoid any impact on your work.

    Once the 11.41 release occurs, you will be able to export and import flows created after this date.

    If you have any questions, contact your Customer Success Manager (CSM) or LATAM Support.

11.39 patch

February 18, 2025 (6 - 8 PM BRT)

Fixes

  • To improve user experience when searching execution logs that have a large payload, the highlighted log result now returns a truncated body.

11.39

February 12, 2025 (7 - 11 PM BRT)

Enhancements

  • Scope log processing is now isolated from main flow executions. This improves the user experience when viewing flow logs. This isolation prevents scope logs from impacting and delaying the processing of main flow execution logs.

  • Audit and Notify module applications now use the new Message Broker (High Availability) cluster.

  • The platform's cache database service has been upgraded.

Fixes

  • Platform log audits are now recorded in the correct database. Previously, some backend audits were recording data in the legacy database.

  • When the new functionality of editing flow pods is enabled, the audit log is now recorded when the user edits the fields pod type and pod quantity.

  • In the VTEX connector, the OrderItem.PriceTag.Value property of the Order class has been changed from int to long. This resolves an issue where the OrderItem.PriceTag.Value field of the Order class was exceeding the limit, which impacted the activity of getting the order by ID.

OSZAR »