[KULRICE-8074] Getting client side validation errors when no errors are present Created: 04/Sep/12  Updated: 03/Oct/14  Resolved: 17/Sep/12

Status: Closed
Project: Kuali Rice Development
Component/s: Quality Assurance
Affects Version/s: 2.1.1
Fix Version/s: 2.2.0-m4, 2.2
Security Level: Public (Public: Anyone can view)

Type: Bug Fix Priority: Blocker
Reporter: Jerry Neal (Inactive) Assignee: Brian Smith (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: JPEG File screenshot-1.jpg    
Issue Links:
cloned from KULRICE-7208 Template Closed
fixes KULRICE-8038 Travel Account Maintenance (New) acco... Closed
is relied upon by KULRICE-8066 WorkFlowDocTypeBlanketAppIT fails wit... Closed
Similar issues:
KULRICE-7026Alter behavior of client side validation
KULRICE-11109Server-side Validation Error on valid dates
KULRICE-7312Client-side validation tooltip doesn't open (for timed interval) when other validation treatment is applied
KULRICE-6661Client side validation errors not getting removed when value changed with a date picker
KULRICE-7772Client side validation no longer properly notifies the user with a popup nor jumps them back to the page error list
KULRICE-6835Issues with client side validation
KULRICE-4708Support for client side field validation
KULRICE-11729Selectively disable client side validation on KRAD collections
KULRICE-7889Client-side summaries on save feature lost
Rice Team: QA
Rice Module:
KAI Review Status: Not Required
KTI Review Status: Not Required


In a few different places (like people flow edit and adding note attachments), we are getting a client side validation error that says 'validation.null'. The fields are valid as well and there is no way past the error. See screenshots

Comment by Jerry Neal (Inactive) [ 04/Sep/12 ]


Please make this issue your priority.


Comment by Jerry Neal (Inactive) [ 05/Sep/12 ]


Did you determine this was fixed yesterday? If so please resolve.


Comment by Brian Smith (Inactive) [ 05/Sep/12 ]

It exists AFTER the update, so something between my last update and my newest update is what broke it. It did not exist locally before I updated.

Comment by Brian Smith (Inactive) [ 05/Sep/12 ]

I tracked down the issue to a method that was added in validationPattern which converts patterns into constraints and makes some false assumptions:

ValidCharactersConstraint constraint = new ConfigurationBasedRegexPatternConstraint();
return constraint;

1. some pattern regex does not have a javascript equivalent - this is what causes the error to appear - it fails the regex check obviously
2. no labelKey and validationMessageParams are set so all messaging is lost - thus you are seeing "validation.null"

Not sure what to do here and what the intent of this method was to begin with. Is it intended to be a stop gap or a permanent solution (if its supposed to be a permanent solution it has serious problems noted above).

Comment by Jerry Neal (Inactive) [ 06/Sep/12 ]


Can you determine who made the update and reach out them for more information?


Comment by Brian Smith (Inactive) [ 07/Sep/12 ]

This will be fixed after Martin does a rollback of the code and Peter merges with trunk.

Comment by Peter Giles (Inactive) [ 13/Sep/12 ]

Is the fix version on this correct? Can this issue be resolved now that Martin's rollback has been applied to trunk?

Comment by Jessica Coltrin (Inactive) [ 30/Oct/12 ]

closing all 2.1.2 Jiras

Generated at Sat Jul 11 00:50:24 CDT 2020 using JIRA 6.1.5#6160-sha1:a61a0fc278117a0da0ec9b89167b8f29b6afdab2.