Checkbox list in 9.0 UI?

[Mark De Carvalho]

Trying to achieve something similar to highlighted screenshot attached. What control do I use in 9.0 UI? Is there an example I can use?

In Classic Presentation this was achieved with a Grid. Please advise, thank you.

0

Attachments:

You must be logged in to view attached files.

[Jasper Chow]

Perhaps similar to the weekday checkbox in recurring schedule item?

Check TaskRecurrenceDetail.layout for configuration. Adjust the composite cols accordingly in to show one item per row.

0

[Jasper Chow]

Add attachment

0

Attachments:

You must be logged in to view attached files.

[Mark De Carvalho]

Unfortunately those are hardcoded checkboxes, i need this list to be data-driven as per the example screenshot. Any ideas? What control replaced this grid functionality in the new UI?

0

[Atulan Zaman]

Hi Marco.
Your use case would have to be implemented a little differently since the classic (Grid) and AFL tables (Table) differ in that, classic table supports in-line editing, whereas AFL table does not. I can give you two alternate solutions that you can try and see which one suits best.

Option 1: Using a Table with an interactive column.
You can find an example of this in AttendeeEntityPersonList.layout. In this implementation, you can have a table with two columns, one for the caption and the second to show the state of your selection (replacing the checkbox). The second column is bound to an UI event that updates the form data. This might take up more space in the form, since it’s a table and not a collection of check boxes.

Option 2: Explicit checkboxes with scripted visibility
If the possible values for the checkboxes are known, you can create as many checkboxes in separate rows, and set their visibility based on the data object. You can find a similar pattern in NotificationList.layout, where we hide action buttons for notifications based on the kind of notification. Notice the “visible” property of <Item> elements under <Toolbars>. You might need to create some boolean attributes in the model for this, or you can use the inline scripting notation, if possible (eg.

Java

visible="`(and ,isRecipientSubscribed (not ,isMandatoryAction))"

1	visible="`(and ,isRecipientSubscribed (not ,isMandatoryAction))"

Hope it helps.

0

[Atulan Zaman]

Mark*. Sorry for the name typo.

0

[Atulan Zaman]

Note: If you choose to go with the second approach and using an inline script, make sure to add the attributes you are using (eg. isRecipientSubscribed above) to the “attributes” property of the relevant control. Otherwise the attributes would not be loaded by the UI automatically for the calculation.

0

[Patrick Tsang]

I would argue this use case is better served with a Multipicker, which would also resolve the space issues.  This use case seems more similar to a tagging system.

0

[Mark De Carvalho]

Thanks for the feedback and examples. I will go with option 1 as the multipicker UX is not very good compared to the “checkbox” pattern.

0

[Author]

Posts