Create Catalog Task action
Summarize
Summary of Create Catalog Task Action
The Create Catalog Task action enables users to generate a record in the Catalog Task [sctask] table, associated with a requested item from the Requested Items [screqitem] table. This action is integral for managing catalog tasks within workflows in ServiceNow.
Show less
Key Features
- Roles and Availability: Accessible as a Workflow Studio action, usable by those with the flowdesigner or admin role for configuration.
- Inputs:
- Table: Specify the table for record creation, such as Catalog Task [sctask].
- Requested Item: The specific record from the Requested Item table that the catalog task fulfills.
- Short Description: A brief description for the catalog task.
- Fields: Template values for setting task field values, allowing dynamic input in subflows.
- Wait: A flag to pause the flow until the task record is active, ensuring proper sequencing.
- Template Catalog Item: The Catalog Item record for populating catalog variables, though this input does not support dynamic values.
- Catalog Variables: A slush bucket for selecting variables that provide additional details for the catalog task.
- Outputs: Outputs available in the Data panel for further use in the flow, including a reference to the created Catalog Task record.
Key Outcomes
By using the Create Catalog Task action within a flow, users can effectively manage approval processes, set task details, and control workflow execution. The action allows for seamless integration with other tasks and ensures that the flow pauses correctly while waiting for the catalog task to complete, providing visibility into the task and request lifecycle.
Creates a record in the Catalog Task [sc_task] table associated to a requested item in the Requested Items [sc_req_item] table. Adds the catalog task record as data to be used in the flow.
Roles and availability
Available as a Workflow Studio ServiceNow core action. Users with the flow_designer or admin role can add an action to a flow and define configuration details.
Inputs
Provide a value for each input that your flow needs. To add dynamic values, you can also drag and drop pills from the Data panel or select them from the pill picker.
- Table
- Data type: Table Name
Extension of the Task table in which to create a record. For example, Catalog Task [sc_task] or Incident Task [incident_task].
- Requested Item [Requested Item]
- Data type: Record
The requested item record from the Requested Item [sc_req_item] table that this catalog task fulfills.
- Short Description
- Data type: String
The short description for the catalog task.
- Fields
- Data type: Template Value
The field values that you want to set in the catalog task. If adding the action to a subflow, you can allow flow designers to dynamically set field values. See Create a template value input.
- Wait
- Data type: True/False
Flag indicating whether to pause the flow until the Task record is no longer active. You can add a wait condition by dragging-and-dropping a True/False data pill into this input. The flow only waits for the Task record to complete when the condition field is true.
- Template Catalog Item [Catalog Item]
- Data type: Record
The Catalog Item [sc_cat_item] record you want to use to populate the catalog variables slush bucket. This input does not support any data pill values.
- Catalog Variables
- Data type: Slush Bucket
The list of catalog variables that you want to show on the catalog task. These variables provide more information to the catalog task fulfiller.
Outputs
These outputs appear in the Data panel. You can use them as inputs elsewhere in your flow.
- Catalog Task
- Data type: Record
Reference to Catalog Task record created.
Use a flow to process a catalog item request
In this example, the Service Catalog Item request flow first requests manager and department head approval. Only approved requests ever run the Create Catalog Task action. The Requested Item input uses the requested item that triggered the flow to run. The Fields input sets the value of the task short description, assign group, and description. Since the wait input is selected, the flow will pause while the catalog task is being fulfilled. Also since there is no template catalog item selected, there are no catalog variables available to this task.
In this example, the flow execution details show the requested item record number and the catalog task record number. The action state is listed as waiting since the Wait input was selected. The flow waits until the catalog task is closed before continuing.