Uploaded image for project: 'Kuali Rice Development'
  1. Kuali Rice Development
  2. KULRICE-13096

CaseConstraint propertyName updated incorrectly

    Details

    • Type: Bug Fix
    • Status: Closed
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 2.4.1
    • Fix Version/s: 2.5
    • Component/s: Data Dictionary
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Rice Module:
      KRAD
    • KRAD Feature Area:
      Data Dictionary
    • Application Requirement:
      KS
    • Sprint:
      Core 2.5.0-m6 Sprint 2, Core 2.5.0-m7 Sprint 1
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required
    • Code Review Status:
      Not Required
    • Include in Release Notes?:
      Yes
    • Story Points:
      3

      Description

      Case CaseConstraints aren't working properly (when defined in the data dictionary and using the maintenance document framework). The propertyName is erroneously prepended with "document.newMaintainableObject.dataObject" (in BindingInfo#getPropertyAdjustedBindingPath) and it appears that the bad value is being written back to the data dictionary service. The result is the propertyName grows each time the page is loaded.

      Tried prepending the propertyName with "#form" and using the binding path relative to form but this didn't fix the issue.

        Attachments

          Issue Links

            Activity

            Hide
            sudduth Glenn Sudduth (Inactive) added a comment -

            Possibly the same problem

            Show
            sudduth Glenn Sudduth (Inactive) added a comment - Possibly the same problem
            Hide
            lsymms Larry Symms added a comment -

            Confirmed occuring in 2.5 branch of KS

            Show
            lsymms Larry Symms added a comment - Confirmed occuring in 2.5 branch of KS
            Hide
            jruch Jeff Ruch added a comment - - edited

            Because the propertyName of the case constraint gets over written by the getPropertyAdjustedBindingPath, there isn't a clean way to fix this. My solution is to check if the property path already starts with the binding path. If it does, I leave the property path alone.

            I will add an AFT for this case and also inquire with the architecture group on whether this solution is adequate.

            Show
            jruch Jeff Ruch added a comment - - edited Because the propertyName of the case constraint gets over written by the getPropertyAdjustedBindingPath, there isn't a clean way to fix this. My solution is to check if the property path already starts with the binding path. If it does, I leave the property path alone. I will add an AFT for this case and also inquire with the architecture group on whether this solution is adequate.
            Hide
            jruch Jeff Ruch added a comment -

            Added case constraint to to demo travel account. Selecting IAT in accountType code will cause the subsidized percent to be required. Tested on existing AFTs and they passed.

            Show
            jruch Jeff Ruch added a comment - Added case constraint to to demo travel account. Selecting IAT in accountType code will cause the subsidized percent to be required. Tested on existing AFTs and they passed.

              People

              • Assignee:
                jruch Jeff Ruch
                Reporter:
                lsymms Larry Symms
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: