WebEOC Nexus 10.11 Release Notes

These notes describe updates in the WebEOC Nexus 10.11 release scheduled for June 24, 2025. More information is available in this help center or by contacting the Juvare Support Center at +1 (877) 771-0911 or support@juvare.com.

New Feature

Mark New Data as Read

A red dot indicates when data on boards, dashboards, menus, and maps is new, and a user has not yet viewed it. You can use the Mark New Data as Read icon to remove these indicators from the main menu and next to the affected items on the Boards, Dashboards, Menus, and Maps landing pages.

Mark New Data As Read icon

With a single click, you can now mark this new data as read, improving focus and reducing clutter during shift transitions or after large data updates. Using this new feature, you can:

  • Avoid visiting each board, dashboard, menu, or map manually.

  • Quickly reset the new data state to reflect only the most recent updates.

  • Experience a streamlined, clear, and consistent data display, helping you focus on what matters now, not what changed while you were away.

See Mark New Data as Read for Boards, Dashboards, Menus, and Maps for details.

Enhancements

  • Improved Login Experience: When you log in to WebEOC Nexus 10.11, the following enhancements are available:

    • Modernized Login page: The page’s design now has a clean, simplified layout using components standard in other Juvare products to help unify branding to improve the user experience, consistency, and accessibility. The Login page has also been optimized for desktop, tablet, and mobile devices.

    • New Disclaimers Panel: A new, collapsible disclaimers panel now appears beneath the login fields on the Login page. It prominently displays the agency-specific terms and conditions. See Configure System Messages for details on setting the terms and conditions, which can be configured using HTML and markdown for rich text formatting.

    • New Login policy: A new window opens for users before they are able to log in that displays the Login policy. After the user accepts the policy, this page no longer displays at login unless the contents of the policy are updated. After accepting the policy, the user can click a button to log in. See Configure System Messages for details on setting the Login Policy, which can be configured using HTML and markdown for rich text formatting.

    • Improved Forgot Password Workflow for SSO users: We’ve introduced a streamlined and intuitive password recovery experience if you use SSO using your organization’s identity provider (IdP) to log in. You receive immediate feedback on token and email validity. Screens for password reset completion or error states are now responsive and mobile-friendly. This updated workflow:

      • Aligns the login experience with accessibility and usability standards.

      • Ensures agency terms are acknowledged transparently before login.

      • Improves success rate and clarity of password recovery flows.

      See Reset Your Password in WebEOC Nexus for details.

      While the Forgot Password? Workflow has been improved, the Forgot Username feature, previously available from the Login page, has been removed.

    • Improved Login experience for non-SSO JLS users to clear sessions: If users are logging in using JLS, but not SSO using their organization’s identity provider (IdP), a new button has been added to the WebEOC Nexus Login page, Login as Different User. This button displays if there is a valid active JLS session for the current user. Clicking this button clears the current JLS session, removing tokens, and reloads a clean Login page. This allows the user to start a new session with a different user account, clearing any existing JLS sessions that, in previous WebEOC Nexus versions, occasionally got stuck or corrupted and could not be resolved via password or authenticator resets. With this new functionality, users can resolve these types of issues without intervention from support or an administrator. Fast user recovery is essential: downtime or login problems will no longer delay emergency coordination efforts.

      If there is no active session for the current user, only the Login button, and not the Login as Different User button, displays on the Login page.

      Refer to Log In to WebEOC Nexus for details.

    • Additional enhancements include:

  • Support for Arabic file names: To improve internationalization, we have enhanced OutputBinary header encoding to support Arabic file names and non-Latin characters. Arabic file names now display correctly when retrieved via the REST API. Additionally, Arabic-named files can now be uploaded and retrieved with proper file name display. Previously, Arabic file names appeared as unreadable or special characters when downloaded via the REST API.

  • Auditing when users are added or removed from a position: Adding or removing a user from a position via the REST API now correctly generates audit log entries. Previously, these actions were not logged.

  • Various security improvements.

  • Updated Help Center link for Unified Command Platform (UCP): The link to the Admin and User Help Centers has been updated for UCP instances to open a version of help that includes the correct product name. In previous versions, the help links opened Help Centers that referred to WebEOC Nexus.

Updates to Help Pages

Added these topics to the WebEOC Nexus Admin Help Center:

Resolutions

  • Improved Board Deletion Logic: Board deletion logic has been updated to remove related data before the board itself is removed. Previously, if a board deletion failed mid-process (for example, due to database issues), some data could be left behind, causing inconsistencies, even though the board appeared to have been successfully deleted. Now, if an error occurs during cleanup, the board remains visible, allowing users to retry board deletion or to contact support.

  • Homepage loading errors fixed: In WebEOC Nexus 10.9, some homepages failed to load if a map that had been added by a Quick Action had missing annotation permissions. With the fix, homepages now load reliably even if a map added by a Quick Action lacks associated annotation permission records.

  • Improved experience with large notifications: Some users experienced crashes or long loading times when opening notification details, especially when the message had thousands of recipients. We optimized how the system processes large recipient lists and file attachments. The page now opens much faster, even when notifications include 4,000+ recipients or the system has tens of thousands of files. You can now view large notifications without delays or timeouts, improving reliability for high-volume users.

Previous Versions

Release notes for previous versions are available here.