Difference between revisions of "Version 5.1.0 (Server)"
m (→5.1.0.100?? - 2026-??-?? (Hotfix)) |
(→5.1.0.100?? - 2026-??-?? (Service Pack)) |
||
| Line 30: | Line 30: | ||
</div></div> | </div></div> | ||
--> | --> | ||
| − | |||
<div class="toccolours mw-collapsible mw-collapsed" style="width:100%; overflow:auto;"> | <div class="toccolours mw-collapsible mw-collapsed" style="width:100%; overflow:auto;"> | ||
<div style="font-weight:bold;line-height:1.6;"><h2 style="text-decoration:none;border-style:none">Kernel</h2></div> | <div style="font-weight:bold;line-height:1.6;"><h2 style="text-decoration:none;border-style:none">Kernel</h2></div> | ||
<div class="mw-collapsible-content"> | <div class="mw-collapsible-content"> | ||
=== Features === | === Features === | ||
| + | * The User-Group Cache has been extended by the ability to detect relation data modifications wrt. the RIGHTUID property. | ||
| + | <!-- | ||
=== Bug Fixes === | === Bug Fixes === | ||
=== Enhancements === | === Enhancements === | ||
| + | --> | ||
=== Known Issues === | === Known Issues === | ||
* Due to Configurable Unique Constraints not being implemented yet, Exclusive Access is not guaranteed on database level currently. | * Due to Configurable Unique Constraints not being implemented yet, Exclusive Access is not guaranteed on database level currently. | ||
* Custom code assembly improvements have led to the effect that obsolete "legacy" MetaClasses originating from pre-version-4 databases get in the way of building the customizing and must be either deleted or marked as abstract (setting the ClassType property to 50). | * Custom code assembly improvements have led to the effect that obsolete "legacy" MetaClasses originating from pre-version-4 databases get in the way of building the customizing and must be either deleted or marked as abstract (setting the ClassType property to 50). | ||
</div></div> | </div></div> | ||
| − | |||
<!-- | <!-- | ||
<div class="toccolours mw-collapsible mw-collapsed" style="width:100%; overflow:auto;"> | <div class="toccolours mw-collapsible mw-collapsed" style="width:100%; overflow:auto;"> | ||
Revision as of 00:02, 18 April 2026
 |
Custom code compilation errors: Implicitly abstract classes Custom code assembly improvements have led to the effect that obsolete "legacy" MetaClasses originating from pre-version-4 databases get in the way of building the customizing and must be either deleted or marked as abstract (setting the ClassType property to 50). Any valid custom classes that use abstract custom code must also be marked as such via their ClassType. Obsolete classes:
Namespaces with obsolete classes:
|
5.1.0.100?? - 2026-??-?? (Service Pack)
Kernel
Features
- The User-Group Cache has been extended by the ability to detect relation data modifications wrt. the RIGHTUID property.
Known Issues
- Due to Configurable Unique Constraints not being implemented yet, Exclusive Access is not guaranteed on database level currently.
- Custom code assembly improvements have led to the effect that obsolete "legacy" MetaClasses originating from pre-version-4 databases get in the way of building the customizing and must be either deleted or marked as abstract (setting the ClassType property to 50).
SmartStudio
Bug Fixes
- An issue where saving a situation with system MetaProperties could fail was fixed.
Plugins
Features
- The UBIK Plugin Design feature now supports Language synchronization and Localizations for system objects.
5.1.0.10003 - 2026-04-01 (Initial Release)
Kernel
Features
- UBIK Jobs: UBIK provides a new concept about how to schedule and execute tasks asynchronous on a sperate (Enterprise) Service.
Bug Fixes
- An issue where changelogs couldn't be activated for system design MetaClasses was fixed.
- An issue where a rename & removal of a MetaProperty from a MetaClass led to an error during saving was fixed.
Enhancements
- ACM Management shows sorted lists now.
- UBIK now uses industry-standard JSON Web Token (JWT) technology for authorization, enhancing security and reliability. Session tokens are transmitted via HTTP headers instead of URLs for improved protection
Known Issues
- Due to Configurable Unique Constraints not being implemented yet, Exclusive Access is not guaranteed on database level currently.
- Custom code assembly improvements have led to the effect that obsolete "legacy" MetaClasses originating from pre-version-4 databases get in the way of building the customizing and must be either deleted or marked as abstract (setting the ClassType property to 50).
MRO
Features
- MRO Signature Tasks have been introduced, which automatically displays the signee as well as the validation timestamp after the task has been signed.
- MRO Picture Tasks have been introduced, which are used to document the task status by adding a photo as finished or not finished.
- MRO Numeric Tasks have been introduced. A Numeric Task records a numeric double value (e.g., from a temperature sensor). Once a value is entered (including Not Applicable), the task is considered complete. An acceptability range and measurement unit can be defined.
- MRO Material MetaClass and business logic, providing a structured and reliable foundation for managing material data was introduced.
- MRO Goods Movement data model and business logic, enabling structured and reliable handling of goods movement processes were introduced.
- MRO Notifications data model and business logic, providing a structured and reliable foundation for handling notifications were introduced.
- MRO Workpackage -Templates (Datamodel and business logic) and were introduced.
- The MRO Workpackage template mechanism supports scheduling and asynchronous execution on an Enterprise Service now.
- A standard Datamodel for Assets and Functional Locations was introduced in MRO.
Plugins
Features
- The UBIK Plugin Design feature now takes relation property values into account for MetaProperties assigned to a MetaClass.
- System definitions generated by the UBIK Plugin Design feature now include multi-language translations for References, Relations, Units and UnitItems.
Bug Fixes
- Fixed an issue where the Template Matap Users AdminTool use case did not include all properties of the Matap User.
