Attached release notes detail improvements and fixes for RadiantOne v7.3.21.
Customer Support Portal
https://radiantlogic.zendesk.com/hc/en-us/articles/4414337255700-New-Radiant-Logic-Help-Center#new-radiant-logic-help-center-0-0
/hc/theming_assets/01HZPGPEX84XX6AFH9F52ZEAJJ
Welcome
Explore the new features of the new Help Center, Knowledgebase and Community.
custom
https://developer.radiantlogic.com/
/hc/theming_assets/01HZPGPF1N62PEX8WEYKERPM50
Developer Portal
Learn about the detailed offerings and access the documentation to help get you started.
custom
https://support.radiantlogic.com/hc/en-us/community/topics
/hc/theming_assets/01HZPGPF6379TZRQEB48TYBA4F
Community
Join discussions with other RadiantOne users.
custom
https://customer.academy.radiantlogic.com/learn
/hc/theming_assets/01J09S6MG4F5KSRCPPWKD7F7B7
Training Academy
Online learning hub offering self-paced on-demand courses, weekly instructor-led workshop options, and easily consumable training modules.
7.3 EOL, guides, ticket history
Comments
We are using FID v7.3.17 and I have carried out the steps outlined in "Mitigation steps for the Log4J vulnerabilities in RadiantOne JMSHA servers".
So, it is still recommended to upgrade to this patch, if the purpose is solely to address the Log4j issue?
Hi Raymond, good question! A support ticket has just been opened for you to discuss this request. You should have received an email notification with the ticket number.
Rachel DeHoyos
Radiant Logic Customer Experience Manager
Hi Raymond,
So yes it is still recommended to update to the latest version, especially when java changes are involved. The patch we did addressed that specific CVE, but it is still recommended to update.
Thank you,
Andrew
Please sign in to leave a comment.