Creating a Dynamic Catalog item

[eddiemorgan]

Hi All,

I am new to ServiceNow Administration, and one of my first projects is to streamline a process with a new catalog item.

We have a process where staff are allocated to rooms using codes. These allocations need to be changed fairly regularly (staffing changes, regulation changes, room occupant preferences, etc), and the current way we receive the requested changes is through generic RITMs with Excel or Word attachments.

What I would like to do is:

- User opens form

- Q1: Location (dropdown from list of all locations - create a table?) - ideally, this would also auto-select based on the location on the user's account.

- Q2: Sub-location (dependent on the answer to Q1 - sub-tables of table for Q1?)

- Q3: List of codes (dependent on the answer to Q2) with a radio multi-choice of rooms (also dependent on Q2). The idea is that they do a current state and then a future state for each code.

So based on this, I have several questions.

1. Is this possible? (We are on Zurich 7 and have ITSM Pro)

2. Assuming I need tables for the variables, am I able to create/update tables using CSV imports?

3. Is there a better way of doing this than the way I have described?

Happy to provide more info if needed 🙂

Thanks!

[brianlan25]

I have questions about Q3. You codes list of code but then you say with radio multi-choice. Do you want them to be able to select multiple codes? If so you cannot use multi-choice variable you would need a list collector variable and the data would also need to be in a table.

Yes you can update update tables via a CSV. There is the import set functionality.

[AlpUtkuM]

Q1) If I would be you, I would create a reference variable on the catalog Item to indicate user (such as user name) who is filling the form out. Then, you could create location reference variable as well to auto populate It. Check this please : https://www.servicenow.com/community/itom-articles/auto-populate-a-reference-variable/ta-p/2325319

Q2 and Q3) I would create a custom table extending from "dl_matcher" table. You could create table fields as location, sub location and list of codes. Location and sub location fields should be choice and list of codes should be list type of field on the table. Afterwards, you could create Data Lookup Rule(s) to apply on your catalog Item. https://www.servicenow.com/community/itsm-articles/service-catalog-data-lookup/ta-p/2300091