Source Request Task in HAM

[khandelwal2]

I have created a new catalog item but using the 'Standard Hardware Asset request' flow. after raising request catalog task is not getting created for sourcing. I checked for it to be generate sourceable should be set to true. How sourceable is getting set "true"?

[Shraddha sawant]

@khandelwal2 -

Kindly check the OOB workflow is published or not,OOB flow name is Source Request.

Source request workflow is triggered when the Request is 'Sourceable'. On the Request table there is a field called Sourceable that is marked as true if the catalog item(s) are published from models. Not to be confused with the field called 'Sourced' that is also on the Request. If you are publishing hardware or software models to the catalog then you will notice that a field called 'Model' gets populated on the catalog item. There is a business rule on the Request that runs and looks at the Item associated to the Request item. To summarize if the Item associated to the Request item has a model, then Sourceable gets marked as true. This workflow is required to properly create the Catalog Sourcing task that is needed for Procurement. 

[MercBuilding]

Hi @Shraddha sawant ,

   Glad to see the explanation. Can we implement this in normal catalog item without any model name and ITAM team will pick the specific model they want to source?

[Rakesh18081]

I am also looking for this solution.

[Vikram Reddy]

Hi @khandelwal2,

Sourceable isn't something you flip by hand, it's set by an out-of-box business rule on the Request record that fires when the RITM is created, and it only turns true if the catalog item tied to that RITM has its Model field populated. If your new catalog item doesn't carry a reference back to a hardware Product Model, that business rule has nothing to key off, sourceable stays false, and the OOB Source Request flow never triggers, so no sourcing catalog task gets generated.

This is the bit that trips people up: attaching the Standard Hardware Asset Request flow to a catalog item you built by hand isn't enough on its own. Sourcing in HAM is designed around catalog items that come from publishing a Product Model, not items authored directly in Service Catalog. Worth checking, in order:

• the Model field on the catalog item, confirm it's populated and points to an actual hardware Product Model record, not blank
• the Publish to Hardware Catalog UI action, use this from the Product Model record itself rather than building the catalog item manually, it auto-populates Model and wires up the sourcing plumbing for you
• the Manufacturer on that model, the company referenced there needs the Vendor checkbox checked, otherwise sourcing options won't populate even once sourceable is true
• the sn_hamp_hw_asset_process HAM process variable, if you're deliberately keeping your custom item instead of a published one, this needs to be present so the Flow Designer flow actually recognizes the request as HAM-sourceable
• whether you're actually looking at sourceable and not sourced, they're two separate fields on the same table and it's easy to check the wrong one mid-debug

Honestly the cleanest path is usually to scrap the hand-built catalog item and republish straight from the Product Model using Publish to Hardware Catalog. Retrofitting sourcing onto a manually created item can be made to work, but you're fighting the design, and you'll likely trip over more gaps later, transfer order line linking and stockroom location matching being the usual suspects.

Thank you,
Vikram Karety
Octigo Solutions INC