overview creating a catalog item in servicely is an easy and quick way to gather structured information for any type of record within the platform most commonly, catalog items are used to create work records (e g , itsm request docid\ hy hagjblrwwuaboqprcm ) with additional information to ensure the record can be addressed quickly and efficiently creating the catalog item log into your instance as an administrator catalog item development should be done in a subproduction environment within change sets docid\ n2uudis1ndtpjcmol2i1n to ensure migration between environments effectively type "catalog item" click on catalog items click on new to create a new catalog item populate the form to specify the catalog item's parameters the name field will be shown to end users, and is indexed for search the category field allows you to specify where in the portal catalog categories docid\ yfanvbo dgmdsqhojcqbq the item will be visible provide a summary this is visible on the catalog item form specify the target table this is what record will be created upon the submission of the form in servicely, catalog items can create any record! poplulate the name field this is the form on the record that will be populated with the catalog item's name in our example, this will be "change home address" as set in step 5 when finished, hit create to create the catalog item creating catalog item questions questions allow us to capture the specific information we need to automate or resolve the catalog item without needing additional details in follow up messages on the catalog item, click new under the question items provide the question with a unique name this is the system name, and is used for any conditional logic or complex scripting provide the question iteself this is the question that is visible to the end user specify the question type in this example, we want to populate the field with the user who is submitting the quesiton, so we select the reference field type we can use the additional options under the field type to describe the fields behaviour should it be readonly , mandatory , or invisible to the user (helpful for scripting)? for the reference field type, pick the table we're referring to determine how we're going to populate the record our questions can be stored directly as question answers against the record, or we can populate fields on the record itself in this example, we want the user who the form is being submitted for to be the requested for on our hr case record question data can also be defaulted we can populate a default field for any of the question types reference fields against the user table can also be defaulted dynamically from a function, meaning we can pre populate the field to be the current user when finished, click create the populate the question repeat for each additional question previewing your catalog item upon completion, ensure you hit save & stay to commit the changes to the system to preview your catalog item, click the preview button