I’m currently working a custom Integration Hub Spoke to automate mobile device ordering from our Service Catalog directly to a Telecom Expense Management (TEM) portal.
The Architecture: ServiceNow Flow Designer ➔ TEM Portal (e.g.,) ➔ Carrier (AT&T/Verizon)
The Catch: Unlike a direct integration with a warehouse, this is a "proxy order."
ServiceNow pushes the request payload to the TEM provider.
The TEM provider validates and places the order with the Carrier.
The Carrier eventually provisions the device and ships it.
The HAM Conundrum: From a Hardware Asset Management perspective, we want to track the lifecycle accurately (Request ➔ On Order ➔ In Stock). However, because of the "middleman" latency, we don't get the Serial Number or IMEI back in the immediate API response.
For those who have integrated ServiceNow with TEM aggregators:
How do you handle the data gap between "Order Submitted" and "Device Shipped"?
Looking for the cleanest pattern to ensure data accuracy without leaving RITMs hanging!
#ServiceNow #HardwareAssetManagement #IntegrationHub #ITAM
