Your setup is pretty complex, likely more than needed, with multiple nested Masters and nested groups therein with conflicting Click or Tap events. You have multiple instances of a group with one interaction but objects within that group having different interactions.
Something to keep in mind is that “deeper” or “child” objects override interactions of “parent” objects. In your case, you have a Master (Mdl Filter Start) with:
- Dynamic Panel (DP Modal)
- Group (TopSection)
- Master (Btn w icon Deselect all) with raised event of “DESELECTALL” --to “Fire Event …”
- Group (Action group) with
Click or Tap: Raise Event Btn w icon Deselect all raise DeselectAll (Which is what you appear to want happen.)
- Master (Icn Close blue for button h50)
- Unnamed group
- Unnamed Hot Spot with
Click or Tap Raise Event... This overrides your interaction for "Action group" --and the event named, “DoClose” is never handled, so nothing happens when you click on the ‘X’ icon.
- Unnamed widget with text value of “Deselect all” with
Click or Tap Open LInk: (Nothing selected) This also overrides your interaction for "Action group" --and there is no target specified for the Open Link action, so nothing happens. Additionally, you most likely do not want two different results if a user clicks on the text, “Deselect all” versus the ‘X’ icon (which would be confusing and unexpected usability.)
So, you can either remove the deeper “child” interactions on individual widgets, or replace these interactions with identical actions (not recommended as much harder to inspect and maintain), or add some more Raise Event actions (also not the best idea for same reasons.) If for some reason you (think you) need to retain the existing actions for these deeper widgets, you’ll need to add some case statements to provide logic for determining which action should apply–their “deep” action or that of their parent (thus rasing an event.)