Lifecycle Full Version field
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-27-2022 12:32 PM
On the Application Service Software Models table, there is a freeform string field called Lifecycle Full Version, which the docs define as "the granular licensable version of the software". Why does this field exist / what is it generally used for? Shouldn't the version information be stored on the software model record instead?
- Labels:
-
Application Portfolio Management

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-01-2022 07:45 AM
Lifecycle data moved from software model to product model. If SAM plugin is enabled you get access to SAM content (the SW products, versions, lifecycles), and I don' think you need this field.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-16-2023 02:13 PM - edited 06-28-2023 05:22 AM
Hi Doron,
This field is populated when you run the technology models retrieval job and appears to be used to match the life cycle data when calculating technology risk. We are seeing that the normalized discovered data from ServiceNow (with SAMP) populates this full version in a way that does not match the ServiceNow life cycle data from the content service. We are seeing, for example, the full version of 1.1.1.X on the Application Service Software Model but the life cycle version data only has 1.1.1. As a result, this does not show up in the APM homepage under the technology portfolio. When we remove the additional value from the full version, it calculates the risk just fine. How do we manage that without having to manually adjust the value for each App Service Software Model entry?
Thank you