Catalog Items

Creating a Catalog Item

Catalog items are created in Service Catalog → Manage → New Item. The item wizard guides you through general information, variable definition, workflow configuration, and approval chain setup. Items in Draft state are only visible to administrators until published.

⚙️ Minimum Requirements

DynamoDB: StackFlow_CatalogItem with GSI on categoryId and status
Workflow: Each catalog item must reference a valid workflowId in StackFlow_Workflow
Role: Creating/editing catalog items requires itsm_manager or super_admin JWT claim

curl -X POST https://your-instance.stackflow-tech.com/prod/api/catalog/items   -H "Authorization: Bearer $ADMIN_TOKEN"   -H "Content-Type: application/json"   -d '{
    "name": "AWS IAM Role Request",
    "category": "access",
    "short_description": "Request a new AWS IAM role or permission",
    "fulfillment_group": "Cloud Operations",
    "approval_required": true,
    "approver_type": "manager",
    "sla_hours": 24,
    "auto_fulfill": false
  }'

Item Versioning

Every save to a published catalog item creates a new version. The version history is accessible from the item's detail page. Open RITMs always use the version of the item that was active when the request was submitted, ensuring consistent fulfillment even when the item is subsequently updated.

Breaking Changes: If you need to make a breaking change to a catalog item (e.g., removing a required variable), create a new item with a new name rather than modifying the existing one. This prevents confusion for users with in-flight requests.

Publishing and Retiring

State	Visibility	Can Submit
Draft	Admin only	No
Published	All authorized users	Yes
Retired	Hidden (existing RITMs still visible)	No

Item Templates

StackFlow ships with 40+ pre-built catalog item templates covering the most common IT service requests. Templates can be imported into your tenant and customized from Service Catalog → Manage → Import Templates. Templates include variables, workflow definitions, and fulfillment tasks pre-configured following ITIL best practices.

Best Practices

Keep catalog item names user-friendly — write for end users, not IT staff. Use plain language ("Get a new laptop" not "Hardware Asset Provisioning Request"). Include a clear description of what the user will receive and how long it typically takes. Set realistic SLA targets and publish them in the item description so users have appropriate expectations.

← Previous

Catalog Overview

Service catalog architecture

Self-Service Portal

End-user portal experience