Login to follow
OutSystems UI

OutSystems UI (ODC)

Supported
Stable version 2.24.0 (Compatible with ODC)
Uploaded on 11 Aug (9 days ago) by OutSystems
OutSystems UI

OutSystems UI (ODC)

Details
Detailed Description

With dozens of responsive UI patterns, this framework is integrated with OutSystems and allows you to build the UI of your app using low code.

Key features:

  • More than 70 UI patterns
  • Easily customizable and extendable design system
  • Responsive UI
  • Right-to-left support
  • Accessibility compliance with WCAG 2.1
  • Actions to deal with different device types
  • Built for Web and Mobile apps

Find out more at https://outsystemsui.outsystems.com

Limitations
Release notes 

What's New

  • ROU-11920 - Now, Dropdown Search and Dropdown Tags will be using the latest version of their library provider, VirtualSelect v1.1.0.
  • ROU-12024 / RPM-5688 - Now, French (fr) and German (de) are available in Multilingual Locales.

Fixed Issues and Improvements

  • ROU-11919 - Fixed an issue where the Dropdown Search/Tags components became unresponsive and threw console errors when the extensibility attribute allowNewOption was used.
    The issue was fixed by updating the Virtual Select library.
  • ROU-11926 / RPM-5839 - Fixed an issue where restoring a page from cache (using the back button) caused console errors when an AnimatedLabel component was conditionally rendered using an if statement based on isDataFetched from an Aggregate or Data Action.
  • ROU-11937 - Fixed an issue that caused the Dropdown Search/Tags components not to close when clicking on another dropdown.
    The issue was fixed by updating the Virtual Select library.
  • ROU-11952 / RPM-5882 - Fixed an issue where PullToRefresh was unintentionally triggered when closing the BottomSheet component.
    This occurred when the BottomSheet was placed in the Content placeholder of the native layout instead of the Bottom placeholder, and the component was closed via drag gestures.
  • ROU-12023 / RPM-5899 - Fixed an issue that caused the Pagination component's accessibility not to work as expected.
    This occurred when more than 5 page buttons were present in the pagination block at runtime.
  • ROU-12050 / RPM-5952 - Fixed an accessibility issue where the nav element used for the menu remained focusable in desktop layouts, causing unnecessary tab stops.
    The element is now removed from the tab order on desktop to improve keyboard navigation and prevent false positives in accessibility evaluation tools.
  • ROU-12062 - Fixed an issue that caused the BottomSheet component to not respond to gesture events on certain tablet devices.
    This occurred when running the application on tablets like the iPad Pro in landscape mode, which are classified as a Desktop device by the platform.
  • ROU-12066 / RPM-5986 - Fixed an issue that was preventing FocusTrap from behaving as expected.
    This occurred due to a regression on the BottomSheet, DropdownServerSide, Notification, SideBar, and Submenu.
  • ROU-12067 / RPM-5985 - Fixed a performance issue in the AccordionItem component caused by unnecessary layout reflows.
    This was especially noticeable when typing quickly in input or textarea fields, resulting in screen lag.
  • ROU-12091 / RPM-5932 / RPM-5991 - Fixed an issue where SideBar and BottomSheet child components sometimes lost keyboard navigation (A11Y).
    This occurred when they contained components like Tabs, which manage their own focusable elements, preventing proper focus trapping.
  • ROU-12094 / RPM-5969 - Fixed an issue that caused the DropdownSearch/Tags components not to properly deal with focus on other elements when opened.
    When these components were active and another interactive element (e.g., an Input or Text Area) was clicked, focus would incorrectly return to the closing component after a brief shift, instead of remaining on the newly selected element.
    The issue was fixed by updating the Virtual Select library.
  • RPM-6040 - Fixed an issue where the open Dropdown Search/Tags failed to close.
    This occurred when a user interacted with another Dropdown Search/Tags, causing multiple dropdown interfaces to appear simultaneously.
    The issue was fixed by updating the Virtual Select library.