- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-26-2025 02:48 AM - edited ‎05-26-2025 02:51 AM
I am currently testing SAM Professional.
I understand that it is easy to create a Catalog Item (pc_software_cat_item) from the related list of the Software Model (cmdb_software_product_model).
However, since preparations for M365 integration are delayed, we are planning to create and release the catalog item first for the time being.
In other words, at this point in time, no Software Model has been created.
However, I am concerned about the following: "If I create a Catalog Item manually first, will I be able to link it correctly when the Software Model is created later?"
Is it possible to link the Software Model to an existing catalog item?
If this is not possible, I imagine that, for example, the Variables set in the Catalog Item would need to be recreated, or they would need to be linked to the new pc_software_cat_item using Variable Sets.
Also, please let me know if there are any other concerns or cautions about "creating a catalog item first."
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-26-2025 02:52 AM
If you aren't running with the Software Model yet, you shouldn't relate them later. Just replace the catalog item when you do go live.
Please mark any helpful or correct solutions as such. That helps others find their solutions.
Mark
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-26-2025 03:03 AM
Hi @nagaryu,
- publish the final item later and replace the existing one
- add the field „Model“ to your view to link the cat item to any existing model after it was created.
Not sure if the linked model will trigger the same changes to the software model - to link the cat item and block the action to create a cat item. This needs to be checked, to avoid any cat item duplication. If it’s not updated, you go with @Mark Manders solution or establish checks to block these kind of actions.
Best, Dennis
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-26-2025 02:52 AM
If you aren't running with the Software Model yet, you shouldn't relate them later. Just replace the catalog item when you do go live.
Please mark any helpful or correct solutions as such. That helps others find their solutions.
Mark
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-26-2025 03:03 AM
Hi @nagaryu,
- publish the final item later and replace the existing one
- add the field „Model“ to your view to link the cat item to any existing model after it was created.
Not sure if the linked model will trigger the same changes to the software model - to link the cat item and block the action to create a cat item. This needs to be checked, to avoid any cat item duplication. If it’s not updated, you go with @Mark Manders solution or establish checks to block these kind of actions.
Best, Dennis
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-26-2025 03:13 AM
Hi @Mark Manders , @dreinhardt ,
Thank you for your quick response. In other words, am I correct in understanding that "the existing Catalog Item needs to be discontinued and the Variables and Variable Sets need to be set again in the newly created pc_software_cat_item"?
I am also considering installing the com.snc.procurement plugin separately.
Using this, I am considering using it because it allows me to easily assign licenses to users from the sc_request > sc_task > Source Request button.
I tried creating a pc_software_cat_item in PDI, and although I was unable to use this function before linking the Software Model to the Model field of this Catalog Item (sc_task was not created), after linking, a sc_task was created and this function became usable.
Even so, considering the safety of the operation, is it recommended that "linking to an existing pc_software_cat_item should not be done"?