Hi,
We are currently implementing Life Cycle Management in SAM-P and we and we would like to create a report linking records in the Software Installation table to Software Model Lifecycle table. We created a database view, joining several tables in our attempt to achieve this.
One of the joins in this view is about linking the Software Model table to the Software Discovery Model .
Within a record of the Software Model table, you can click on Show Matching Software Discovery Models in Related Links and it shows something like this:
Product, Language, Platform, Edition and Version.
However, the ServiceNow Docs on
https://docs.servicenow.com/bundle/newyork-it-service-management/page/product/asset-management/conce...
says this about the subject:
The ServiceNow platform uses any of the following field combinations to match the new software discovery model to an
existing software model.
- Display Name, Publisher, and Version
- Display Name and Version if the Publisher field is empty
- Display Name only if the Publisher and Version fields are empty
This is not the same as the filter with the 5 fields mentioned above and the database view produces different results when I use these two alternate field options.
Could anyone advise me on what would be the recommended way to join these two tables?
This will almost work, but will result in duplicate results because multiple matching samp_sw_entitlement_definitions exist, even when matching on all the norm_ fields (edition, language, platform, etc). The exact same piece of software can be licensed differently, therefore there will be multiple matching Discovery Maps for the same Discovery Model.
If you go through cmdb_software_product_model to get to sam_sw_model_lifecycle, it should fix that, but you'll need models created for all the software you're managing.
The functions in the script below can help to create Software Models for either all discovered software, or all software received from the content service (in case you need to analyse lifecycle data on software you are considering purchasing in the same view as purchased software).
[EDIT: Turns out that's supposed to happen OOTB, but wasn't working for us. Unnecessary script removed form the thread].
This is as far as we've gotten in our ogranisation, but are still a bit away from a working solution. Feedback, updates, assistance, and advise welcome.
