2023 release notes

A Full Screen option has been added to the end of the following flow sections to allow the user to open that section in full screen mode:

The GET v2/flows/:id now accepts the query parameter include with the following values;

In this release, when a customer subscribes to flow error emails, the included link will redirect to the corresponding thread for component errors and the corresponding container for container errors.

This release introduces significant enhancements, including:

The Dashboard is now enhanced to provide a more useful and intuitive selection of information regarding integration flows, executions, and errors.

Clicking the workspace name in the Workspace Memory Usage list on the Current Month Quota page will now redirect the user to the corresponding workspace’s Dashboard.

Configuration screens for the Content-Based Router have been changed to React. Users can now map values from previous steps for evaluation.

A new Sailor version has replaced jakarta.json with org.eclipse.parsson.

As a part of our ongoing platform optimization and extending its capability to withstand a high load, we have removed the Runlog and implemented a new "Containers" page to display related information. This change does not reduce the amount of logging information available to you. Instead, it increases the information available for error handling and debugging while increasing the platform’s efficiency.

We implemented new menu Containers under the Analyze section. The new page, Containers, will display information about containers and components inside. The main page displays logs for "Today" by default, and users can extend the date range by the filtering and Search fields. The container logs save up to 30 days. The Containers page displays the following States:

As we deactivated the data messages processing in the lookout, we created a new data source Clickhouse for Dashboard.

We added a new node_config option, consume_raw_data, into the Flow’s attributes as a configuration option. This parameter configures the parsing behavior in the webhook step. The webhook step receives an input message in the raw structure if selected.

Some Instagram services use unusual authorization schemas, so we added a New Auth Client Type, oauth2_instagram. In the component.json of the REST API V2 component, you need to define the scopes because OAuthFieldView does not allow you to specify it in credentials. For example:

"authClientTypes": [
  "oauth2_instagram"
],
"credentials": {
  "fields": {
    "auth": {
      "required": false,
      "viewClass": "OAuthFieldView"
    }
  },
  "oauth2": {
    "scopes": ["user_profile", "user_media"]
  }
},

We applied a new design to the Summary tab on the Flow-Designer page and transferred it from ember to react.

This release adds the Step Name column next to the Flow Name on the Logs page. This makes it easier to isolate relevant logs during troubleshooting.

Recipes can now contain the declarations.topics property with a list of pub-sub topic declarations. Users can define a topic ID in the same way as for credentials in the flow template. Upon activation of a recipe that contains topic(s), we create the required topic(s) in the corresponding workspace.

We have migrated the Settings and History tabs of the Flow Designer page to React. In addition, the platform saves any setting changes once you click outside the focus area. Alternatively, you can still click the Save button at the top right.

Changes to the cron scheduling of a flow are now saved automatically instead of requiring users to click the Save.

The Implement screen displays the flow definition. This screen is now updated to our new style and will be more responsive.

We enable option alwaysFakeOptionals and disable fillProperties in the json-schema-faker library, which is used by the Generate Stub Sample button on the UI.

Additional sporadic bugs related to 'hanging' or not starting flows are also addressed with this change. Clients using outdated components may still experience sporadic issues. These issues will be resolved by updating to the most recent versions of the connector.

A bug prevented CamelCase and UPPERCASE word searches from working on the logs page. Search functionality on the logs page is now case-insensitive.

A bug returned irrelevant search results if the user started searching immediately after the Flows page loads. This bug has now been corrected.

A bug caused the queue reader to sometimes miss changes in the state of thread queues. This bug has been resolved.

We continue to improve our flow designer Page. When you create or change a flow, you will notice a new, more uniform design with components of the flow displayed inside squares instead of circles.