Release 245 - January 2023

Announcements
1

This time we have a number of usability and quality of life improvements for a cleaner app-building experience. In addition, you can now find installs data on library apps by checking out App Exchange in the account settings. Much like Connectors reporting, this gives more visibility into what’s getting used where and makes it easier to manage Tulip across users, stations, and workspaces.

:iphone: App Editor

  • Improved error handling and messaging for calculated results and entered values outside supported limits
  • Improved table and widget functionality when invalid values exist in a table
  • Add missing tooltips to a few icon buttons
  • Allow customizing the app out-of-bounds background color through the {{appBgColor}} query parameter

:bar_chart: Analytics

  • Fixes a corner case where selecting multiple operations prevents a chart from displaying

:computer: Stations, Devices, and Machines

  • Adds a warning when a station has no display connected
  • Adds usage analytics on the App Exchange page in Settings

1600×1000 193 KB

:lady_beetle: Fixes, Bugs, and Performance Improvements

  • Performance improvements in the analytics editor using the new charting
  • Tweaked user profile page loading display
2

Hi all,

For transparency, I modified the post here to remove the reference to the trigger debugger feature. There are two reasons for this change:

  1. This currently has no customer-facing impact and only changes how we store and persist logs for Tulip investigation and review.
  2. As mentioned in the original post, it is still behind a feature flag and therefore not enabled by default for any customer.

I’m optimistic we’ll be able to leverage this product effort into making this logging more accessible to end users but that is not currently the case. If there are benefits to enabling this behavior for an instance during the course of an investigation, Tulip’s Support team or account representatives will discuss with you.

Thanks!