[KULRICE-9599] Validation framework improvement for handling collections differently Created: 22/May/13  Updated: 12/Aug/13  Resolved: 14/Jun/13

Status: Closed
Project: Kuali Rice Development
Component/s: User Interface
Affects Version/s: 2.3
Fix Version/s: 2.3.0-m3, 2.3
Security Level: Public (Public: Anyone can view)

Type: Improvement Priority: Major
Reporter: Brian Smith (Inactive) Assignee: Brian Smith (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Similar issues:
KULRICE-4543Exception and incident handling framework improvements
KULRICE-9903Validation Framework alerts for ARIA tags
KULRICE-2056Improve handling of hidden values in lookup framework.
KULRICE-6743Document the UI Framework - State-based Validation
KULRICE-4737Improve configuration of development framework
KULRICE-3851Nested collections of a reference throwing exception when maintenance document is canceled and not validating required
KULRICE-6838UIF Framework - Framework Improvements (AJAX Improvements)
KULRICE-7472CLONE - UIF Framework - Framework Improvements (AJAX Improvements)
KULRICE-6671UI Framework - Framework code improvements
KULRICE-9598Validation framework improvement to cut data that is determined to be default
Rice Module:
KRAD
Application Requirement:
Rice
KAI Review Status: Not Required
KTI Review Status: Not Required
Code Review Status: Not Required
Include in Release Notes?:
Yes

 Description   

Improve and possible rewrite how the validation framework handles collections and their fields, specifically in terms of error bubbling with server messages (especially if we change how collections render this will be broken - probably broken in LightTable) and order array (is broken in LightTable for sure) so it doesn't list each field in order as this can get infinitely large.


Generated at Mon Mar 30 05:42:38 CDT 2020 using JIRA 6.1.5#6160-sha1:a61a0fc278117a0da0ec9b89167b8f29b6afdab2.