Hi there, @wordpresschef… you can do what you described by merging three filters together, however, if you create an attribute (number) on the option set and give each option a number (starting at 1 for the first option and so on), then this filter in the Default value field will do the trick.
Well, that is definitely a different question, but it’s not clear (to me, at least) what you mean by individually. Are you saying you want each user to see a different set of default selections, and if so, how do you want to define the default for each user? Is it random?
Ah, okay… now I get it. What immediately comes to mind is instead of having a number attribute on the option set as I previously suggested, have an yes/no attribute called default, and set that attribute to yes for the options you want to use as the defaults. With that attribute in place, this expression in the Default value field will do the trick.
The downside to this suggestion is if you want to change the defaults, you will have to deploy your app to live. If you don’t want to go that route, you could store the statuses in a custom data type and use a yes/no field to define the default values. Then, if you wanted to change the defaults, you could do it directly in the live database without having to deploy the app.