What is the best practice for removing/deleting variables from catalog items?

johnnyw
Mega Expert

We have quite a few catalog items that have different variables on them.   There have been some requests to update the catalog items to remove some questions (variables) since some are no longer needed.

To accomplish this, I have been deleting the variable from the catalog item setup to keep it clean.   However, I see an issue with this since any already submitted Request Items that had this variable populated before will no longer have this variable show and will make the request item look incomplete.  

So my question is, what is the best practice for removing any catalog item variables that are no longer needed?

Thanks,

Johnny

14 REPLIES 14

seanbracebridge
Kilo Expert

Set those variables to Active = false


I tried it and it still shows the field and data on the old Tickets while it no longer appears on the new tickets.



Please tell me how it turns out.


Thanks Sean.   I will try this solution.



Do you know how to set specific values for a multiple choice variable to be inactive?   One of our requested changes is to disable a multiple choice option.   I don't see 'Active' as a field on the question choice form.



Regards,


Johnny


Hi Sean,



I just tested making variables Active = false that I wanted to disable and it looks like previously submitted RITMs with this variable populated retain the information.   That is great thanks!



I still do not see a way to disable specific multiple choice variable options though.



Regards,


Johnny


If you mean you are removing the multiple choice variable itself it should be there, If not, you should add it on the form.



If you mean the choices itself on the multiple choice variable then you might not have one. You may want to start adding a field called 'Deactivate' or something of the like and then create a policy or a script that hides the choice. I am just not sure if this does not affect older tickets.



Please tell me how it works out.


Sean, I did mean the choices itself on a multiple choice variable.   I did more searching on the community and found several people with the same issue with no solution.