Kuali Rice Development
  1. Kuali Rice Development
  2. KULRICE-8804

Uppercase implementation does not uppercase values

    Details

    • Type: Bug Fix Bug Fix
    • Status: Reopened Reopened
    • Priority: Major 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-5798Add forceLowercase to AttributeDefinition and AttributeField
      KULRICE-5282Uif Framework - Binding needs to look at forceUppercase
      KULRICE-4025Direct inquiry does not work properly in some conditions
      KULRICE-10957Labs Lookup Default and Labs Lookup Results Limit failures due to capitalization (uppercase)
      KULRICE-6958Cleanup 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

          Activity

          Hide
          Jerry Neal (Inactive) added a comment -

          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

          Show
          Jerry Neal (Inactive) added a comment - 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
          Hide
          Steve Manning (Inactive) added a comment -

          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

          Show
          Steve Manning (Inactive) added a comment - 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
          Hide
          Jerry Neal (Inactive) added a comment -

          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.

          Show
          Jerry Neal (Inactive) added a comment - 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.
          Hide
          Claus Niesen added a comment -

          I've noticed that uppercaseValue isn't set when forceUppercase in the data dictionaryis set.

          Show
          Claus Niesen added a comment - I've noticed that uppercaseValue isn't set when forceUppercase in the data dictionaryis set.
          Hide
          Steve Manning (Inactive) added a comment -

          uppercaseValue works, the problem is still with the forceUpperCase on the attribute definition

          Show
          Steve Manning (Inactive) added a comment - uppercaseValue works, the problem is still with the forceUpperCase on the attribute definition
          Hide
          Jerry Neal (Inactive) added a comment -

          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.

          Show
          Jerry Neal (Inactive) added a comment - 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.

            People

            • Assignee:
              Unassigned
              Reporter:
              Jerry Neal (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:

                Structure Helper Panel