When setting values for custom properties (e.g. license terms) the correct type should be enforced in UI/backend/both to avoid the user entering invalid data and that data being saved incorrectly.
The specific example we have is where the custom property value is an integer but the user enters a value > supported by the relevant Java number type.
Steps to Reproduce:
1) Either edit a existing license or create a new license
2) Go to the terms accordion and in the "Number of Concurrent Users" term enter a number outside the Java integer range (-2,147,483,648 to +2,147,483,647) (e.g. 10000000000)
3) Click save and close
Actual Result: The displayed value is 1410065420 (if 10000000000 entered)
Expected Result: Value should not save and the user should be warned that the number entered is outside the valid range