{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":37988,"path":"order-management/som_request_tracker.md","title":"Inbound Request","bundle":null,"doc_type":null,"release":"australia","body":"\n# Inbound Request\n\nTrack 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.\n\n## Inbound request table\n\nAdd a record to the modified Inbound Request table \\[sn\\_tmt\\_core\\_inbound\\_queue\\].\n\nThe following fields have been added to enhance the Inbound Request table:\n\n-   Requested flow\n-   Account\n-   Contact\n-   Consumer\n-   Response payload\n-   Source record ids\n-   Status\n-   Run in the background\n-   Initiated by\n-   Domain\n-   Execute after\n-   Request configuration\n-   Job id\n\n<table id=\"table_e1m_jt1_pdc\"><thead><tr><th>\n\nFields\n\n</th><th>\n\nDescription\n\n</th><th>\n\nField type\n\n</th></tr></thead><tbody><tr><td>\n\nRequested flow\n\n</td><td>\n\nThe reference to the Lead to Cash Entity mapping, for example Sold Product to Order mapping.\n\n</td><td>\n\nReference: sn\\_l2c\\_core\\_entity\\_mapping\n\n</td></tr><tr><td>\n\nRun in background\n\n</td><td>\n\nDetermines whether the flow is synchronous or asynchronous.\n\n</td><td>\n\nTrue/FalseDefault value: True\n\n</td></tr><tr><td>\n\nResource\n\n</td><td>\n\nThe name of the flow that creates the record in the Inbound Request table.\n\n</td><td>\n\nString\n\n</td></tr><tr><td>\n\nSource record ids\n\n</td><td>\n\nSystem-generated id of the source records.\n\n</td><td>\n\nList\n\n</td></tr><tr><td>\n\nSource table\n\n</td><td>\n\nPrimary Lead to Cash Entity table on which the request is triggered.\n\n</td><td>\n\nTable name\n\n</td></tr><tr><td>\n\nRecord id\n\n</td><td>\n\nSystem-generated id of the target record.\n\n</td><td>\n\nString\n\n</td></tr><tr><td>\n\nReference table\n\n</td><td>\n\nName of the target entity table for the request.\n\n</td><td>\n\nTable name\n\n</td></tr><tr><td>\n\nPayload\n\n</td><td>\n\nRequest received as input to trigger the flow.\n\n</td><td>\n\nString\n\n</td></tr><tr><td>\n\nResponse payload\n\n</td><td>\n\nResponse of the request that contains the result of the flow and captures the record-level action and transaction status.\n\n</td><td>\n\nJSON\n\n</td></tr><tr><td>\n\nState\n\n</td><td>\n\nCurrent state of the transaction.\n\n</td><td>\n\nString \\(choice\\)New, In progress, Completed, Error, Pending\n\n</td></tr><tr><td>\n\nStatus\n\n</td><td>\n\nThe status of completion of the flow, for example success, partial success, failure\n\n</td><td>\n\nString \\(choice\\)Success, partial success, failure\n\n</td></tr><tr><td>\n\nError message\n\n</td><td>\n\nError message that is returned for an exception.\n\n</td><td>\n\nString\n\n</td></tr><tr><td>\n\nAccount\n\n</td><td>\n\nThe account associated with the source or target record.\n\n</td><td>\n\nReference: customer\\_account\n\n</td></tr><tr><td>\n\nContact\n\n</td><td>\n\nThe contact associated with the source or target record.\n\n</td><td>\n\nReference: customer\\_contact\n\n</td></tr><tr><td>\n\nConsumer\n\n</td><td>\n\nThe consumer associated with the source or target record.\n\n</td><td>\n\nReference: csm\\_consumer\n\n</td></tr><tr><td>\n\nInitiated by\n\n</td><td>\n\nThe user id from the current user session.\n\n</td><td>\n\nReference: sys\\_user\n\n</td></tr><tr><td>\n\nDomain\n\n</td><td>\n\nThe current domain scope of the record, for example global\n\n</td><td>\n\nDomain id\n\n</td></tr><tr><td>\n\nRequest Configuration\n\n</td><td>\n\nThe reference to the Inbound Request Configuration table.strict\\_read\\_only field\n\n</td><td>\n\nReference: sn\\_tmt\\_core\\_inbound\\_queue\\_config\n\n</td></tr><tr><td>\n\nExecute After\n\n</td><td>\n\nInbound request that must be processed before the current request.strict\\_read\\_only field\n\n</td><td>\n\nReference: Inbound Request\n\n</td></tr><tr><td>\n\nJob id\n\n</td><td>\n\nReference to Upgrade Inventory Job table.strict\\_read\\_only field\n\n</td><td>\n\nReference: sn\\_ind\\_tmt\\_orm\\_upgrade\\_inventory\\_job\n\n</td></tr></tbody>\n</table>**Note:** The **requested\\_flow** and **response\\_payload** fields aren’t visible to agents.\n\nUse the **Requested flow &lt;is not empty&gt;** 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.\n\n**Note:** The flow designer **SOM Request Processor** is deprecated. Requests are directed to the flow designer IBQ Request Processor.\n\n## Security roles\n\n<table id=\"table_uwv_tp4_ddc\"><thead><tr><th>\n\nRole\n\n</th><th>\n\nPermission\n\n</th></tr></thead><tbody><tr><td>\n\nInbound Queue admin \\[sn\\_tmt\\_core.inbound\\_queue\\_admin\\]\n\n</td><td>\n\nCreate, read, delete, and update\n\n</td></tr><tr><td>\n\nInbound Queues Create User \\[sn\\_tmt\\_core.inbound\\_queue\\_create\\_user\\]\n\n</td><td>\n\nCreate**Note:** For Sales CRM requests, the user doesn't have access to the **response\\_payload**, **payload**, or **requested\\_flow** fields.\n\n</td></tr><tr><td>\n\nInbound Queues Write User \\[sn\\_tmt\\_core.inbound\\_queue\\_writer\\]\n\n</td><td>\n\nWrite access for non Sales CRM requestsRead only access for Sales CRM requests\n\n**Note:** For Sales CRM requests, the user doesn't have access to the **response\\_payload**, **payload**, or **requested\\_flow** fields.\n\n</td></tr><tr><td>\n\nInbound Queue Read User \\[sn\\_tmt\\_core.inbound\\_queue\\_read\\]\n\n</td><td>\n\nRead access to all Sales CRM requests\n\n **Note:** For Sales CRM requests, the user doesn't have access to the **response\\_payload**, **payload**, or **requested\\_flow** fields.\n\n</td></tr></tbody>\n</table>## Archival policies\n\nArchive 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.\n\n|Archival rule|Time period|\n|-------------|-----------|\n|Successful requests|10 days|\n|Failed requests|30 days|\n\n**Related topics**  \n\n\n[Inbound Request Configuration](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/order-management/inbound-request-configuration-table.md)\n\n"}}