Source Request Workflow not published and how does this affect Hardware Asset Management Flows?

[WazzaJC]

Hi ServiceNow Community friends,

In our client's instance, we have implemented Hardware Asset Management Pro, out of the box (OOTB).

We are now trying to use the standard OOTB Hardware Request Flow on Hardware Catalog items, however we have noticed that the relevant procurement tasks are not being raised so the asset which has sourceable is required, is remaining as not sourced.

I have also noticed in the client's instance, that the original OOTB 'Source Request' workflow is not published and it is not possible to publish it, perhaps as it is corrupted or was checked out many years ago and is now unable to be published/activated.

Could this be the reason that we are unable to source/procure the asset and why we are not seeing the procurement task being triggered ? Is it because part of the Hardware Asset Management process depends on this Source Request workflow ?

As a solution - can I not export the XML record for the standard Source Request workflow from my PDI and then import the XML record into the client DEV instance, in order to have a fully working version of the OOTB Source Request workflow? If I bring in the XML I should get a fresh version of the Source Request workflow that I can then Publish/Activate and this should then function to allow the sourcing of the asset request to work properly?

Please can anyone who has experience with Hardware Asset Management let me any thoughts on the above and if the solution may work to get this part of the process working again ?

Many thanks community friends, I appreciate your help.