Understanding how ServiceNow fulfils service catalogue requests is foundational knowledge for administrators and certification candidates. This question focuses on identifying the available fulfilment process options and clarifies what is — and isn't — used in real implementations.
The quiz question
Select 3 answers from the options below.
Correct answers
2. Workflow
3. Execution Plan
Incorrect options
Roadmap
Detailed explanation
When a user orders a catalogue item, ServiceNow creates a request that follows a predefined fulfilment process. This process controls how approvals are handled, how tasks are created and assigned, and how the request is completed. ServiceNow's own Service Catalog API documentation confirms it directly: a catalog item must reference a flow, workflow, or execution plan that defines how the item request is fulfilled — exactly three supported mechanisms, nothing more.
✔️ 1. Flow
Flows are created using Flow Designer and represent the modern, recommended approach. They provide no-code/low-code automation, handle approvals, tasks, notifications, and conditions, and are generally easier to read, maintain, and extend than the alternatives. Under the hood, a flow is stored as a record on the sys_hub_flow table.
Best suited for: most new implementations and future-proof designs — ServiceNow's own documentation explicitly recommends flows as the fulfilment method for new catalog items.
✔️ 2. Workflow
Workflows are the legacy automation method for fulfilment, built in the classic Workflow Editor rather than Flow Designer. They support complex logic and branching paths, and can stop or continue based on approvals or conditions. Workflows are stored on the wf_workflow table, and are still widely used in existing implementations that predate Flow Designer's maturity.
Note: while still supported, workflows are gradually being replaced by flows — ServiceNow's guidance is to use the flow property for new implementations rather than building new workflows.
✔️ 3. Execution Plan
Execution plans define simple, linear fulfilment processes. They describe how an item is procured, configured, or installed; consist of one or more predefined tasks; and involve no branching or complex logic. They're stored on the sc_cat_item_delivery_plan table. Compared to workflows, execution plans are strictly for task generation and sequencing — they can't be designed with a graphical editor, and the requester sees each task listed as a discrete stage rather than a smoother workflow-style progression.
Ideal for: straightforward, task-based fulfilment scenarios — and for cases where you need to build the process programmatically or through imports rather than a visual designer.
Why the other options are incorrect
🚫 Plan
Not a valid fulfilment mechanism for catalogue items. It's too generic and isn't a recognized ServiceNow fulfilment feature — a plausible-sounding distractor, but not something you'll find on the catalog item form.
🚫 Roadmap
Roadmaps are typically used for strategic or planning purposes (think Now Value or Strategic Portfolio Management), and have no role in request fulfilment automation.
Overall explanation summary
When preparing to fulfil catalogue item requests, administrators typically:
- Set up fulfilment groups to assign request tasks
- Define fulfilment processes using Flow Designer flows, workflows, or execution plans
- Assign the fulfilment process to catalogue items
Each fulfilment method serves a different use case, but all three are valid and supported — the right choice comes down to complexity, maintainability, and how future-proof the implementation needs to be.
Fulfilment process comparison
| Feature / Aspect | Flow | Workflow | Execution Plan |
|---|---|---|---|
| Underlying table | sys_hub_flow | wf_workflow | sc_cat_item_delivery_plan |
| Process type | Visual, modern automation | Legacy automation | Linear task sequence |
| Complexity support | Medium to high | High | Low |
| Branching logic | Yes | Yes | No |
| Approvals | Yes | Yes | No |
| Task assignment | Yes | Yes | Yes |
| Maintenance | Easy | Moderate | Very easy |
| Best use case | Most catalogue items | Existing complex setups | Simple fulfilment |
| Precedence if multiple are set | Always wins | Overridden by flow | Overridden by flow |
Quick exam tip
✔ Fulfilment processes = Flow + Workflow + Execution Plan
✘ Ignore generic distractors like Plan or Roadmap
✔ If more than one is configured on the same item, Flow wins
One-line memory aid
Catalogue fulfilment follows either a modern flow, a legacy workflow, or a simple execution plan — and if more than one is attached to the same item, the flow always wins.
Additional learning resource
- Service Catalogue Request Fulfilment — official ServiceNow documentation
Final thoughts
This question reinforces a key ServiceNow concept: multiple fulfilment mechanisms exist, and choosing the right one depends on complexity, maintainability, and future readiness. For exam preparation, remember Flow, Workflow, and Execution Plan — and ignore generic-sounding distractors like Plan or Roadmap.
This article reflects ServiceNow's Service Catalog API documentation, including the flow-takes-precedence rule when multiple fulfilment mechanisms are configured on the same catalog item. Table names and precedence behavior are consistent across recent release families as of this writing — verify against your own instance if you're on an older release.