In Portal 2, there is currently no capability for custom buttons to directly listen to the same filters that a portlet uses. This limitation reduces flexibility and can lead to less intuitive user interactions, as demonstrated by the need for users to manually select an item in a scheduler portlet to trigger related custom button actions.