Please fix and enhance the expression editor in "Enabled state"

The expression editor in “Enabled state” is unfortunately somewhat buggy and misses some functionality:

  • It frequently looses focus and closes without saving what you entered

  • References to variables are called differently, why? In button triggers, a ref to a variable in the expression editor is established with “@Variable…”. Here this is changed to “@Variables…” making it incompatible to copy and paste…

  • The reference to the current active user is missing from the command list. It would be very nice, especially should the custom user group handling finally lands, to be able to enable/disable a button directly from here without the need to additional helper triggers on step entry. Currently I need to load the current user into a table placeholder pointing to the user table and go from there. E.g. I would like to enable certain buttons only IF the user belongs to a certain user group, like shift supervisors.


Btw.: You can vote your own suggestion as well.

1 Like

The Expression Editor refreshing after about 20 seconds is extremely annoying.

Hi @sebme and @jmurray , thanks for reporting these issues with the expression editor. Our team noted this in our system and hope to resolve it soon.

If you run into any other issues with the expression editor, we’d love to hear it. Please feel free to continue sharing here in the thread.

For what its worth, I just wanted to note that this functionality is an incredible step forward for the platform and I am sure some of the bugginess will be cleaned up soon. Being able to control app logic live with expressions is a game changer and gets me really excited for a future where we will be able to define variables based on expressions (and maybe even table records one day). My apps are simpler now and that is a huge win for long term sustainability of complex applications.

Let’s be sure to share our excitement with the Tulip team too!

1 Like

As an LTS user, this is definitely something I’d like to see included in a point release. It severely detracts from the usability of the feature. It’s not a loss of existing functionality, but the ability to use this was a primary part of LTS12 so having it randomly stop working with no apparent deterministic cause is not great.