One workflow for 1,000+ catalog items

Up to 20 developer hours a month back, and routine catalog items handed to Tier 1 support.

Role: Workflow design · Platform: ServiceNow

Dynamic catalog workflow: before and after Before: one workflow per catalog item, around 200 and growing, each taking about a day to build plus testing and each maintained separately. After: one master workflow reads an approvals table and a tasks table at runtime. More than 1,000 catalog items run on it, routine items are created by Tier 1 support without development, and it saves up to 20 developer hours a month. BEFORE One workflow per catalog item, about 200 and growing catalog item its own workflow • About a day to build each one, plus testing • Every workflow maintained separately HOW Move the logic out of workflows, into data Few platform options existed, so the team designed its own runtime approach and refined it over time. AFTER One master workflow, configured by data 1,000+ catalog items Master workflow Approvals table Tasks table read at runtime 1,000+ catalog items on one workflow Up to 20 developer hours saved a month Tier 1 support builds routine items

Context

Every catalog item had its own workflow. There were around 200 of them, and the number kept growing.

Problem

Each new item took about a day to build, plus testing on top. Every workflow then had to be tracked and maintained on its own, so the maintenance load grew with every item we added.

Decision

At the time, the platform offered few ready-made options for this. So we designed our own: one workflow that decides at runtime what each request needs, instead of a new workflow for every item. We refined the design over time, but runtime execution was the goal from the start.

What we built

  • One table that holds the approval rules for each catalog item.
  • One table that holds the tasks for each catalog item.
  • One master workflow that reads both tables when a request comes in, and runs the right approvals and tasks.
  • Adding a routine catalog item now means adding rows to the tables, not building a workflow.

Result

  • 1,000+ catalog items now run on the one workflow.
  • Up to 20 developer hours saved a month.
  • Routine catalog items are now created by Tier 1 support, with no development needed unless an item has specialised needs.

What I'd do differently

Next time I'd map the nuanced requirements before building: whether tasks run in parallel or in sequence, and which special conditions decide whether a task runs. Then I'd build those into the decision logic from day one.