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

Allow for disabled expressions to be partially evaluated server side


    • Type: Improvement Improvement
    • Status: Closed Closed
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.4
    • Security Level: Public (Public: Anyone can view)
    • Labels:
    • Similar issues:
      KULRICE-9846defaultValue not applied before disabled expression evaluation on initialization
      KULRICE-8126Collection control does not honor disable if disable is disabled by an expression for collection refresh
      KULRICE-11584Allow required to use expressions (like disabled)
      KULRICE-7835expressions not being evaluated on line actions within a collection
      KULRICE-6012Allow for ajax-ified server side validation
      KULRICE-11583Key Value should allow expressions in their key and value content
      KULRICE-8101Expressions not evaluated on tooltip content
      KULRICE-13382Create Server Side validation tests
      KULRICE-8627Document client side disable functionality
      KULRICE-7053spring expression error on refresh
    • Rice Module:
    • Application Requirement:
    • Sprint:
      2.4.0-m4 KRAD UXI Sprint 2
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required
    • Code Review Status:
      Not Required
    • Include in Release Notes?:


      In some cases, whether a disabled condition should apply depends on information only available server side.

      For example, suppose we have a system parameter which determines whether a disabled check should be applied. Currently there is no way to check this parameter in the disabled condition (since it is not available client side). The only way to do this is with property replacers. It would be much more convenient if part of the expression could be evaluated server side.

      One way to do this would be to have a convention that when the expression placeholder is present, to evaluate this part server side. The result goes into the client side expression.

      for example:



      and (field3 eq 'foo')"

      would translate to the client side expression

      "true and (field3 eq 'foo')"


      "false and (field3 eq 'foo')"

      We might want to be smarter though and if the server expression evaluates to false not set the disabled condition at all.


        Jessica Coltrin (Inactive) made changes -
        Field Original Value New Value
        Fix Version/s 2.4-backlog [ 16596 ]
        Jerry Neal (Inactive) made changes -
        Component/s User Experience (UX) [ 13465 ]
        Gayathri Athreya made changes -
        Priority Major [ 3 ] Critical [ 2 ]
        Brian Smith (Inactive) made changes -
        Assignee Brian Smith [ bsmith ]
        Brian Smith (Inactive) made changes -
        Status Open [ 1 ] In Progress [ 3 ]
        Brian Smith (Inactive) made changes -
        Sprint 2.4.0-m4 KRAD UXI Sprint 1 [ 159 ]
        Brian Smith (Inactive) made changes -
        Rank Ranked higher
        Brian Smith (Inactive) made changes -
        Original Estimate 1 day [ 28800 ]
        Remaining Estimate 1 day [ 28800 ]
        Brian Smith (Inactive) made changes -
        Remaining Estimate 1 day [ 28800 ] 0 minutes [ 0 ]
        Time Spent 1 day [ 28800 ]
        Worklog Id 91733 [ 91733 ]
        Brian Smith (Inactive) made changes -
        Status In Progress [ 3 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Brian Smith (Inactive) made changes -
        Fix Version/s 2.4.0-m3 [ 17037 ]
        Gayathri Athreya made changes -
        Link This issue is fixed by KCINFR-986 [ KCINFR-986 ]
        Jessica Coltrin (Inactive) made changes -
        Fix Version/s 2.4.0-m3 [ 17037 ]
        Jessica Coltrin (Inactive) made changes -
        Status Resolved [ 5 ] Closed [ 6 ]


          • Assignee:
            Brian Smith (Inactive)
            Jerry Neal (Inactive)
          • Votes:
            0 Vote for this issue
            1 Start watching this issue


            • Created:

              Time Tracking

              Original Estimate - 1 day
              Remaining Estimate - 0 minutes
              Time Spent - 1 day


                  Structure Helper Panel