Home Asset Management

Relate Consumables directly to the User

Simon_ZeinhoferSimon_Zeinhofer Customer IT Monkey ✭

Hello guys,

we found out, that in SCSM 2016 and Cireson it is not possible to relate Consumables (e.g. Headsets, Mice etc.) directly to a user - at least we think it is not possible :D Maybe it is and we just didn't figure it out yet.

But even if we could, we have no "Related Consumables" field in our user objects (which we have in our Hardware Asset Object). Neither in SCSM nor in Cireson.

So my question is. Is there a way to create this field in SCSM and then just add it in the System.Domain.User.js file? For examle like the Source_ConsumableHasAssignedAssets in our Hardware Asset Class. We would need to add it to SCSM first I guess and then add the field in the Cireson .js file.

Any suggestions here? :)


  • Adam_DzyackyAdam_Dzyacky Product Owner Contributor Monkey ✭✭✭✭✭

    So on a consumable, there is a list of Assigned Users and you can add more as you see fit.

    Then on Hardware Asset forms there are other Asset concepts available such as related Software Assets, more Hardware Assets, and Consumables.

    But what you are getting at is approaching this from the other direction - exposing Asset concepts on a User form. This requires some customization but is all within the realm of possibility. I'm guessing you're thinking something like this...

    In which case, what you'll need to do is create a custom Type Projection. The reason you'll need a custom projection is because AFAIK the only projections that exist out of the box are things like:

    • User to Related Items (Work Items and Config Items)
    • User to Cireson Asset Management concepts

    But there isn't any Type Projection that intersects both of those things (AFAIK that is). So in my case above, I configured my User form to use a Cireson AM Type Projection. It lets me provide the screenshot above, but what it doesn't show is that my "Related Items" tab with Work Items is now 100% empty. That said, a custom Type Projection would need to be created that includes all of those relationships. If however, there are only a subset of users that would be approaching things this way and don't necessarily need to see other related user concepts, this would work as you can control who sees the form and no extra Type Projections would be required.

    In either case it's worth mentioning that building Type Projections doesn't have to be difficult thanks to this nifty SCSMProjectionBuilder project from @Justin_Workman .

Sign In or Register to comment.