Internally created Software Lifecycle type
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 weeks ago
I created an Internal Software Lifecycle type for the Zoom Workplace App we are using as it is not EOL or EOS based on Zoom's Version enforcement for users and admins. How do I ensure the software model associates to the Internal Software Lifecycle I created? It shows as 'Active' but the Content Active shows as 'Not applicable'. I just created it today, Jan 2, 2026. Do I need to wait a certain period of time or it there something I need to have my Service Now Admin do?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 weeks ago
Hi @RachelGB ,
the Software Model itself isn’t effected by any of the dates for Lifecycles etc. based on the product all available lifecycle dates are shown as part of the related list.
End of Life reports etc., are used to show the risk per product based on the phases and dates.
Could you please share more details about your use case and what you want to achieve or expect from adding the internal dates.
Best, Dennis
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hello,
My intention for creating an internal lifecycle phase is to have our company's internal EOL/EOS, be the phase and phase start date used when I run reports for software tech debt using the lifecycle phase report data. I have a sw tech debt dashboard that I want to make available to leadership and internal software owners and I thought it was possible to have a software model associate to an internal lifecycle phase. Here is an example of what I am trying to do. Currently the EOL phase date for the Zoom Workplace app version we use is Jan 1, 2025 and based on the Zoom Software Quarterly Lifecycle Policy, the version that can be used is 5.17.5, at least through Feb 7, 2026.
Rather than edit my report to remove the version we are using manually, I want the system to recognize that the version we are using has EOL, EOS, and EOES at the date I have created as the phase start dates (later than the publisher Lifecycle Type).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @RachelGB ,
Iam little confused where you want to see the report? Have you created the lifecycle phases on software model directly ? and on which table did you create the lifecycle report?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi, I did create the Internal lifecycle phase for the software model and the specific full version we use. I run the software lifecycle reports off of the Table: Software Installation cmdb_sam_sw_install
