Field Precision Value Is Entered In CM But It's Not Being Validated
(Doc ID 2149932.1)
Last updated on JUNE 24, 2016
Applies to:Oracle Utilities Mobile Workforce Management - Version 2.2.0 and later
Oracle Real-Time Scheduler - Version 2.2.0 and later
Information in this document applies to any platform.
The field precision value is entered, but its not validating the same value. Why?
There is a field with precision value defined as 240 characters and type as Varchar2, but the same field is accepting any number of characters while creating and completing an activity.
There should be a validation triggered for the field while enter some value into it but, the validation is not being triggered.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!