ServiceNow Catalog Item

You are a ServiceNow platform architect specializing in service catalog design. The user wants to build a complete service catalog item with variables, order guides, fulfillment workflows, and service portal integration.

What to check first

• Verify the sc_catalog table exists and you have catalog_admin role in your ServiceNow instance
• Confirm the sc_cat_item table is accessible via REST API at /api/now/table/sc_cat_item
• Check that at least one catalog exists: navigate to Service Catalog > Catalogs and note the sys_id
• Ensure you have access to Workflow Editor (wf_workflow table) for building automation

Steps

1. Create a new catalog item record in the sc_cat_item table with name, description, and assign it to an existing catalog using the catalog field (foreign key to cmn_catalog)
2. Define variable set by creating records in io_set_item (item options) linked to your catalog item via sys_id
3. Add individual variables in the variable table, setting type (string, reference, checkbox, etc.), mandatory flag, and question_text for the portal display
4. Create a fulfillment workflow in Workflow Designer, triggered on catalog item order, with nodes for approval, assignment, and state transitions
5. Link the workflow to the catalog item by populating the workflow field with the workflow's sys_id
6. Configure the short_description and description for portal visibility, and set active = true
7. Test the item in the Service Portal by creating an order and verifying variables render correctly and workflow executes on submission
8. Enable notifications by setting up email notifications on the fulfillment workflow and linking recipient rules to the item's request table (sc_request)

Code

// ServiceNow Catalog Item Builder - Business Rule or REST API Integration
(function() {
  var CatalogItemBuilder = {
    // Create catalog item with variables and workflow
    createCatalogItem: function(catalogSysId, itemConfig) {
      var itemGR = new GlideRecord('sc_cat_item');
      itemGR.newRecord();
      itemGR.catalog = catalogSysId;
      itemGR.name = itemConfig.name;
      itemGR.short_description = itemConfig.shortDesc;
      itemGR.description = itemConfig.description;
      itemGR.category = itemConfig.categoryId || null;
      itemGR.active = true;
      itemGR.workflow = itemConfig.workflowId || null;
      var itemSysId = itemGR.insert();
      gs.info('Catalog item created: ' + itemSysId);
      return itemSysId;
    },

    // Create variables and attach to item
    addVariableToItem: function(itemSysId, varConfig) {
      var varGR = new GlideRecord('variable');
      varGR.

Note: this example was truncated in the source. See the GitHub repo for the latest full version.

Common Pitfalls

• Treating this skill as a one-shot solution — most workflows need iteration and verification
• Skipping the verification steps — you don't know it worked until you measure
• Applying this skill without understanding the underlying problem — read the related docs first

When NOT to Use This Skill

• When a simpler manual approach would take less than 10 minutes
• On critical production systems without testing in staging first
• When you don't have permission or authorization to make these changes

How to Verify It Worked

• Run the verification steps documented above
• Compare the output against your expected baseline
• Check logs for any warnings or errors — silent failures are the worst kind

Production Considerations

• Test in staging before deploying to production
• Have a rollback plan — every change should be reversible
• Monitor the affected systems for at least 24 hours after the change