USoft 11.2
September 2026
The release notes are an addition to the product information in the Knowledge Base.
The Knowledge Base describes the most recently released version of the software. By contrast, the Release Notes in this document describe changes by individual patch release.
There is no USoft 11.1 release. USoft 11.2 is the first version after USoft 11.0.
This page contains the following sections:
- Introduction to USoft 11.2.
- New Functionality and Enhancements in USoft 11.2.
- Vulnerabilities.
- Known Problems and Workarounds for USoft 11.2.
- Third-Party License Notices.
Introduction
USoft Product Documentation
For general product documentation, please go to the Knowledge Base at docs.usoft.com.
Context Help
USoft Definer and USoft Authorizer have "What's This?" context help on individual fields. To get help on a field in a specific window, click the "What's This?" icon (the question mark) on the ribbon bar, then click in the field.
USoft Windows Designer and USoft Web Designer have context help for individual properties of controls. To get help on a property of an object, open the Property Inspector for the object, and click on the property name. The help text appears in the lower area of the Property Inspector. You may have to toggle the '?' button to get it displayed.
USoft Studio has extensive in-product help of its own. Click the Help menu, or use the Help tile in the Home page, or click '?' icons for help on individual pages.
USoft Support
For all communication related to this release, please use the USoft Customer Portal.
License
Before you can use USoft Developer Series products, you must have a valid license. To obtain a valid license, contact USoft support through the USoft Customer Portal.
Find details in the "USoft for administrators" section on docs.usoft.com.
Getting Started
Follow these general steps to get started with USoft. Please find details of these steps in the "USoft for administrators" section on docs.usoft.com.
- Make sure that your system and RDBMS satisfy USoft system requirements.
- Install the USoft software.
For details of the following steps, search "USoft Binder" on docs.usoft.com.
- Set up a new project using USoft Binder.
- Start the USoft product from the work area of the USoft Binder.
New Functionality and Enhancements in USoft 11.2
This section provides you with an overview of the most important new functionality and enhancements in the product.
License management
In this release, USoft has modernised license management. It replaces an earlier approach that no longer matched the way the USoft platform is deployed and licensed. The result is a licensing lifecycle that is more robust, more automated, and easier to follow.
For details, see USoft license management.
What is new:
- A redesigned licensing framework that covers issuing, distributing and enforcing licenses.
- Support for enforcement in the cloud and for enforcement on your own servers (on-premises).
- One central licensing process, which improves governance and operational control.
- A stronger basis for automating license management and for letting you manage licenses yourself in future releases.
Benefits:
- Greater transparency about how licenses are used, what you are entitled to use, and when licenses must be renewed.
- More consistent enforcement of license terms, which reduces the risk of breaching those terms and the risk of unexpected interruptions.
- Cloud-based enforcement reduces manual work and the risk of mistakes during operation.
Rules Service scaling
In version 11.2, the Rules Service can automatically shut down engines that have not been used for a certain period. This is called scaling down. Shutting down an engine frees resources and releases the license that the engine was using. Scaling down always takes the specified minimum number of engines into account. The number of engines is never reduced below that minimum.
The default timeout is 15 minutes. You can change it when you configure the Rules Service. You can also set it to unlimited. If you do, engines are never scaled down.
Version 11.2 also introduces Peak Engines. A Peak Engine works in the same way as a normal engine, except that it uses a separate concurrency allocation in the license. When all engines allowed by the license are in use, the Rules Service starts additional engines under the Peak Engines allocation. This is useful in production environments in which the regular license limit is reached.
Peak Engines exceed the number of engines specified in your license. USoft support therefore monitors how many Peak Engines you use, and may contact you about increasing the number of engines in your license.
When the Rules Service scales down, it shuts down running Peak Engines first. Engines that use the normal license are only scaled down when no Peak Engines are running. An incoming request is always assigned to an available normal engine first, and to a Peak Engine only if no normal engine is available.
For details, see Scaling.
SCIM user and group provisioning
In version 11.2, the USoft platform supports SCIM (System for Cross-domain Identity Management). SCIM is a standard for creating and maintaining users and groups in an application automatically, based on an external identity provider. Instead of maintaining application accounts by hand, your administrator connects your identity provider to the USoft SCIM endpoint. After that, changes that are made to users and groups in the identity provider are sent to the USoft platform automatically. These changes include creating, changing, deactivating and deleting a user.
For details, see Introduction to SCIM.
What is new:
- A SCIM 2.0 endpoint for creating, updating, deactivating and deleting users.
- Group provisioning, so that group membership in the identity provider can be mapped to USoft authorisation roles.
Benefits:
- A new employee gets access without a manual account request. Someone who leaves the organisation loses access as soon as they are deactivated centrally.
- Fewer accounts that are out of date or that no longer belong to anyone. This reduces both findings in audits and unnecessary license consumption.
- One authoritative source for identity data, which keeps USoft authorisation aligned with the directory of your organisation.
Support for .NET 10 components
In version 11.2, USoft supports building and using RDMI components that are based on .NET 10. Previously, you could only develop components for .NET 6.
What is new:
- You can build and deploy components that target .NET 10.
- You can continue to use the most recent Microsoft development platform and the tools that come with it.
- You can use the improvements in performance, security and developer productivity that .NET 10 offers.
Benefits:
.NET 10 introduces a range of improvements, including:
- Better application performance, through optimisations in the runtime and in the JIT compiler.
- Extended security capabilities and continued improvements to the platform.
- Better developer productivity, through the most recent C# language features and tooling.
- Continued support for applications that are designed to run in the cloud and on more than one operating system.
.NET 10 is a Long-Term Support (LTS) release. Microsoft supports an LTS release for three years. This support includes security updates, bug fixes and servicing updates. .NET 10 was released on 11 November 2025 and is supported until 14 November 2028.
Vulnerabilities
This section summarises the findings of vulnerability scans that were assessed for this release. Each finding is classified as patched, not applicable, a false positive, or low risk. The classification is based on the component versions that are present in the USoft product environment and on the way those components are used.
Summary
| Category | Component type | Status |
|---|---|---|
| Linux / Ubuntu | Python Cryptography | Patched / not applicable |
| Linux-Windows / Java | Apache MINA SSHD | False positive |
| Linux-Windows / Java | jakarta.xml.rpc-api | False positive |
| Linux-Windows / Java | org.ini4j/ini4j | False positive |
| Windows | PowerShell | False positive |
| Windows | .NET | False positive |
| Windows | SqlClient | False positive |
| Windows | Visual Studio libraries | False positive |
| Windows / Frontend | UDesign JavaScript libraries | Low risk |
Linux (Ubuntu, container and open-source components)
1. Python Cryptography package (Ubuntu 24.04)
Reported: CVE-2026-26007, CVE-2024-26130, CVE-2023-50782, GHSA-537c-gmf6-5ccf
Assessment:
- The image is based on Ubuntu LTS 24.04, which contains backported patches.
- All relevant CVEs are either fixed or not applicable.
Result: not vulnerable. These scanner reports are expected false positives, caused by the way the package version is numbered.
2. Apache MINA SSHD
Reported: CVE-2022-45047
Assessment:
- The vulnerability affects SSHD version 2.9.1 and earlier.
- The version in use is 2.16.0, which is not vulnerable.
- The vulnerable class is not used.
Result: false positive. The vulnerability cannot be exploited in this environment.
3. ini4j (org.ini4j/ini4j)
Reported: CVE-2022-41404
Assessment:
- ini4j is used by a library, but it is not used to read
.inifiles that a user supplied. There is therefore no risk that the vulnerability is abused.
Result: false positive. The vulnerability cannot be exploited in this environment.
4. Java XML API (jakarta.xml.rpc-api)
Reported: CVE-2016-4570, CVE-2016-4571
Assessment:
- These CVEs apply to the mini-xml C library (msxml).
- That library is not used by this dependency.
Result: false positive, caused by an incorrect mapping of the dependency.
Windows (.NET, PowerShell and Visual Studio)
1. PowerShell and MarkdownRender mapping
Reported: CVE-2024-0057, CVE-2024-21409
Assessment:
- The scanner incorrectly maps MarkdownRender 7.2.1 to the PowerShell runtime.
- The runtime actually in use is System.Management.Automation 7.2.19, which is patched.
Result: false positive, caused by an incorrect mapping of the component.
2. .NET Core 3.1
Reported: CVE-2020-0605, CVE-2020-0606, CVE-2021-24112, CVE-2021-26701, CVE-2020-1147, CVE-2022-41032, CVE-2020-1108, CVE-2021-26423, CVE-2022-23267, CVE-2022-24464, CVE-2022-29117, CVE-2022-29145, CVE-2022-38013, CVE-2021-31204, CVE-2020-8927, CVE-2021-1721, CVE-2022-24512, CVE-2021-31957, CVE-2022-34716, CVE-2022-30184, CVE-2021-34485
Assessment:
- The scanner assumes that the .NET Core 3.1 runtime is used.
- The runtime actually in use is .NET Framework 4.6.1, which is not affected.
Result: false positive, caused by an incorrect mapping of the runtime through the CPE identifier.
3. SQL Client
Reported: CVE-2024-0056
Assessment:
- A newer version of SqlClient is in use.
Result: false positive.
4. Visual Studio and DIA SDK
Reported: CVE-2014-3802
Assessment:
- The vulnerability applies to
msdia.dllin Visual Studio 2012 and earlier. - The component actually in use is
EnvDTE.dllfrom Visual Studio 17.x.
Result: false positive, caused by an incorrect mapping of the component.
5. UDesign client-side JavaScript libraries (jQuery, Bootstrap)
No CVEs were listed explicitly.
Assessment:
- The vulnerabilities are client-side only.
- Exploiting them requires DOM injection.
- The application is not exposed externally.
Result: low risk. The vulnerabilities cannot be exploited in this environment.
Known Problems and Workarounds for USoft 11.2
DEFINER
USD-6501
In the EAR diagrammer, when you hover above one of the icons, the tooltips are displayed in the wrong location.
WEB APPLICATION
USD-5750
Given a domain with a regular expression and a custom message for that regular expression, the custom message is not used when validating from a web application.
USD-6321
In web applications, the currently selected date indicator sometimes remains active even when the date was changed (eg., by browsing to the next or previous month).
WEB DESIGNER
USD-5252 (US-991)
Web Designer can crash when it loads a page and WebView2 is not installed.
Third-Party License Notices
The USoft product set includes code licensed from RSA Security, Inc. Some portions licensed from IBM are available at http://oss.software.ibm.com/icu4j/.
The following licenses only apply to those portions of software derived from code licensed by the license holders concerned. These software components are listed below.
Apache Java
XML Parser Xerces-J and XSLT Processor Xalan-J:
<usoft install dir>\java\Redist.jar
Apache C/C++
XML Parser Xerces-C:
<usoft install dir>\bin64\xerces-c_3_2D.dll
XSLT Processor Xalan-C:
<usoft install dir>\bin64\Xalan-C_1_12.dll<usoft install dir>\bin64\XalanMessages_1_12.dll
Apache FOP (Formatting Objects Processor)
Apache FOP comes with several libraries, all of which are currently sourced from within the Apache Software Foundation. These libraries are all licensed under the Apache License. There is one exception, "xml-apis.jar", which contains code licensed by the W3C (World Wide Web Consortium, http://www.w3.org/).
Apache License Notice
This product includes software developed by The Apache Software Foundation (http://www.apache.org/).
Portions of this software were developed at the National Center for Supercomputing Applications (NCSA) at the University of Illinois at Urbana-Champaign.
This software contains code derived from the RSA Data Security Inc. MD5 Message-Digest Algorithm, including various modifications by Spyglass Inc., Carnegie Mellon University, and Bell Communications Research, Inc (Bellcore).
Regular expression support is provided by the PCRE library package, which is open source software, written by Philip Hazel, and copyright by the University of Cambridge, England. The original software is available from ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre/
The Apache license can be seen in <usoft install dir>\java\redist\apache or at http://www.apache.org/licenses/LICENSE-2.0.
BOOST Software License Version 1.0
Boost Software License - Version 1.0 - August 17th, 2003
Permission is hereby granted, free of charge, to any person or organization obtaining a copy of the software and accompanying documentation covered by this license (the "Software") to use, reproduce, display, distribute, execute, and transmit the Software, and to prepare derivative works of the Software, and to permit third-parties to whom the Software is furnished to do so, all subject to the following:
The copyright notices in the Software and this entire statement, including the above license grant, this restriction and the following disclaimer, must be included in all copies of the Software, in whole or in part, and all derivative works of the Software, unless such copies or derivative works are solely in the form of machine-executable object code generated by a source language processor.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR ANYONE DISTRIBUTING THE SOFTWARE BE LIABLE FOR ANY DAMAGES OR OTHER LIABILITY, WHETHER IN CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
XML4C consists of Apache's Xerces-C XML parser, which is distributed under The Apache Software License, Version 1.1, and International Components for Unicode (ICU), which is distributed under the X License.
ICU License - ICU 1.8.1 and later
ICU is released under a nonrestrictive open-source license that is suitable for use with both commercial software and with other open source or free software.
Open-Source license:
For the general privacy policy governing access to this site, see the Unicode Privacy Policy.
Unicode Copyright
Copyright © 1991-2020 Unicode, Inc. All rights reserved.
Definitions
Unicode Data Files ("DATA FILES") include all data files under the directories:
Unicode Data Files do not include PDF online code charts under the directory:
Unicode Software ("SOFTWARE") includes any source code published in the Unicode Standard or any source code or compiled code under the directories:
- https://www.unicode.org/Public/PROGRAMS/
- https://www.unicode.org/Public/cldr/
- http://site.icu-project.org/download/
Terms of Use
Certain documents and files on this website contain a legend indicating that "Modification is permitted." Any person is hereby authorized, without fee, to modify such documents and files to create derivative works conforming to the Unicode® Standard, subject to Terms and Conditions herein.
Any person is hereby authorized, without fee, to view, use, reproduce, and distribute all documents and files, subject to the Terms and Conditions herein.
Further specifications of rights and restrictions pertaining to the use of the Unicode DATA FILES and SOFTWARE can be found in the Unicode Data Files and Software License.
Each version of the Unicode Standard has further specifications of rights and restrictions of use. For the book editions (Unicode 5.0 and earlier), these are found on the back of the title page.
The Unicode PDF online code charts carry specific restrictions. Those restrictions are incorporated as the first page of each PDF code chart.
All other files, including online documentation of the core specification for Unicode 6.0 and later, are covered under these general Terms of Use.
No license is granted to "mirror" the Unicode website where a fee is charged for access to the "mirror" site.
Modification is not permitted with respect to this document. All copies of this document must be verbatim.
Restricted Rights Legend
Any technical data or software which is licensed to the United States of America, its agencies and/or instrumentalities under this Agreement is commercial technical data or commercial computer software developed exclusively at private expense as defined in FAR 2.101, or DFARS 252.227-7014 (June 1995), as applicable. For technical data, use, duplication, or disclosure by the Government is subject to restrictions as set forth in DFARS 202.227-7015 Technical Data, Commercial and Items (Nov 1995) and this Agreement. For Software, in accordance with FAR 12-212 or DFARS 227-7202, as applicable, use, duplication or disclosure by the Government is subject to the restrictions set forth in this Agreement.
Warranties and Disclaimers
This publication and/or website may include technical or typographical errors or other inaccuracies. Changes are periodically added to the information herein; these changes will be incorporated in new editions of the publication and/or website. Unicode, Inc. may make improvements and/or changes in the product(s) and/or program(s) described in this publication and/or website at any time.
If this file has been purchased on magnetic or optical media from Unicode, Inc. the sole and exclusive remedy for any claim will be exchange of the defective media within ninety (90) days of original purchase.
EXCEPT AS PROVIDED IN SECTION E.2, THIS PUBLICATION AND/OR SOFTWARE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND EITHER EXPRESS, IMPLIED, OR STATUTORY, INCLUDING, BUT NOT LIMITED TO, ANY WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. UNICODE, INC. AND ITS LICENSORS ASSUME NO RESPONSIBILITY FOR ERRORS OR OMISSIONS IN THIS PUBLICATION AND/OR SOFTWARE OR OTHER DOCUMENTS WHICH ARE REFERENCED BY OR LINKED TO THIS PUBLICATION OR THE UNICODE WEBSITE.
Waiver of Damages
In no event shall Unicode, Inc. or its licensors be liable for any special, incidental, indirect or consequential damages of any kind, or any damages whatsoever, whether or not Unicode, Inc. was advised of the possibility of the damage, including, without limitation, those resulting from the following: loss of use, data or profits, in connection with the use, modification or distribution of this information or its derivatives.
Trademarks and Logos
The Unicode Word Mark and the Unicode Logo are trademarks of Unicode, Inc. "The Unicode Consortium" and "Unicode, Inc." are trade names of Unicode, Inc. Use of the information and materials found on this website indicates your acknowledgement of Unicode, Inc.'s exclusive worldwide rights in the Unicode Word Mark, the Unicode Logo, and the Unicode trade names.
The Unicode Consortium Name and Trademark Usage Policy ("Trademark Policy") are incorporated herein by reference and you agree to abide by the provisions of the Trademark Policy, which may be changed from time to time in the sole discretion of Unicode, Inc.
All third-party trademarks referenced herein are the property of their respective owners.
Miscellaneous
Jurisdiction and Venue. This website is operated from a location in the State of California, United States of America. Unicode Inc. makes no representation that the materials are appropriate for use in other locations. If you access this website from other locations, you are responsible for compliance with local laws. This Agreement, all use of this website and any claims and damage resulting from use of this website are governed solely by the laws of the State of California without regard to any principles which would apply the laws of a different jurisdiction. The user agrees that any disputes regarding this website shall be resolved solely in the courts located in Santa Clara County, California. The user agrees said courts have personal jurisdiction and agree to waive any right to transfer the dispute to any other forum.
Modification by Unicode, Inc. Unicode, Inc. shall have the right to modify this Agreement at any time by posting it to this website. The user may not assign any part of this Agreement without Unicode, Inc.'s prior written consent.
Taxes. The user agrees to pay any taxes arising from access to this website or use of the information herein, except for those based on Unicode's net income.
Severability. If any provision of this Agreement is declared invalid or unenforceable, the remaining provisions of this Agreement shall remain in effect.
Entire Agreement. This Agreement constitutes the entire agreement between the parties.