ERP Data Hub Use ERP Data action details for flows

  • Release version: Xanadu
  • Updated August 1, 2024
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of ERP Data Hub Use ERP Data action details for flows

    The Use ERP Data action in Workflow Studio enables ServiceNow customers to integrate and test ERP (Enterprise Resource Planning) data within flows after creating and managing models in ERP Data Hub. This action allows you to incorporate real-time ERP data interaction—such as reading or updating ERP system information—directly into the ServiceNow AI Platform workflows.

    Show full answer Show less

    Role Requirements and Availability

    This action is part of ERP Data Hub and requires specific user roles assigned via delegated development or direct user assignment. Proper role permissions are necessary to access and utilize this action in Workflow Studio flows.

    Inputs

    • ModelName: Specifies the ERP model name that contains the read or update operation. The model must already exist and define these operations in ERP Data Hub.
    • ModelOperation: Defines whether the action will perform a Read or Update operation on the ERP system. The operation entity must be preconfigured in ERP Data Hub.
    • Mandatory Field(s): Required input parameters for the operation, pre-defined in the ERP Data Hub model.
    • Optional Field(s): Optional input parameters for the operation, also pre-defined in the ERP Data Hub model.
    • System: References the connected ERP system to interact with.

    You can provide static values or dynamic values using the pill picker to populate these inputs in your flow.

    Outputs

    • Action status: Provides runtime details of the action, including a status code and message.
    • Don't Treat As Error: Boolean indicator to classify the action status as an error or success in the flow.
    • Error Message: Contains any error messages generated by the action or underlying ERP system operation.
    • Response: Returns the requested ERP data as a dynamic object, which can be used as inputs for subsequent flow steps.

    Practical Benefits

    ServiceNow customers can leverage the Use ERP Data action to efficiently test and build flows that integrate ERP system data without custom coding. This streamlines workflows that require ERP system interactions, improves data accuracy, and enables automation of business processes that span ERP and ServiceNow platforms.

    After you're done creating and managing your model in ERP Data Hub, go to Workflow Studio and use the Use ERP Data action to test your model's inputs and outputs. You can then build a flow with the action to incorporate ERP (Enterprise Resource Planning) data into the ServiceNow AI Platform.

    For information on using the Use ERP Data action to retrieve ERP data, see Building flows to read or update the ERP system.

    Roles and availability

    Available as part of ERP Data Hub.

    Role requirements
    This action requires roles granted by delegated development or assigned to the user. For more information, see User access to Workflow Studio flows.

    Inputs

    Provide a value for each input that your action needs. To add dynamic values, you can also select data pills using the pill picker.

    ModelName
    Data type: Dynamic Choice

    Name of the ERP model that contains the read or update operation. The model must already be created, and have the read or update operation defined in ERP Data Hub. For more information, see Managing how models read and update the ERP system.

    ModelOperation
    Data type: Dynamic Choice

    Whether to Read or Update the ERP system. The read or update entity must already be defined in ERP Data Hub. For more information, see Add a read, update, or create entity to a model in ERP Data Hub.

    Mandatory Field(s)
    Data type: Dynamic Template

    Fields that are required for the operation. Fields must already be defined as required input parameters when you manage the model in ERP Data Hub. For more information, see Manage input parameters for an ERP Data Hub model operation.

    Optional Field(s)
    Data type: Dynamic Template

    Fields that are optional for the operation. Fields must already be defined as optional input parameters when you managed the model. For more information, see Manage input parameters for an ERP Data Hub model operation.

    System
    Data type: Reference

    Name of the connected ERP system. For more information, see Working with ERP systems in ERP Data Hub.

    Outputs

    You can use these outputs as inputs for other items.

    Action status
    Data type: Object

    Data pill that contains the current runtime details about the action. The Action Status object consists of a code and a message.

    Don't Treat As Error
    Data type: True/False

    Option to report the Action Status as an error or a success when returned to a flow.

    Error Message
    Data type: String

    String data pill containing the error message produced by the action, step, or system operation.

    Response
    Data type: Dynamic Object

    Requested data that's returned from the ERP system. For more information, see Choose output parameters for an ERP model.