[KULRICE-7563] Easy display of List<String> NEW control(s) Created: 27/Jun/12  Updated: 19/Jan/15

Status: Open
Project: Kuali Rice Development
Component/s: User Experience (UX), User Interface
Affects Version/s: 2.2.0-m1
Fix Version/s: Backlog
Security Level: Public (Public: Anyone can view)

Type: New Feature Priority: Major
Reporter: Brian Smith (Inactive) Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: DeopdownControl, Old, Uif-InputField
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
fixes KULRICE-6286 Create HTML lists from simple String ... Closed
is related to KULRICE-10367 Component for add/delete as tags Open
Similar issues:
KULRICE-7561Allow an easy way to enable/disable controls and buttons clientside
KULRICE-5528RuleRepositoryServiceImpl.getRules(List<String> ruleIds) doesn't support multiple elements in the ruleIds parameter
KULRICE-9735Property editor class is initiated Previously with the list<String or any type> but after 2.2.0 upgrade its not happening.
KULRICE-5661make it easy to add BSFRuleExpression variables
KULRICE-3452Extra white area appears in Firefox when tabs display error messages
KULRICE-2478Ensure that Rice configuration of JPA is easy to understand and use
KULRICE-10820Improve visual treatment of create new link on Lookups
KULRICE-12286New KIM API to bulk fetch display name information
KULRICE-9360DocBook styling for KNS to KRAD Conversion Guide
KULRICE-5934Proposition Summary displays "null", when a new proposition is created using the KRMS Rule Editor
Epic Link: Components
Rice Module:
Application Requirement:
KAI Review Status: Not Required
KTI Review Status: Not Required


Right now there is no way to easily display a List/Array of strings to the user (without using a wrapping object and collection components).

Add a new control that allows display lists of strings in 1 of 3 options (we may want to split this into multiple controls instead of options of 1 control):
Comma seperated
Line break between items
As unordered or ordered list

This control would be the automatic choice for fields whose property path point to a list of string for readOnly content.

Possibly include a default for this type when NOT readOnly (as a seperate control - some kind of freeform string list entry, this needs research).

In many cases, List<String> has a set of input for the non-readOnly case (examples being checkbox and multiselect - these both must be backed by List<String>).

To reiterate: jira is for easy List<String> readOnly display control (and IN ADDITION, another control that allows freeform string list content). readOnly control is higher priority, but both should be supported.

Comment by Jerry Neal (Inactive) [ 04/Sep/12 ]

Adding message from Venkat:

Looks like it's a KRAD issue in M3.

When we use DropdownControl (multiple select) and if it's readonly, looks like we're having issue with spring evaluating the value. If we use, readOnlyDisplayReplacementPropertyName for that propety, would fix this issue

<bean parent="Uif-InputField" p:propertyName="features" p:label="Features">
<property name="control">
<bean parent="Uif-DropdownControl" p:multiple="true" p:size="5" p:options-ref="features-options"/>

Here, property 'features' defined as List in the form.


Comment by Brian Smith (Inactive) [ 05/Nov/12 ]

readOnly lists are resolved using a different approach, see readOnlyListDisplayType and readOnlyListDelimiter options on DataField in 2.2 rc1. Note this includes automatic readOnly conversion for MultiValueControl types as well and any DataFields that use List<?> where ? is a simple type.

Comment by Brian Smith (Inactive) [ 15/Apr/13 ]


Ones we are considering

Generated at Thu Jun 04 05:56:50 CDT 2020 using JIRA 6.1.5#6160-sha1:a61a0fc278117a0da0ec9b89167b8f29b6afdab2.