Releases
Keep track of what is changing in the Nimbus Intelligence Connectors
Last updated
Was this helpful?
Keep track of what is changing in the Nimbus Intelligence Connectors
Last updated
Was this helpful?
Fixed issue with warehouses "randomly" crashing during data fetching without providing an error. The result could be seen in the Application Usage page as jobs that never finished, displaying a symbol.
Added various endpoints
Added support for incremental fetching on the Tickets and Changes endpoints.
Improved options to filter usage history
Stability improvements
Visual enhancements
The application now logs to the active event table on the account if it exists.
Added rows/s and estimated credit usage on the Job History for every job.
Added general application usage statistics to the Account Usage page (previously named Job History).
Added support for incremental fetching.
Fixed bug in 3 endpoints.
Rework of the Job History Page
Adding the option to set monthly schedules
Reorganized Connectors configuration in Connections, Configurations and Schedules.
Created different pages for each type of entity and functionality.
Now a single set of credentials can be linked to several Configurations that fetch to different target database/schema and endpoint selection. In turn Configurations can be linked to many Schedules that execute data fetching jobs with the specified Configuration at user given schedules.
Table Management now shows table without any latency.
All connectors allow choosing Full Refresh and Incremental Fetch methodologies. Full Refresh allows to update deleted rows from the API.
Banners are shown in the Connections, Configurations and Schedules page that allow to interact with the entities in a much easier way than in previous versions.
All connectors can be tested straight away after creating the Connections, contrary to some cases in previous versions where configuration of the Connection had to be provided before being able to test it.
Script for adding additional warehouses is also provided in the Connections page.
Schedules form has been reworked (originally Task form) and allows for more precise and granular definitions on when to run jobs. Also allows for Custom Cron schedules.
Fixed bug where some connectors would show duplicated information and/or warning messages.
Fixed bug where URLs given with trailing / would produce fails in the authentication process for some regions (e.g. Italy).
Added the ability of scheduling tasks hourly, by providing the time range (00:00 - 23:59), the hour interval (every 1,2,3...23 hours), and the weekday.
Added a custom cron scheduler as an option when configuring a task.
Several improvements on the UI and user-application interaction
Incremental fetches have been implemented. Depending on the endpoint, some data may still be fetched from the same day as the last run, since the date filters allow only dates and not timestamps.
Fixed sometimes missing recent data on incremental fetches.
Freshsales
Replaced Logs tab for a more user friendly Job History tab that shows the last 20 jobs that were executed by the application.
Fixed bug that made scheduled tasks fail just after the data fetching.
Added input field so the user can in put custom PAT server names.
Added support for incremental fetching.
General improvements in Home Page
Adding Option to Drop Tables created by the apps. Introducing a new tab.
Line Items endpoint added
Owners endpoint added
Enhanced logging messages for failed endpoint fetches.
API rate limits
API rate limits are handled and do not break the data fetching process
Fixed Categories endpoint. Sub-categories enabled.
Line Items endpoint added
Application now is stable with multiple connections.
User script now does not allow the user to introduce wrong credentials, which was breaking the behavior of future correct connections.
Front end general improvements.
Page refresh behavior improvement.
User Scripts merged into a single one.
Fixed billing bug where second (row) billing event was failing on consumer accounts.
Introduced incremental updates on most endpoints.
Changes requested by Snowflake before Public Preview.
Introduced yellow warning alerting the user that introducing a wrong OAuth 2.0 connection can trigger unexpected behavior.
Added help tooltips to script generating user-filled fields.
Added a maximum length limit of 25 characters to the connection name in the user scripts.
First release to Public Preview and review for Snowflake.
Launching with four different connectors allowing three different ways of authentication
OAUTH2
API key
Client ID & Secret
Main actions through the app's interface:
Configure multiple connections
Multiple endpoints to fetch data
Schedule a task for fetching data
Delete current connection
Drop task
Removed Refresh button from home page before running install user script to encourage the user to leave and re-open the app, avoiding known Snowflake issue.
Imrpoved logs when task fails due to known Snowflake issue.
