Range Check Is Triggered Incorrectly on Float Type Attributes in Configuration
Last updated on MARCH 28, 2017
Applies to:Oracle BigMachines CPQ Cloud Service - Version 2016 R2 Update 1 and later
Information in this document applies to any platform.
When adding a Range Check on a float attribute in Configuration, an alert shows incorrectly.
- Create a float attribute in Configuration > Set a default value to be 25.0.
- Select "Range Check" in Data Validation, minimum:1.0 and maximum: 100.0.
- Put the attribute on the layout and deploy.
- When coming into Configuration, click "Update" or "Save" to trigger the Range Check on the attribute.
A pop-up alert shows as follows:
Any number between 10.0 to 100.0 will trigger this alert.
The site was recently upgraded to 2016 R2 Update 1.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms