Expanders 5.16.0
· One min read
Changes and improvements
UniqueConstraint
This Expanders version introduces a new Element UniqueConstraint. Each DataElement can have one or more of these UniqueConstraints.
Each one lists a number of Fields. The constraint will generate a check to make sure it is not possible to create 2 instances. with the same values for these Fields.
It replaces the option uniqueKey
and improves on it:
- You can have more than one UniqueConstraint.
- The check uses a dedicated query instead of a Finder, so that it will work even for
null
values. - No need to explicitly define a Finder.
- No more loosely typed String to define the Fields.
ConvertUniqueKeyOptions Transmuter
You can automatically convert uniqueKey
options by using the ConvertUniqueKeyOptions transmuter.
In the µRadiant (version 1.8.3+), right-click on the Application and select Convert Unique Key Options
.
Removed Options
Some of the Options have expired and have been removed:
legacy.logicDataMethods.reenable
legacy.oldCollectionMethods.reenable
legacy.oldSearchMethods.reenable
legacy.relationRetrievalMethods.reenable
legacy.searchDataRefMethods.reenable
legacy.struts.defaultStyle