Hi @p t1,
Q: How software models can be created for corresponding discovery models
the link between discovery & software models is based on the following attributes:
- Publisher
- Product
- Version
- Edition
- Platform
When you create a software model an choose the following combination (Publisher Microsoft, Product: Windows Server, Version: 2019 and Edition is empty) it will include all Windows Server 2019 discovery models whether it is Standard or Enterprise. You can also create a software model based on a DMAP (Discovery Map) - "Discovery Maps (DMAPs) are variations of the software as predefined in the SAMP content library. Although a software model can be defined manually by setting the Publisher, Product, Version, Edition, the best approach is using DMAPs whenever possible. The DMAPs associate the relevant content with the Software Model automatically like the suite relationships, downgrade models, lifecycle, and next version."
Q: And how those software models are linked with product lifecycle information that we are getting in software product lifecycle table?
The life-cycle information is linked with product and maintained by the content team, but can also be extended by yourself. "The Software Product Lifecycle [sam_sw_product_lifecycle] table holds the information of the software product, its lifecycle type (internal or external), full version, lifecycle phases, start date of the phase, and the risk."
Best, Dennis
Should my response prove helpful, please consider marking it as the Accepted Solution/Helpful to assist closing this thread.
