Details
-
Type:
Improvement
-
Status:
Closed
-
Priority:
Major
-
Resolution: Complete
-
Affects Version/s: None
-
Component/s: Development
-
Security Level: Public (Public: Anyone can view)
-
Labels:None
-
Similar issues:
KULRICE-7211Default datePicker widget disabled property to disabled property on control KULRICE-13121 Setting the disabled property on a ConcreteKeyValue in a KeyValuesFinder class does not disable that option in a drop down control KULRICE-8126Collection control does not honor disable if disable is disabled by an expression for collection refresh KULRICE-12721Improvements to property binding security KULRICE-7976 Allow table header to be disabled KULRICE-7484Ajax Improvements- Add a preSubmitCall property to ActionField KULRICE-12556disabledWhenChangedPropertyNames does not work with multiple property names configured KULRICE-9846defaultValue not applied before disabled expression evaluation on initialization KULRICE-5331UIF Framework - Add support for disabled on input controls KULRICE-10395Allow for disabled expressions to be partially evaluated server side -
Rice Module:KRAD
-
KAI Review Status:Not Required
-
KTI Review Status:Not Required
Description
When a field becomes disabled, its validation should be set to valid. This would probably also effect prerequisite constraints, so a disabled field's dependencies would not be validated.
A second thing that would be very nice is if disabling/enabling could happen through javascript. This would make the UI much cleaner.