DesignStudio 3.0 Release Notes

These notes describe enhancements and resolutions introduced in the DesignStudio 3.0 release scheduled for July 27, 2026. 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 Features

Classic Styling and Nexus Component Styling

DesignStudio 3.0 introduces a new style of components, while making all previous features available in a different style.

• Classic Styling: All components from DesignStudio 2.5 and previous are included and function the same as they did in previous versions.

• Nexus Component Styling: All classic components have been rebuilt, with additional settings, styles, and display options. New components have also been added.

You can mix and match Nexus Component Styling and Classic Styling views in the same board. The only exception to this is the Details view. When you generate a Details view from an Input view, that Details view will automatically use the same components (Classic Styling or Nexus Component Styling) as the Input view. In other words, you will not have the option to select the type of components when you generate a Details view from an input view.

The components used in the view depend on whether you select the Use Nexus Component Styling checkbox when creating a view.

Nexus Component Styling is not available for Dashboard views.

Other Changes Introduced with Nexus Component Styling

• When creating Input, Child Input, List and Details views, you can select the Use Nexus Component Styling checkbox to use this styling.

• When using Nexus Component Styling, dropping a new component onto the canvas for all views opens the Properties tab on the right, showing the component's settings. All board components have been redesigned with this functionality.

• When you make updates to settings in the Properties tab on the right, they are reflected in real time; there is no need to click Confirm or Done, as you do when adding components to a view in Classic Styling.

• When creating a List view: the Wizard has changed.

  • It includes the Use Nexus Component Styling checkbox.

  • A Card Table Configuration step has been added to configure row-level Status Indicators and other settings.

• After creating a List view using Nexus Component Styling, edit it using the following components:

  • List View Settings: Enable export options, comments and share buttons, and add associated views.

  • Map Configuration: Configure the map settings for the List view.

  • Status Indicators: Define how icons and colors display for fields on boards to indicate a record’s status.

  • Table Fields: Update field configurations for List views.

• In List Views, the App Bar has been replaced with a View Header.

• When creating Filter and Search for a List view, use the new List View Settings component.

• When adding a collapsible embedded map to a List view, use the Map Configuration component in Nexus Component Styling.

New Nexus Component Styling Board Components

The following components have been added when using Nexus Component Styling:

• Accordion: Inserts a container on the canvas that stores other components that can be opened and closed using standard accordion features.

• Alert: Adds an alert message to a field. For example, use an alert if a user enters data that does not follow the required format.

• Chip: Adds a visual indicator of a status.

• History Configuration: Used to configure a History view.

• List View Settings: Configures List view settings such as enabling Comments and Share buttons, setting up filters, and adding associated view.

• Map Configuration: Used to configure map settings for a List view.

• Mini Expression: Functions the same as the Card component, except that: the mini expression component displays a smaller expression card.

• Note: Displays a note on the board.

• Return Button: Displays a button that returns the user to the previous view.

• Scripts & Styles: Provides you with a coding shortcut by letting you view and modify the scripts and styles used in the board without opening the board in Code mode.

• Section: Functions identically to the Header component in Classic Styling.

• Share Button: Inserts a button on the board that gives board users access to Share Links, where users can quickly generate and share direct URLs to WebEOC Nexus board views.

• Status Indicators: Lets you define custom icons and colors to display for records on boards to indicate a record’s status.

• Table Fields: Used to edit the field configuration on List views.

• Toggle Radio: Inserts buttons on the canvas. Like a Radio component, a user can select one button at a time.

Components with New Settings or Styles in Nexus Component Styling

The following components have additional settings when using Nexus Component Styling:

• Address

• Auto Number

• Card

• Checkbox

• Date

• Date/Time

• Email

• File

• Filter Pill

• Multiple Files

• Number

• Phone

• Radio

• Select

• Text

• Text Area

• Time

New History View

You can create a History view for an Input view, used with List views. When you click a record on the List view, the slide-out panel displays a History tab with the history of the changes to that record. See Create a History View for details.

