Can you lock a list collector or make it read only after one of the options is selected

Cupcake · ‎06-01-2017

I wanted to know if it is possible to make a list collector RO or lock it after a specific value is selected.

So if someone selects the N/A value, I don't want them to be able to select anything else, but if they change their minds and they un-select that value then the list collector should no longer be locked or RO.

Is this even possible?

Thanks,

Karen

Chuck Tomasi · ‎06-01-2017

It would seem like a separate variable is needed here to indicate an N/A value. If they check the box, then a UI policy makes the list collector appear and they can start populating values. That way you have a way to keep the list collector unavailable in the N/A case, but still allow them to choose values when it is applicable. Make sense? two fields - one checkbox, and one list collector, and a catalog UI policy based on the checkbox value to make the list collector appear when needed.

View solution in original post

Community Alums · ‎06-01-2017

I would echo ctomasi here. The whole point of a list collector is that it's a reference field that lets you pick more than one thing. I'd probably use a reference field there.

Now as to how:, just use a UI policy that makes the field read only when it's not blank. That said, as soon as they make a choice, It will be locked, so if they mess up, they have to start over...

Cupcake · ‎06-01-2017

Thank you Andrew, I've already done the UI Policy too. So I know I am ahead of the game; however, a few points that I mentioned to Ctomasi:

They want a list collector because the customer needs to be able to select more than one option
They only want the rest of the list lock "If and ONLY If" the N/A option is selected.
If there is no way to accomplish this that is okay by me, I just wanted to ensure that there was no other means of getting around it.
In my UI Policy I said if

Community Alums · ‎06-05-2017

Karen,

It's not so much that it's not possible, as much as that it seems like a bad idea based on the way you described your needs previously.

In this case, the thing I would be worried about would be, what if they accidentally select "N/A" ? They can't fix it, and will have to submit a new request.

By the way, since List Collectors are comma separated lists, i think you'll have to do a "contains" condition, rather than "is".

In order to get the functionality you want, I'd suggest the following:

Hide the list collector by default
Add a "Yes/No" variable that asks "is there any change in XYZ?"
If the answer is no, leave the list collector hidden.
if they choose yes, make the list collector show up so they can make a choice.

By essentially moving the NA field off the list collector, you can still get the information you're after, without making the UI so rigid it's hard for the user to make use of it. In my experience, it's always best to allow for the user to make mistakes.

Kusuma2 · ‎06-01-2017

Hi Karen Brown ,

IN your case its better to go with the Field or (variable) type : Reference.

But if you want to restrict user to select only one option from the list collector ,you can achieve it through the ui polcy.

Below is the screen shot it might be helpful for you to understand better.

Here my variable name : Ref

Kindly let me know if this was helpful.

Please provide your feedback appropriately (Like, Helpful, Endorse AND/OR Correct) to help community.

Thank you!

Regards,

Ajay.