‎27-04-2023 11:32 PM - edited ‎28-04-2023 04:33 PM
Hello,
We are finding that for our SaaS applications in HOPEX - the Obsolescence Risk is calculated as Unknown.
See screenshot below:
What do other users do for SaaS applications?
Ideally, we would prefer if HOPEX calculated the Obsolescence risk as Low, since SaaS applications don't have that risk.
‎02-05-2023 04:30 PM
We need both behavior because some of those packages may have support date linked to the versions and/or modules you pay for and you use.
Meanwhile, a quick workaround solution could be to define a software technology "SaaS" with proper support date (corresponding to your obsolescence politics) and linked to all of your SaaS applications.
You may create different "templates" (if I may name this software technology a template) corresponding to your different warning levels you want to address.
‎02-05-2023 04:11 PM
Hi @PBessodes ,
Thank you so much for response.
Two feedbacks.
‎02-05-2023 09:39 AM
Hello,
The usual practice is to define a software technology representing your SaaS application ("business package"). Your own use (with your parameters and potential personalizations) should then be an application based on this technology. You need to capture support dates for the technology and then obsolescence risk should be calculated the standard way for your application.
‎28-04-2023 06:03 PM
Would appreciate any insights from anyone who's had to deal with this question before.