This feature is available in Nexus Component Styling only.

Add Comments and Share Buttons to Views

You can add a Comments and Share button to both Classic Styling and Nexus Component Styling views.

Add a Comments Button

When you use Classic Styling, you can add a Comments button to views using the App Bar.

When you use Nexus Component Styling, you can:

• Add a Comments button to Details views using the App Bar.

• Add a Comments button to List views using the List view Settings component.

Add a Share Button

When you use Classic Styling, you can add a Share button to views using the App Bar.

When you use Nexus Component Styling, you can:

• Add a Share button to Details views using the App Bar.

• Add a Share button to List views using the List View Settings component.

• Add a Share button to Input and Details views using the Share Button component.

Resolutions

Forms & logic

• Fixed an issue where using conditional logic on a text area component with Rich Text formatting did not work. Conditional logic now works correctly when a Rich Text text area is part of the condition when building boards.

• When creating a form, calculated fields using JavaScript did not work correctly. Number values that were supposed to display a total instead displayed the value “true.” Now, calculations using JavaScript display the correct result.

• Form creators can now control which file types are allowed for attachments, resolving attachment errors on Mac.

List, Details & Dashboard views

• Fixed an issue with dashboards created in DesignStudio and viewed in WebEOC. If you applied a filter to the dashboard in WebEOC, the Full Screen mode option no longer worked. With the fix, the Full Screen mode option works for dashboards after you apply a filter to the dashboard.

• Fixed an issue with exporting and importing a board in JSON format. If you exported a board in JSON format, then created a new board and imported that JSON file as the basis for the board, some board views and resources were not included in the import. With the fix, an imported board in JSON format includes all views and resources.

• Fixed an issue that occurred if you had unsaved changes in a view, then added a resource. The Confirm Switch modal prompting that changes should be saved did not display, and unsaved changes in the view were lost. Now, if you have unsaved changes and attempt to create a resource, the Confirm Switch modal prompts you to confirm, preventing accidental loss of work.

• Fixed an issue where, when configuring a View Link component, Input views in the board did not display as options in the View drop-down list and could not be opened using a View Link. Now Input views can be selected as part of View Link configuration.

• Fixed an issue where data entered in a child input view did not display in the child table on the parent Details view.

Design experience & Board Workspace

• Fixed an issue for the Date and Date/Time components. When you added a record on an Input view, the placeholder and calendar icon displayed for a very short time and then disappeared. Additionally, these components did not allow manual entry. Dates could only be selected from the picker. With the fix, when adding a record, the placeholder and calendar icon display and you can enter dates manually.

• Fixed an issue where if you were working in Code mode and saved changes, then attempted to publish the board, a confirmation message to save the changes displayed, even though the changes had been previously saved. With the fix, after saving changes in Code mode, there is no prompt to save the changes again during the publish process.

• Fixed an issue that occurred when creating a List view. If an error message was displayed when the List view wizard was open, the application stopped responding. The application no longer hangs if an error message appears over the List View creation wizard.

• In previous versions, the Details option had been incorrectly hidden on the View menu in the Board workspace. With the fix, the Details option displays on the View menu.

• Fixed an issue with the color of the Help icon that displayed if a user added help text to a field. In previous versions, in dark mode, the help icon was displayed in a dark color which was not visible. Now, help icons are white on boards viewed in dark mode.

• Fixed an issue where, when making a change in Design view, then switching to Code view and back to Design view, the view changes were not detected. If you tried to switch to another view or create a new view, the Confirm Switch dialog did not display. Now, the Confirm Switch dialog opens in this scenario.

Accounts

Fixed issues when adding a Guest account. DesignStudio created these accounts with an expiration date that could not be edited, and users with Guest accounts could log in after their account expiration date. With the fix, Guest accounts are not created with automatic expiration dates. Expiration dates on these accounts can be edited. After the account expires for that particular organization, then users cannot log in to that organization as a Guest.

Previous Versions

Release notes for previous versions are available here.