Details
-
Type:
Bug Fix
-
Status:
Reopened
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: Backlog
-
Component/s: Development
-
Security Level: Public (Public: Anyone can view)
-
Labels:
-
Similar issues:
KULRICE-7065Uppercasing not working KULRICE-4606When a new campus code value is added, the campus name and campus short name always convert to uppercase. KULRICE-7060KIM Person Maintenance screen allows a new user to be created with mixed-case or uppercase letters in Principal Name field KULRICE-11107AFT Failure KRAD LIbrary Widget Suggest Auto-Query Configuration requires capitalization to work now (uppercase) KULRICE-10303Add ForceUppercase to metadata model and default into DD KULRICE-5798 Add forceLowercase to AttributeDefinition and AttributeField KULRICE-5282Uif Framework - Binding needs to look at forceUppercase KULRICE-4025 Direct inquiry does not work properly in some conditions KULRICE-10957Labs Lookup Default and Labs Lookup Results Limit failures due to capitalization (uppercase) KULRICE-6958 Cleanup EL Variable Names -
Rice Module:KRAD
-
KRAD Feature Area:UIF Component
-
KAI Review Status:Not Required
-
KTI Review Status:Not Required
-
Include in Release Notes?:Yes
Description
Currently when uppercaseValue is set to true on input field, the value is uppercased by using CSS. However, this only uppercases the value for display, it does not actually uppercase the value that is submitted. We need to change this or add functionality to uppercase the value as well
Issue Links
- cloned from
-
KULRICE-8803
Inquiry bases logic on readonly for building inquiry or direct inquiry based on the readonly flag of the Inquiry widget, not the field it applies to
-
- is related to
-
KULRICE-9226
AttributeDefinition forceUpperCase Doesn't Work
-
Activity
Added functionality to krad.utility.js uppercaseValue function to actually convert the string to uppercase so that it will be persisted as an uppercase string
I think we should probably be checking this server side as well (see linked issue). When doing the binding we can read the uppercase information from the attribute definition and perform uppercase if needed.
I've noticed that uppercaseValue isn't set when forceUppercase in the data dictionaryis set.
uppercaseValue works, the problem is still with the forceUpperCase on the attribute definition
This implementation is not quite what we need. The problem is the uppercasing is being done during the lifecycle, which happens after the controller executes. We need the data to be uppercased before the controller executes. We could do this in the binding (some place that checks for encryption, property editors.
So that the value is uppercase for script calls (like ajax queries), we probably want to add script for the onchange event that will uppercase the value