Is there a way to tie the Service Request to an Asset?

[Suggy]

Looking for a way to tie a Service Request to an Asset.

Use case - As part of onboarding, a service request will be created and the asset will be assigned to the user. Need to link the Asset and the REQ/RITM.

[Arthur Schulcz1]

This will normally be done as a catalog task with the asset tag and serial number included as variables in the REQ/RITM.  The team that sources or deploys the asset would update the ticket with the device (or software) information.

You can reference these workflows in a PDI for examples of how to implement: Service Catalog Item Request, Procurement process Flow - Hardware

[OlaN]

Hi,

OOB there is a field on the Asset called "Request line" this is a reference to the sc_req_item table, and can be populated as a part of your catalog fulfillment task.

You can for example have a variable on the Catalog item for requesting a computer, that references the asset table, and when the Flow/workflow finishes it sets the value of the "Request line" field on the selected asset.

[Suggy]

Hi @OlaN  I see that field is used as part of Procurement management. When you receive the asset, the RITM number created as part of the procurement request is populated there.

[OlaN]

Not sure if you are correct. We haven't got the Procurement license, and still have that field on our alm_hardware table OOB.

Do you have a reference to the Docs on this?