Hi Community,
We have a Vendor ↔ Servicenow integration where order and asset updates are exchanged between ServiceNow and the vendor. Currently, when a user's Project Number/Cost Center changes, an existing Business Rule updates the Cost Center on already created hardware assets and successfully generates an outbound SN-Vendor.asset.update - Integration transaction.
The issue occurs when the Cost Center changes after the order is sent to the vendor but before the asset is created. Since no asset exists at the time of the change, the existing logic cannot update anything. When the vendor creates the asset later, it may contain an outdated Cost Center.
We tested Flow Designer and Business Rule approaches that update the Cost Center after asset creation, but no outbound transaction was generated because the asset is created/updated by 'system', which is excluded by ServiceNow's loop-prevention logic. Every time vendor creates an asset record, the field 'updated by' is 'system' and hence gets ignored by integration logic to avoid loops.
Looking for a recommended design pattern to handle Cost Center changes between order placement and asset creation, while ensuring the vendor receives the updated Cost Center without modifying core integration safeguards or introducing integration loops.
