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

Update default values to use a boolean variable rather than a list

    Details

    • Type: Bug Fix Bug Fix
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.4.1
    • Fix Version/s: 2.4.2, 2.5
    • Component/s: Development
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Environment:
      trunk
    • Similar issues:
      KULRICE-11285KRAD Library Fields Input Quickfinder return value loads Default tab rather than Quickfinder
      KULRICE-4261select a source encoding for maven build rather than using sys default
      KULRICE-4155kim documents set boolean to on/off, rather than tru/false and do not use the boolean var/char converter to make Y/N in DB
      KULRICE-5905Validation Action custom attribute for message rather than using description
      KULRICE-7531Action List does not use backdoored user's Action List preferences
      KULRICE-11279Default StringListConverter to generate mergeable lists
      KULRICE-12912FilterGenerator throws exception when attribute is boolean
      KULRICE-12540MultiValuePredicates do not handle large value sets appropriately
      KULRICE-6860Add support for specifying multiple default values for an attribute definition or field
      KULRICE-9883Boolean property value is evaluated as string instead of a boolean
    • Rice Module:
      KRAD
    • Application Requirement:
      Rice
    • Sprint:
      Core 2.5.0-m3 Sprint 2
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required
    • Code Review Status:
      Not Required
    • Include in Release Notes?:
      Yes

      Description

      Update the value used to determine whether default values should be applied to a field to a boolean type.

        Issue Links

          Activity

          Hide
          Jeff Ruch added a comment -

          Setting default values need to occur on the controller. This is because values set prior to the lifecycle running, could be over written. The variable that controls whether default values on fields should be added was viewsThatNeedDefaultValuesApplied. It was determined that we could simplify the process by making this variable a boolean since there will be at most one view. Any usage of viewsThatNeedDefaultValuesApplied should be updated to use applyDefaultValues.

          Show
          Jeff Ruch added a comment - Setting default values need to occur on the controller. This is because values set prior to the lifecycle running, could be over written. The variable that controls whether default values on fields should be added was viewsThatNeedDefaultValuesApplied. It was determined that we could simplify the process by making this variable a boolean since there will be at most one view. Any usage of viewsThatNeedDefaultValuesApplied should be updated to use applyDefaultValues.
          Hide
          Jeff Ruch added a comment -

          Updated impacting changes document for 2.5 M2 to 2.5 M3.
          Updated impacting changes document for 2.41 to 2.42

          Show
          Jeff Ruch added a comment - Updated impacting changes document for 2.5 M2 to 2.5 M3. Updated impacting changes document for 2.41 to 2.42

            People

            • Assignee:
              Jeff Ruch
              Reporter:
              Jeff Ruch
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 6 hours
                6h
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 4 hours Time Not Required
                4h

                  Agile

                    Structure Helper Panel