I have a button that clears the variables so operator can have a clean start to input values into variables in a step. For the button I need to have one action for each variable to clear. For this one step I have more than 20 variables and therefore 20 actions in that one trigger. Very tedious to type essentially the same action numerous times with the only difference being the name of the variable.
It work help if there was a feature instead of clearing just one variable we get a listing of all the variables and we get an to “select all” or select/deselect individual variables to clear. This would be similar to excel data list when you want to filter the data set in a column using the DATA/Filter feature and I get to pick what I want to filter by. In Tulip case, it would be which variables I want to clear.
Hey Attaboy, I think in many cases like this people just restart the app (which can be done with a trigger), or “complete” the app. Do you have many other variables that you don’t want to clear? Or if it is only a few that you don’t want to clear it might be easier to just reinitialize them at the top of the app
I had the same thought as Attaboy, and this solution addresses my use-case.
It would still be nice to be able to group variables in folders like we can group steps, that way we can reset only one folder. Plus it has other uses beyond only resetting.
Thanks for this, it’s an interesting idea! Can you give some examples of groups you might want to create? I’m particularly curious about the difference between variable folders and object variables that allow multiple properties.
I think the fundamental problem with object variables - as they could very much act like a variable group - is that in the current Tulip environment it is almost prohibitively difficult to add changes to them once an app has been built.
Linking to any property in an object freezes the object. Say you want to add an additional property later on, you would have to break everything in order to do so.
Offering groups of variables instead could be a way to solve that problem and the original one of this post - if they are not locked in.
Or you find a way to enhance the object type in Tulip to make it more user friendly. As a programmer I would use objects every time. But working with them in Tulip is a pain in its current form. Even more so with object arrays as there are important service functions missing.
Aditionally objectlists from a connector output can’t be part of the “folder” object.
I would also like to be able to have the “set to default value functionality” to some variables but not all.
Currently there is a “Reset all App Variables to Defaults” Action. However I’d like to save some Variables from that. I want to set one variable or a group of variables back to default.
This would totaly make sense, to select multiple variables as a target of one data manipulation (no matter if clearing, initializing, incrementing, writing a static value, setting to default…).
@sebme and @thorsten.langner, these are really great insights , thanks for sharing! Over the next year we’re doing a lot of foundational work on how we structure and process data across the platform, so any and every perspective you share goes a long way toward building the best possible platform.
