How Does Validation Of Request Messages Work?
(Doc ID 1550463.1)
Last updated on MARCH 08, 2017
Applies to:Oracle Health Insurance Claims Adjudication - Version 2.13.1 and later
Information in this document applies to any platform.
You can use soapUI to test with sending Request Messages to the Oracle Health Insurance Components products. Below questions about 'validation' are answered.
A Request Message is sent to OHI with soapUI, but no value is provided for a mandatory field (a field that shows mandatory in the UI with a * (asterisk)).
When you check the result in the User Interface, the data from the Request Message is available in the UI. But you get an error for the mandatory field that has no value when you query the record in the UI (Error: A selection is required. You must make at least one selection).
So values can be sent in, but there is no validation done. What is cause of this?
If validation is enabled, the validation is done with the XSD specification.
What is the easiest way to find or verify these .XSD files?
How can you validate a Request Message in soapUI?
How are requests used for File Based Import validated?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|