Lets say I have a bunch of buttons each with a name that corrosponds to an enum. Liked = enum.Accepted Ok = enum.neutral Disliked = enum.negative +5 more I currently have a MF for each button, that creates a variable for the enum, then goes into a sub, and does the thing it needs to do. my quetsion, is there a way to just add the variable into the button, so i dont have to create all these MF's that pass on a variable?
Not in the button settings directly, no.
However, what’s the reason you must use buttons for the enum values? A radio button or dropdown widget would make your life way easier here.
If you really want to stick to buttons and reuse the same button with only one microflow, one could in theory render a list view that creates a non persistent object with an enum attribute for each enum value in a data source microflow and renders a button with that enum value as a parameterized caption. It goes without saying that this is obviously too complex and doesn’t really save you time or complexity either.
If you only want to show a subsection of the statuses using a radio button you have the following alternatives:
Create a separate enum that has fewer values and covert that to a another enum that has all the values in the subsequent save microflow or
If security isn't important: Use CSS' n-child selector and a dynamic class to hide the x elements so that the user can't select them. For example to hide the first value: