Inbound Request

  • Release version: Australia
  • Updated June 18, 2026
  • 3 minutes to read

    • Track the status of Sales CRM workflows and enable agents to track the status of any synchronous and asynchronous flows. It also supports processing dependent records sequentially to make sure that the data stays accurate and consistent.

    Inbound request table

    Add a record to the modified Inbound Request table [sn_tmt_core_inbound_queue].

    The following fields have been added to enhance the Inbound Request table:
    • Requested flow
    • Account
    • Contact
    • Consumer
    • Response payload
    • Source record ids
    • Status
    • Run in the background
    • Initiated by
    • Domain
    • Execute after
    • Request configuration
    • Job id
    Table 1. Inbound Request table fields and descriptions
    Fields Description Field type
    Requested flow The reference to the Lead to Cash Entity mapping, for example Sold Product to Order mapping. Reference: sn_l2c_core_entity_mapping
    Run in background Determines whether the flow is synchronous or asynchronous. True/False

    Default value: True
    Resource The name of the flow that creates the record in the Inbound Request table. String
    Source record ids System-generated id of the source records. List
    Source table Primary Lead to Cash Entity table on which the request is triggered. Table name
    Record id System-generated id of the target record. String
    Reference table Name of the target entity table for the request. Table name
    Payload Request received as input to trigger the flow. String
    Response payload Response of the request that contains the result of the flow and captures the record-level action and transaction status. JSON
    State Current state of the transaction. String (choice)

    New, In progress, Completed, Error, Pending
    Status The status of completion of the flow, for example success, partial success, failure String (choice)

    Success, partial success, failure
    Error message Error message that is returned for an exception. String
    Account The account associated with the source or target record. Reference: customer_account
    Contact The contact associated with the source or target record. Reference: customer_contact
    Consumer The consumer associated with the source or target record. Reference: csm_consumer
    Initiated by The user id from the current user session. Reference: sys_user
    Domain The current domain scope of the record, for example global Domain id
    Request Configuration The reference to the Inbound Request Configuration table.

    strict_read_only field

    		 Reference: sn_tmt_core_inbound_queue_config
    Execute After Inbound request that must be processed before the current request.

    strict_read_only field

    		 Reference: Inbound Request
    Job id Reference to Upgrade Inventory Job table.

    strict_read_only field

    		 Reference: sn_ind_tmt_orm_upgrade_inventory_job
    Note:
    The requested_flow and response_payload fields aren’t visible to agents.
    Use the Requested flow <is not empty> to filter out records using the Lead to Cash core APIs. The Inbound Request table [sn_tmt_core_inbound_queue] provides the status and other details related to the request. For example, while creating an order through a quote record, a confirmation message with the order header number.
    Note:
    The flow designer SOM Request Processor is deprecated. Requests are directed to the flow designer IBQ Request Processor.

    Security roles

    Table 2. Security roles and access for the Inbound Request table
    Role Permission
    Inbound Queue admin [sn_tmt_core.inbound_queue_admin] Create, read, delete, and update
    Inbound Queues Create User [sn_tmt_core.inbound_queue_create_user] Create
    Note:
    For Sales CRM requests, the user doesn't have access to the response_payload, payload, or requested_flow fields.
    Inbound Queues Write User [sn_tmt_core.inbound_queue_writer] Write access for non Sales CRM requests

    Read only access for Sales CRM requests

    Note:
    For Sales CRM requests, the user doesn't have access to the response_payload, payload, or requested_flow fields.
    Inbound Queue Read User [sn_tmt_core.inbound_queue_read]

    Read access to all Sales CRM requests

    Note:
    For Sales CRM requests, the user doesn't have access to the response_payload, payload, or requested_flow fields.

    Archival policies

    Archive the records in the Inbound Request table and determine when to clean up records on the table after a certain number of days. You can implement a different retention period for successful and failed requests.
    Archival rule Time period
    Successful requests 10 days
    Failed requests 30 days