Service Catalog request fulfillment When a user orders a catalog item, a request is created that follows a fulfillment process. A fulfillment process defines the steps to request approval, assign fulfillment tasks, and fulfill requests. Execution plans or workflows are used to define fulfillment processes. Introduces request fulfillment in Service Catalog, provides a comparison of execution plans versus workflows, and demonstrates creating an execution plan and a workflow.Preparing to fulfill catalog item requests involves the following activities. Set up fulfillment groups to assign to tasks. Define the fulfillment processes using execution plans or workflows. Assign the fulfillment process to catalog items. Using workflows Workflows provide greater flexibility than execution plans, which are linear. Workflows allow for different paths to the end of the process. For example, an approver can reject a request, ending the process. If the request is approved, the process continues through fulfillment to the end of the process. Use the Workflow Editor to define fulfillment workflows. The Workflow Editor offers the following features. Edit workflows graphically. Modify activities and conditions. Define transitions between workflow activities. Summarize workflow progress through stages. Validate workflows to identify potential problems. Publish workflows for other users. Service catalog workflowsTwo service catalog workflows are provided in the base system. Use the Graphical Workflow Editor to modify the default workflows or to create additional service catalog workflows. Service catalog workflows support domain separation.Execution PlansAn execution plan describes how a catalog item is procured, configured, and installed. Service Catalog checkout modelsThe service catalog defaults to one-step checkout model, but also allows two-step checkout. Administrators and users with the catalog_admin role can enable and configure the two-step checkout model and control how the delivery address is populated.