Internally created Software Lifecycle type
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
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
an hour 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
