You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As the Software object has End of Software Support as a field we should enable the ability to use this date as a hard limit on Software being valid. My thinking is that you'd simply look at that field on the Software object during the validation Job and if the current date is past the EOS date then the Software is invalid, even if the Valid Until on ValidatedSoftware is in the future or undefined.
Use Case
For some enterprises the policy is that any End of Support software is considered non-compliant and should not be in use on Devices.
The text was updated successfully, but these errors were encountered:
jdrew82
changed the title
Use EOSAs Hard Limit for Being Valid
Use EOS As Hard Limit for Being Valid
Dec 2, 2024
Environment
Proposed Functionality
As the Software object has End of Software Support as a field we should enable the ability to use this date as a hard limit on Software being valid. My thinking is that you'd simply look at that field on the Software object during the validation Job and if the current date is past the EOS date then the Software is invalid, even if the Valid Until on ValidatedSoftware is in the future or undefined.
Use Case
For some enterprises the policy is that any End of Support software is considered non-compliant and should not be in use on Devices.
The text was updated successfully, but these errors were encountered: