---
sourceDocument: Australia ServiceNow AI Platform Capabilities
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/servicenow-platform

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia ServiceNow AI Platform Capabilities

ft:clusterId :

    - platcap

bundleId :

    - platcap

workflow :

    - Platform


---

# Create a catalog workflow

# Create a catalog workflow {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

Create service catalog workflows when the default workflows are not appropriate for a
fulfillment process.

## Vorbereitungen

Role required: workflow_creator, workflow_admin, or admin

## Warum und wann dieser Vorgang ausgeführt wird

This example describes the procedure to set up fulfillment for a laptop request.

## Prozedur

1. Navigate to AllWorkflowWorkflow Editor
2. Click New Workflow.  
   Abbildung : 1. Service catalog workflow form
3. Complete the form with the following information.  
   {#t_CreateANewServiceCatalogWorkflow__table_wbf_1zt_dq__entry__2}

   | Field | Input value |
   |-|-|
   | Name | <kbd class="ph userinput">Laptop Fulfillment</kbd> |
   | Table | Requested Item \[sc_req_item\] Consider the following information: * Workflows on the Service Catalog Requested Item \[sc_req_item\] table fulfill the request of a single catalog item. Each requested item triggers its own fulfillment workflow when the item is ordered. Use the Requested Item table to add workflows for requested items. Hinweis: To enable approval-type workflows to operate smoothly, make sure that the appropriate users have the correct role to access necessary tables in all domains. * Use caution when using before query business rules, as they can restrict access to the requested item record. * Workflows on the Request \[sc_request\] table always run when a service catalog request is submitted, regardless of what item was ordered. These workflows control the entire request process, which can involve delivering several requested items. Therefore, Request table workflows are not assigned to a specific item from the maintain item form. If you do use the Request table for service catalog requests, add conditions to the workflow to ensure it runs when the correct item is requested. {#t_CreateANewServiceCatalogWorkflow__ul_ut3_fzt_dq} |
   | Expected time | Days <kbd class="ph userinput">7</kbd>, Hours <kbd class="ph userinput">00:00:00</kbd>. Workflows cannot calculate the end time because not all the activities within the workflow have defined times. Therefore, the Expected time on the workflow becomes the Delivery Time on the catalog request. Hinweis: When both Expected time and Schedule are filled in, the catalog delivery time is then calculated based on the combination of both. For example, if you put 2 days as Expected time, it is calculated as 48 hours. If you then add a schedule that defines a work day as 8 hours, the delivery time becomes 48 / 8 = 6 days. If your schedule excludes weekends, the calculation also add 2 days for the weekend, making the delivery time 8 days. |
   | Schedule | 8--5 weekdays. |
   | Timezone | US/Pacific. The timezone that the schedule applies to. |
   | Description | <kbd class="ph userinput">A workflow for the fulfillment of laptop requests.</kbd> |
   [ ]

   {#t_CreateANewServiceCatalogWorkflow__table_wbf_1zt_dq}
4. Click Submit.  
   Abbildung : 2. Service catalog workflow form activities

## Nächste Maßnahme

After initiating a workflow, add workflow activities to it. Workflow activities are
listed on the Core tab in the right pane.