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

Collections - table layout sequence column is editable

    Details

    • Type: Bug Fix Bug Fix
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.2.0-m2
    • Fix Version/s: 2.2.0-m2, 2.2
    • Component/s: Development
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Similar issues:
      KULRICE-7324Add ability to specify table layout collections action column sequence
      KULRICE-4723Better collection layout support
      KULRICE-12029Issue with delete functionality on Table Layout library demo
      KULRICE-11242Fill AFT Per-Screen Item Gap: KRAD Library: Sequence Column
      KULRICE-12026KRAD Library sequence column value in collection changes on delete
      KULRICE-7003Provide a simpler table layout that does not build up field objects for each column
      KULRICE-13207AFT Failure Tables and Collections Selected collection path was not set for collection action
      KULRICE-12034Delete creating blank rows in Component Library / Collections / Sequence Column
      KULRICE-12027Table indices in Chrome are not sorted correctly
      KULRICE-7888Css box layout classes are appearing more than once in items of a collection
    • Rice Module:
      KRAD
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required

      Description

      Table layout collections renders the sequence column as editable. This also causes the values of the sequence column to be updated twice - so the value gets concatenated with comma separation - see screenshot. This bug appeared after the 2.2 M1 release.

        Activity

        Hide
        Samuel Holtzkampf (Inactive) added a comment -

        There was also issue with auto sequence not generating due to checking for Message instead of MessageField. Fix has been committed.

        Show
        Samuel Holtzkampf (Inactive) added a comment - There was also issue with auto sequence not generating due to checking for Message instead of MessageField. Fix has been committed.
        Hide
        Samuel Holtzkampf (Inactive) added a comment -

        Debugged and saw that the sequence fields' readOnly property is true until somewhere during the ViewHelperService.performApplyModel

        Show
        Samuel Holtzkampf (Inactive) added a comment - Debugged and saw that the sequence fields' readOnly property is true until somewhere during the ViewHelperService.performApplyModel
        Hide
        Eric Njogu (Inactive) added a comment -

        A workaround has been committed that does the following:

        • represents the readOnly property of the sequence field using an EL expression,
        • modifies ExpresssionUtils so that existing property expressions are not replaced by values from the expression graph.

        Kindly let me have your suggestions on how this can be improved.

        Show
        Eric Njogu (Inactive) added a comment - A workaround has been committed that does the following: represents the readOnly property of the sequence field using an EL expression, modifies ExpresssionUtils so that existing property expressions are not replaced by values from the expression graph. Kindly let me have your suggestions on how this can be improved.
        Hide
        Jerry Neal (Inactive) added a comment -

        Eric,

        No we do not want to do that. Setting the value as true should override any expressions. So there is a breakdown somewhere in the expression handling. We need to find the root cause of the problem and not a hack fix.

        thanks,
        Jerry

        Show
        Jerry Neal (Inactive) added a comment - Eric, No we do not want to do that. Setting the value as true should override any expressions. So there is a breakdown somewhere in the expression handling. We need to find the root cause of the problem and not a hack fix. thanks, Jerry
        Hide
        Eric Njogu (Inactive) added a comment -

        property expressions from parent beans are not set if the property was defined in the child

        Show
        Eric Njogu (Inactive) added a comment - property expressions from parent beans are not set if the property was defined in the child
        Hide
        Jerry Neal (Inactive) added a comment -

        Previous solution not acceptable

        Show
        Jerry Neal (Inactive) added a comment - Previous solution not acceptable
        Hide
        Jerry Neal (Inactive) added a comment -

        The issue is resolved by corrections to expression handling

        Show
        Jerry Neal (Inactive) added a comment - The issue is resolved by corrections to expression handling

          People

          • Assignee:
            Matthew Wuertz (Inactive)
            Reporter:
            Samuel Holtzkampf (Inactive)
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Structure Helper Panel