Can I use decision table alternative to creating custom table?

[kmrudulanayak]

I have a catalog item where I have a question of list collector type with 7 choices , Can I use decision table just to store and get choices on form instead of creating custom table, since list table is mandatory field to select for list collector variable type.

[Abhay Kumar1]

@kmrudulanayak In ServiceNow, list collectors do require a table to fetch choices. However, using a decision table directly for list collector options in a catalog item form is not feasible because decision tables are intended for evaluating and returning decisions or outputs based on specific conditions rather than acting as a source for list choices directly.

If you want to avoid creating a custom table just to hold the choices for the list collector if not having huge list of choices then.

[kmrudulanayak]

@Abhay Kumar1 Thank you for quick response. My requirement is just to store and fetch the choices and there is no evaluations/decisions. Considering licensing cost involved with custom table creation, I was asked to look for decision table options for this, if this is not feasible do you have any alternative option that I can try or do you think creating custom table is best option?

[Abhay Kumar1 · Accepted solution]

@kmrudulanayak System Properties (sys_properties table): If you have a small number of choices.

Or Choice Lists on Existing Fields: You could consider using choice lists on fields within an existing table if there’s a relevant place to store this data. This would let you maintain a list of options without creating a new table.

Or one of the best option, create a select Box type variable for your catalog item and either add question choices in related list of that variable or add client script for the same, if fits in your requirement.