App Engine Studio checklist component

[SBrooke27]

I'm banging my head over this. I have a list on a page in which a user can click on a record and edit the information. I originally tried the flyout, but there was quite a bit of information a user can edit and they had some requirements that prevented my using it. In line editing was another option I tried, but the users complained there was too much double clicking to edit. Now I'm using a modal.

Upon clicking a record, a modal opens up with 3 tabs. On one of the tabs, I have a checklist where they can link to values in a reference table. However, they are limited to no more than 2 options of 4-10 options listed.

I tried disabling the other checkboxes, but disabled doesn't seem to be supported in UI builder. I also tried readonly. I put in a HI ticket about this.

I tried popping up a message using a modal, but a modal on top of a modal formats strangely and the button won't work.

I tried adding a notification, but it's added to the page and not accessible when the modal is displayed.

I tried adding a message underneath and setting the display value based on a client state parameter, but the modal would have to be refreshed for it to display and disappear.

I'm also having issue that once the 3rd option is clicked, I'm not sure how to unselect it. I played around with api.emit, but either it doesn't work or I've formed it wrong. 

Can someone help with any of this, an idea I haven't thought of or something I'm doing wrong. It would really be nice to have a property on the checklist component like Max checks that would disable everything not checked after the max number of checks.

Tokyo - Pages built in Rome - cannot update layout.

@Marc Mouries @Jon G Lind - idea?

[Marc Mouries]

It appears that your use case presents unique requirements that don't seem to be entirely addressed by the default component. In this situation I find it's often easier to explore a creative option rather than trying to force the component into doing something it was not meant to do. I'd look into using a repeater that would generate a list of options based on records in the checklist table or your custom table. This would give you more control over the selection and the validation. 

[SBrooke27]

The day you responded to this, I was in the middle of implementing a repeater with the checkboxes. I did finally get it to work. A checklist seemed like it would be the perfect solution though, had it had the right properties. Querying the ServiceNow community, I did see a few people ask about limiting the number of items being chosen within a checklist. Maybe I will submit that as an idea.

[SBrooke27]

The day that I received the email that you responded to this, I was in the middle of implementing a repeater that contains a checkbox. It definitely was an interesting exercise. I did see where others asked about limiting the number of checkboxes that can be selected within Service Portal. Maybe I'll submit an idea to include this option in the checklist component. I think it will be a beneficial addition to functionality.