What are you trying to do?
The decimal field automatically truncates any trailing zeroes beyond the first place (Ex: 10.90 on the service item is changed to 10.9 after submission). This only happens with trailing zeroes.
This truncation can cause questions when looking at the field as part of a service item as it’s unknown if the user missed a second digit or the value was indeed 10.90 when submitted. Activity log shows that the user submitted 10.9, so the data conversion is apparently happening at the UX level before the payload is being transmitted to the FS server. The ability to specify the length on the decimal field or via business rule on a service item would alleviate this while also being able to allow for further decimal points should there be a need for that.
Alternatively, the creation of a field type of “currency” which mandates a length after the decimal shouldn’t be too difficult. ISO4217 (https://en.wikipedia.org/wiki/ISO_4217) shows 9 countries with more than 2 numbers after the decimal point and no countries using a single digit. Could also have this field able to be set to country specific values that would auto-prepend the appropriate symbol for the appropriate currency and/or the correct number of values after the period (if it even applies)
Product area: Freshservice
Impact: Slows us down
