Note that this action captures variable values only at runtime. To detect changes in catalog variable values, you must build additional flow logic, such as using the Wait For Condition action with a change operator, and re-invoke this action when values update.

Inputs

• Submitted Request: The requested item record from the screqitem table for which you want to retrieve catalog variable values.
• Template Catalog Items and Variable Sets: The catalog item record used to populate the list of catalog variables (slush bucket). This input requires a specific catalog item record and does not accept dynamic data pills.
• Catalog Variables: A selectable list of catalog variables from the chosen template catalog items and variable sets whose values you want to extract from the requested item. Selected variables appear as data pills for use elsewhere in the flow. You can also define flow-specific variables for this list.

Outputs

The action outputs each selected catalog variable as a separate data pill in the Data panel. The data type of each output matches the catalog variable type, allowing you to utilize these values as inputs in subsequent flow steps. For details on supported variable types, refer to the Service Catalog documentation.

Practical Example: Retrieving Variables for Hardware Items

In a typical use case, a flow triggers when a Service Catalog item is requested. The flow:

• Retrieves the catalog item record of the requested item.
• Uses conditional logic to check if the item belongs to a specific category (e.g., Hardware).
• Calls the Get Catalog Variables action, providing the requested item and a template catalog item (such as "Standard Laptop") to specify which variables to retrieve.
• Extracts all selected catalog variables, which then become available as data pills for further processing.

This example demonstrates how to dynamically access catalog variable values such as strings and Boolean fields from hardware-related catalog requests, enabling customized flow actions based on catalog data.