---
sourceDocument: Australia ServiceNow AI Platform Capabilities
sourceDocumentLink: https://www.servicenow.com/docs/r/servicenow-platform

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia ServiceNow AI Platform Capabilities

ft:clusterId :

    - platcap

bundleId :

    - platcap

workflow :

    - Platform


---

# Create a service fulfillment step type

# Create a service fulfillment step type {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 minutes to read

Expand the coverage of service fulfillment use cases beyond those supported by step
types in base system. Using a service fulfillment step type, catalog item owners can define
multiple steps that are part of the request fulfilment process.

## Before you begin

Role required: admin

## About this task

The following step types are available in the base system.

* Task
* Custom approval
* Manager approval
{#create-sf-step-type__ul_ehp_lnx_jpb}

## Procedure

1. Set up a data store to store information needed for running the step. This information is provided by a catalog item owner while defining the request fulfillment process. Do one of the following.

   | Option | Description |
   | When additional input is required from the catalog item owner for a step type | Create a table by extending the Service Fulfillment Step \[sc_service_fulfillment_step\] table and add fields to store the additional input. For example, to create a step type for email notifications, the email id and body are the additional input provided by the catalog item owner while defining the steps. So, fields for email id and body should be added to the extended table to store the input. Note: Ensure that the new table has similar ACLs as that of the Service Fulfillment Step \[sc_service_fulfillment_step\] table. Note: Ensure that the new table has the canCreate, canUpdate, and canRead application access enabled. For tables extending the Service Fulfillment Step \[sc_service_fulfillment_step\] table, the Domain master attribute should be added and its value should be set as service_fulfillment_stage. The domain of a service fulfillment step is then inherited from the catalog item. |
   | When no input is required for a step type | Use the Service Fulfillment Step \[sc_service_fulfillment_step\] base table. For example, a department head approval does not require any additional input from the catalog item owner and does not need a new table. |
   |-|-|

   {#create-sf-step-type__choicetable_lxs_24x_jpb}
2. Create a record producer to store the values provided by the catalog item owner to the data store (base table or extended table) of that step. For information about creating a record producer, see [Create a record producer](https://www.servicenow.com/docs/j3DOlwp8LUU8j~ksFdiwww "You can create a record producer for tables and database views that are in the same scope as the record producer. Also for tables that allow create access from applications in other scopes.").  
   Note:  
   * The Service Fulfillment Steps - Properties set variable set is automatically added to the record producer and it should not be removed from the record producer.
   * All additional columns defined in the extended table should have corresponding variables mapped in the record producer.
   * Configure the Record Producer form to display the Allow edit option and Save Options field. Also, select the Allow edit option and set the value of the Save Options field to Save in Destination.
   * Ensure that the record producer is not restricted for the users with catalog_builder_editor role.
   {#create-sf-step-type__ul_hvh_54x_jpb}
3. Create a subflow to perform a sequence of actions by copying the Template: Service Fulfillment Steps subflow and then defining your subflow. For information about subflows, see [Subflows](https://www.servicenow.com/docs/access?context=subflows&version=australia&pubname=australia-build-workflows&ft:locale=en-US).  
   {#create-sf-step-type__table_x2q_phd_jpb__entry__3}

   | Parameter | Type | Description |
   |-|-|-|
   | requested_item | Reference | RITM record |
   | service_fulfillment_step_data | Reference | Step data record. Update the state to one of the following values before ending the subflow: * canceled * failed * completed {#create-sf-step-type__ul_okd_bsx_jpb} |
   | service_fulfillment_step | Reference | Step defined on a catalog item. It must refer to a table in which the record producer defined in the step configuration inserts a record. Do not update the step record. |
   [Table 1. Template: Service Fulfillment Steps subflow input parameters]

   {#create-sf-step-type__table_x2q_phd_jpb}

   For information about subflow field types, see [Field
   types](https://www.servicenow.com/docs/access?context=r_FieldTypes&version=australia&pubname=australia-platform-administration&ft:locale=en-US).
4. Create a step configuration to define the behavior and display of a service fulfillment step type.
   1. Navigate to Service CatalogCatalog AdministrationService Fulfillment Step Configurations.
   2. Click New.
   3. On the form, fill in the fields.  
      {#create-sf-step-type__table_tvl_rlh_jpb__entry__2}

      | Field | Description |
      |-|-|
      | Name | Name of the step configuration. |
      | Application | Application scope in which the step configuration is supported. |
      | Active | Option to enable the service fulfillment support for the flow. |
      | Order | Order of the step configuration. Based on the order of step configurations, the corresponding service fulfillment step types are displayed in the list in the Steps region of the Fulfillment step. The step type corresponding to the step configuration with the least order is displayed beside the list and step types for all other step configurations are included in the list based on their order. Figure 1. Order of service fulfillment step types |
      | Hide | Hides the step type corresponding to this step configuration in the list in the Steps region of the Fulfillment step. No impact on existing steps. |
      | Short description | Description of the step configuration. |
      | Producer | Record producer that creates an instance of the step type in the step's data store. |
      | Service fulfillment subflow | Subflow triggered during the request fulfillment process. |
      | Dynamic title | Text that should be displayed for the corresponding service fulfillment step in the Steps region of the Fulfillment step. If you don't provide any value, the step configuration name is displayed. To display dynamic text, you can include the field name from the step's data store (base table or the extended table) where the associated record producer creates a record. For example, in the base system, the Dynamic title field for the Custom approval step configuration contains the following value:`Approval from ${approval_title}` Here, approval_title is the field from the Service Fulfillment Approval Step \[sc_service_fulfillment_approval_step\] table where the associated record producer, Add custom approval, creates a record. |
      [Table 2. Service Fulfillment Step Configuration form]

      {#create-sf-step-type__table_tvl_rlh_jpb}
   4. Click Submit.
   {#create-sf-step-type__substeps_kcb_jmx_jpb}

*[\>]: and then