Has anyone used a dropdown for blocker reasons?

[Leah Pearlstein]

Has anyone ever switched from using the built in blocker free text field to a predetermined set of blockers in a list dropdown?

 

We are unable to automate our blocker reporting 100% as we have teams that do not adhere to the standard blocker causes. We have the reasons posted in multiple locations and also send regular reminders, but are not getting consistent date.

 

We are investigating the affect of using a dropdown field for blocked items instead of the built in free text field, and instead will likely be using the free text field as a secondary reason. Has anyone done this before?

 

If we do make this change, are there apps/functionality that this would affect other than the core and our subscription blocker apps? 

[David LeDeaux]

Hi Leah,

 

I don't see a problem with doing this from an architectural standpoint. 

 

Obviously anything that's looking to the blocker reason from a reporting perspective won't show that data since it's being stored in a different field.  The only other thing would be a workflow issue where a user now has to look for that field on the right hand column instead of it popping up right next to the blocked button.