Edit: Added a specific Use Case for clarity
Like most users I use parameters for my KWTs. Some parameters have a limited option pool e.g. paramater "WantACookie" can have 3 and only 3 values ...
You could probably get the same behavior using a table variable and doing lookups on it. Not the best way, but would do as a workaround.
Agreed. It does mean the user would have to create a data table for each of these "Enum" data objects. It's a bit of a two ways to skin a cat scenario. Not all users are comfortable with writing scripts. Where I work, the product consultants write KWTs. They wouldn't even be expected to do more than record an on-screen test. They are the same users who won't be comfortable with using datatable objects as enums and doing lookups from them. They are happy to create an onscreen action in the visual editor though. The next level up is parameterising that recorded KWT There are places where it is just more convenient to use the visual editor e.g. Create a small, compact KWT with 3 parameters that does repeating tasks e.g. populate the same three comboboxes on a page but with different values. A sub-function of a sort that I can drag into my current KWT or event run from a script. This could be a created as a script, yes, but to call the script I still need to forward the parameter value to the script. Now if that was just the value of an enum from the parameter supplied to the KWT that would be easier for non-power users and small little units.