Configurable Decimal Places in Double field.

How: Double fields should store zeroes behind the dot instead of rounding it to full numbers. This should either be saved exactly as the user provided the input, or the field should be configurable to hold a defined number of decimal places.

Why: Relevant information to be kept especially for measured/calculated values. The decimal places are important because it indicates the accuracy in scientific/technical context.

Example: pH=7 is not the same as pH=7.0 or pH=7.00 The decimal places indicate the accuracy of the value provided. Currently all three values would be rounded to "7" when entered in a double field.

For Who: Akzo specificly but als applicable for others.

Impact:

Additional context:

As a workaround, for any numerical attribute we are currently using a Regular Expression on string-fields to make sure the decimal places are kept. This is a workaround but is now causing issues for us because:

a) we cannot query on those fields (because they are string fields)

b) We cannot run calculations on those numbers using expression engine.

This is now becoming a critical issue for us as we are onboarding one of our Business Units and their legacy system supports decimal places AND calculations. For this Business Unit it will not be acceptable if Inriver cannot offer the same functionality as they currently have.