[KULRICE-10395] Allow for disabled expressions to be partially evaluated server side Created: 04/Sep/13  Updated: 21/Apr/14  Resolved: 06/Jan/14

Status: Closed
Project: Kuali Rice Development
Component/s: Development, User Experience (UX)
Affects Version/s: None
Fix Version/s: 2.4
Security Level: Public (Public: Anyone can view)

Type: Improvement Priority: Critical
Reporter: Jerry Neal (Inactive) Assignee: Brian Smith (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0 minutes
Time Spent: 1 day
Original Estimate: 1 day

Issue Links:
Fix
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:
KRAD
Application Requirement:
KC
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?:
Yes

 Description   

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:

disabled="@

{getParamInd('ENABLE_CHECK')}

and (field3 eq 'foo')"

would translate to the client side expression

"true and (field3 eq 'foo')"

or

"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.


Generated at Tue Jun 02 14:48:47 CDT 2020 using JIRA 6.1.5#6160-sha1:a61a0fc278117a0da0ec9b89167b8f29b6afdab2.