Release Version 2.11
On This Page
The content on this site may have changed or moved since you last viewed it. As a result, some of your bookmarks may become obsolete. Therefore, we recommend accessing the latest content via the Hevo Docs website.
To know the list of features and integrations we are working on next, read our Upcoming Features page!
In this Release
New and Changed Features
Destinations
-
Improved User Assistance while Configuring Destinations
-
Provided an information banner listing the prerequisites when a user enables the Connect Through SSH option. It helps users ensure that they do not miss any of the prerequisites required for a successful SSH connection.
This change is applicable to all Pipelines created from Release 2.11 onwards.
-
Sources
-
NetSuite SuiteAnalytics as a Source
-
Integrated NetSuite SuiteAnalytics, a reporting and dashboard solution that provides built-in, real-time reporting, searches, key performance indicators (KPIs), and dashboards.
To use this integration, you must obtain the API credentials from the NetSuite SuiteAnalytics account where your data resides. The API credentials are used by Hevo for authentication.
Read NetSuite SuiteAnalytics.
-
-
Salesloft as a Source
-
Provided integration with Salesloft, a cloud-based sales engagement platform that provides sales teams with the tools and technology to improve their sales process and increase revenue. Hevo uses the Salesloft API to ingest data from your Source.
To use this integration, you must generate the API keys in the Salesloft account from where you want to ingest the data. The API keys are used for authentication by Hevo to access the data.
Read Salesloft.
-
-
Support for Additional Fields in the Conversation Object for Intercom App
- Added support for ingesting the source_author_email, delivered_as, and redacted fields in the Conversations object. The additional data ingested in these fields enables you to better understand a conversation. This change is applicable to all new and existing Pipelines. For existing Pipelines, Hevo ingests only the incremental data for these fields. To ingest historical data, you can restart the historical load for the object.
-
Support for AWS OpenSearch as a Source through AWS Elasticsearch
-
Introduced support for AWS OpenSearch as a Source (till version 1.3) via the Elasticsearch Source configuration user interface. You can select Elasticsearch as the Source while creating your Pipeline and provide the OpenSearch credentials. Hevo automatically identifies the Source type based on the credentials and allows you to create the Pipeline with the correct Source.
Note: For OpenSearch Pipelines, the user interface will display AWS Elasticsearch logo.
-
User Experience
-
Enhanced Global Search Functionality
-
Improved the global search feature to make it more responsive. The default search pop-up window now displays two panes. The left pane displays a snapshot of your most recent work, for example, your Pipelines, Models and Workflows, as used to happen previously. You can now click on any of these to view their key details, available actions, and related documentation on the right. You can also open their detailed view from the right pane.
In addition, you can search for and configure any unused Source or Destination from the search results window.
-
Fixes and Improvements
Sources
-
Added Open Authorization (OAuth) Connection Support in Criteo
-
Added support for Open Authorization (OAuth) to authenticate your Criteo account with Hevo. This allows you to configure your Criteo Source without obtaining the Client ID and Client Secret.
Read Criteo.
-
-
Improved Handling of Column Names with Reserved Keywords for RDBMS Sources
- Fixed an issue where Hevo did not ingest data for columns with reserved keywords in their name, such as SELECT, ALTER, and ADD. This fix applies to all new and existing Pipelines created with any variant of MySQL, Oracle, PostgreSQL, Redshift, and SQL Server Sources.
-
Optimized Data Ingestion for HubSpot
-
Fixed the following issues relating to ingestion for objects having more than 10,000 Events:
-
As HubSpot imposes a limit of 10,000 records per API call, Hevo was switching to Full Load mode for ingestion if the object had more than 10,000 Events. However, it was not able to switch back to timestamp-based identification of incremental data in subsequent API calls. This was leading to high Events usage.
-
If an object had more than 10,000 Events with the same timestamp, full-load ingestion was going into a loop as Hevo was unable to identify which Events had already been ingested.
-
-
-
Support for all Form Types in HubSpot
- Fixed an issue where non-HubSpot forms were not being ingested by the Pipeline, which was causing a mismatch between the the Source and Destination data. To ingest the data for these forms in an existing Pipeline, you must restart the historical load for the Form Submissions object.
User Experience
-
Enhanced Content for Pipeline Objects
-
Improved the content for Pipeline Objects by:
-
Adding detailed information about each action that can be performed for an Object
-
Segregating the information for SaaS versus RDBMS Objects
-
Read Managing Objects in Pipelines and its sub-pages.
-
Documentation Updates
The following pages have been created, enhanced, or removed in Release 2.11:
Activate Warehouses
Getting Started
Introduction
-
General FAQs
- Does Hevo provide APIs for automating Pipeline operations? (Removed and the content merged into Pipelines)
Pipelines
-
Examples of Python Code-based Transformations
-
Managing Objects in Pipelines (Renamed)
-
Transformation Methods in the Event Class
Sources
-
NetSuite SuiteAnalytics (New)
-
Salesloft (New)