Salesforce Facts by Abhishek

Suppose we have a scenario where we have a picklist in a screen flow and once a value is selected, the picklist should get disabled. We can implement it using screen action. In this example, we have a picklist with two values A and B in a screen flow. Whenever a value is selected, it is sent to an autolaunched flow and it returns a boolean value in response which is used in the disabled attribute of the picklist input. The catch is we need to create a formula resource to store the value of the selected picklist, directly passing it would always be received as null in the subflow. Attached are the screenshots.

Suppose we have a use case where we have a toggle in the screen flow and we want to allow the user to activate it only once. Once activated it will be disabled. We can use the toggle's value in Disabled attribute in this case. Attached are the screenshots.

Suppose we need to make some of the picklist values as disabled in LWC. Now, the individual options of lightning-combobox doesn't support any disabled attribute. So, we can implement the same using slds and iteration logic. In this example, we have 3 options and option2 is disabled. Attached are the screenshots.