'Create hardware assets prior to delivery' Related link not working after adding custom states
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-03-2025 07:47 AM
I have added custom status choices for both the Purchase Order and Purchase Order Line Items table (we are currently not using the ootb ones). When I click on the 'Create hardware assets prior to delivery' related link, I get the info message:
"Asset updates are in progress. Please do not update this record until complete. Reload page to check progress."
but the assets are not getting created, I have checked the ProcurementUtils script include but can't find where the asset creation is dependent on the PO or PO Line Item status. Is there something else I should be checking?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-03-2025 09:00 AM
Hi @mishael
sorry to tell you, but adding custom states to fundamental tables and not using the OOTB is a pretty bad idea. All the underlying functionality is at risk of breaking. Furthermore, you will not get any support anymore by ServiceNow because they will not take the responsibility for these kinds of customizations.
Maik
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thursday
I encountered a similar issue with the Create hardware assets prior to delivery action.
In my case, the UI Action and the related Procurement Business Rule and Script Include were all out of the box. The issue was caused by a custom Data Policy on the Hardware [alm_hardware] table that made the Serial number field mandatory.
Assets created prior to delivery do not have serial numbers yet because that information is normally captured during receiving. The Data Policy therefore prevented the hardware record from being inserted. The Purchase Order continued to display:
Asset updates are in progress. Please do not update this record until complete.
When I deactivated the Data Policy, the assets were created successfully. When I reactivated it, asset creation failed again.
I recommend checking the following on both alm_hardware and its parent alm_asset table:
Data Policies that make fields mandatory
Dictionary-level mandatory settings
Before-insert Business Rules that validate required fields or call setAbortAction(true)
Custom validation scripts that may reject records created without a serial number
Also note that a Data Policy with Use as UI Policy on client selected can still enforce the requirement during server-side inserts. In this scenario, the Data Policy should be adjusted to exclude legitimate pre-delivery assets, such as assets in the On Order or In Transit state that are associated with a Purchase Order line.