Updating catalog variables

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-05-2024 11:27 AM
When needing to update an existing catalog variable, being the question/label, name and type, what is the preference? Can those three properties be updated in the existing variable safely without adversely affecting requests in-process? Or is it better to create a new select box variable and just hide the existing single text field? FWIW, there aren't any catalog UI Policies, scripts, etc. acting on the field. Thanks in advance for your replies!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-05-2024 12:00 PM
Hi @Jon71
I would like to recommend creating a new Variable.
if you update the variable and if this catalog item is in production (Go Live), and if you have already requested items submitted by the clients or end users. then the data will be lost.
Thanks and Regards
Sai Venkatesh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-05-2024 12:15 PM
hi @Jon71
If you updating catalog variables in ServiceNow can have implications, especially if those variables are already being used in existing records or workflows. So my suggestion is Create a new Variable and hide the old one.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-05-2024 01:38 PM
Hi @Jon71
Updating an existing catalog variable (question/label, name, type) is generally safe if no ongoing requests will be adversely affected. If changes are minor, updating directly is efficient. For significant changes or to avoid disruptions, creating a new variable and phasing out the old one can be a prudent approach.
———————————————-
Please consider marking my reply as Helpful👍 and/or Accept Solution☑️, if applicable. Thanks!