Last updated on JUNE 14, 2017
Applies to:Oracle Public Sector Revenue Management - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
The goal of this article provides details why a Form validation does not check Field length for fields in BO_DATA_AREA.
Attempt to add a Registration Form via XAI having a long name.
BO for the Registration Form: C1-BusinessRegistrationForm has the following schema section:
It maps to the BO_DATA_AREA. The name is mapped to field ENTITY_NAME which has length of 64.
Try to import a registration Form via XAI having an owner name larger than 64 chars and see how the form validation bypasses this issue and the form gets posted normally.
Add a new XAI Inbound Service using BO C1-BusinessRegistrationForm (CM-BusinessRegistrationForm-test)
From Admin menu, XAI Submission, submit the a request to add a registration form.
Notice the length of the following name fields in the request:
Owners / Responsible Parties (68 chars) - longer than 64 chars
USER55, RP 123456789012345678901234567890123456789ABCDEFGHIJKLMNOPQR
Navigate to the created Registration Form
Owners / Responsible Parties Name displayed on the form: 68 chars displayed (same as in xml request)
Click Validate on the Form:
The problem is here! No validation error is raised due to the long Owners / Responsible Parties Name.
Post the form.
Go to the created Owner / Responsible Party person:
Notice the name has been truncated and only 64 chars were saved
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms