Thanks for posting to PX Community @sasharma !

In many applications, the dropdown/modal automatically closes when it loses focus.  So, I suspect this is what you are seeing when you are trying to map this dropdown selection in your application with the in-app Feature mapper utility.

In cases like these, it is recommended to manually map the Feature with a Rule based on the actual click Event that is sent to PX for evaluation.  Here are the details…

First of all, PX does not automatically collect the dropdown values/text, so that cannot be accessed directly through Feature Mapping Rules or in any PX Analytics.

However, as long as PX is tracking the user's click events on those dropdown elements, then those user selections (clicks) can most likely be mapped manually to separate Features in your Product Map, one for each possible selection.

The best place to see what is sent to PX when the user clicks/selects a dropdown option is by using Chrome → Inspect → Network tab filtering by the word “command”.  When you view the “Payload” tab you will see the click event content that can then be used manually in a Tag UI Element Rule in Feature mapping in your Product Map.  Sample below:

The tracked events should include the selectedIndex (ordinal position) and selectedValue (if the "name" attribute is included by your developers in the dropdown option code) attributes from the "option" selected that you can use in your Tag UI Element Rule CSS selector.

A sample Feature mapping using this kind of custom CSS Selector is shown below:

Happy PX-ing!!!