variable sets

[Espina_04]

Do you find it easier to create variable sets for catalog items? We have 2 SMEs and each develops in their own way. One does not like to use them as much as the other. As a recent ServiceNow team member (we implemented a year ago, Sept), I am trying to use the simplest most elegant solution. Would really appreciate all opinions.

[DrewW]

We use variable sets only for variables we know are going to be common with more than one cat item.  Which means you need to have some standards and knowledge of other cat items that have been built.

One Example is we have 5 cat items for getting/returning a computer.  About 80% of the vars are used in one or more of those items.  So those we put in several different Variable Sets and the rest we did not.

[GlideFather]

Hi @Espina_04,

I believe there's no universal answer...

However if you have items with different variables, then variable sets make no sense, but if you have some variables that are reused (additional comments, requested by field etc) - it is so much better to do the VS because on that you can apply attributes on their behaviour - mandatory, read-only, hidden, or default values etc.

Variable set is to avoid creating the very same variable again and again while it already exists...

[Nikhil Bajaj9]

Hi @Espina_04 ,

It is a personal choice but best practice (Undocumented) is - if you have few common variables throughout all catalog items ex:- Requested For, Requested By etc then definitely Varaible set will be useful as it will help reducing the work and can be reused. If not many variables are common then you can avoid update sets.

If my answer helped you, please mark it- solution accpeted.

Regards,

Nikhil Bajaj

[Rafael Batistot]

hi @Espina_04 

My opinion about the theme 

1. Use variable sets when:

   • The variables will appear in more than one catalog item now or in the near future.

   • You want to enforce strict consistency in behavior or validation.

   • You need to group variables logically for better catalog item maintenance.

2. Use standalone variables when:

   • The field is truly unique to a single catalog item and unlikely to be reused.

   • It’s experimental or one-off.