Release 278 - April 2024

Hello everyone

I’m excited to introduce Release 278! This release includes updates to Automations, the App Editor, and lots of UI improvements across the platform. Here are some features worth highlighting:

  • A new function {{ARRAY_VALUE_AT_INDEX}} is available in the expression editor for apps and automations
  • Ability to enable/disable region boundary drawing for overlay Vision snapshots in the app editor

There are also some performance improvements and bug fixes that were reported by users.

View the full 278 Release Notes here.

Let us know your thoughts and questions below!


Control whether operators login to the Tulip Player using SSO or Badge ID

This is already possible, so I assume the update is that you can now control this on a user to user basis? or by role? Either way, a very exciting update and it is great to see the rapid progress on the enterprise user settings front.


I’m very interested too in this feature. Could you tell us at which level this control is done: user, workspace, account level?

Hi @Nicolas and @danielpomeranz , two things for clarification:

  1. We pulled this feature from this release due to bugs that we could not squash in time. It should be in the next release, 279.
  2. The functionality is strictly for customers that use SAML. It allows you to control at the account level whether operators are able to log into the Player via SAML credentials or badge ID. So, it is existing functionality that was previously only available to Tulip support team members, that will now be available for Account Owners to toggle.
1 Like

Ok clear, existing Feature Flag that is now available on account page for us.

1 Like

Hello @tulip Team,

we and our customers have been working with the Relaese r278 for a week now and we’ve been getting a lot of questions about one new feature:

## Changes to the App Editor

We’ve re-designed the Context Pane with updated groupings for variable widgets on the App editor. This also adds a new Overflow styling (see below) section for variable widgets whose datasource has text.

The Expand styling configuration has been renamed to Overflow styling for Input Widgets. The behavior of this function does not change.

All in all, this is a good new feature, but two comments:

  1. you have simply built it into existing apps, where “gray spots” (the new scrollbars) are now appearing everywhere. So “it’s not a bug, it’s a feature”, but there are sometimes too many to adjust all these variables manually from overflow styling “scrollable” to “click to expand” (it behaves more like before the update).

  2. the overflow styling setting option for table records is completely missing. There are also now the scrollbars, but we can’t change it to “click to expand”. After your update we really need it as fast as possible.

Sometimes you have situations where, for example, you don’t want to display the time of a date/time variable or table record and then you make the field so small that it is cut off.


1 Like

Hi Jeremy,

Thanks for the helpful feedback! In response to your comments:

  1. Our app editor today has some constraints on bulk editing widgets in the App Editor. At this time, you will have to manually change the height of the widgets to remove the scrollbars from the canvas. Worth noting that our default widget size for the variable is large enough that the value of the variable when displayed in player won’t display the scroll bar if it fits within the bounding box.

App editor:


  1. This is a known bug on our side and we are currently working to add the Overflow styling section to the table record widget’s context pane.



All right, thank you Yuji :slight_smile:

1 Like