Certainly. Here is a simple self-contained example where there is a field called "showme" whose value is either "true" or "false". And the Button is embedded only inside hte Table rows that have showme="true".
<module name="Search" layoutPanel="panel_row4_col2" autoRun="True" group="Buttons only show for some rows">
<param name="search"><![CDATA[
index=_internal source=*metrics.log group="per_sourcetype_thruput" | head 1000 | stats sum(kb) as totalKB by series | eval actions="PLACEHOLDER" | streamstats count | eval showme=if(count=="2","true","false")
]]></param>
<module name="Pager">
<module name="Table">
<module name="ValueSetter" group="row.fields.actions">
<param name="name">foo</param>
<param name="if.$row.fields.showme$=true">1</param>
<module name="Gate">
<param name="requiredKeys">foo</param>
<module name="Button">
<param name="allowAutoSubmit">False</param>
<param name="customBehavior">confirmationPopup</param>
<module name="Redirector">
<param name="popup">True</param>
<param name="url">http://google.com</param>
</module>
</module>
</module>
</module>
</module>
</module>
</module>
You can of course use the Table module's "hiddenFields" to hide the actual rendered "showme" or "tobedeleted" column from the end user and it will still work.
As to how/why this implementation works -- the ValueSetter module uses it's conditional logic to create a $foo$ token that will only be defined on certain rows. Then the Gate module will either block or allow the downstream push based on that token. Then last but not least the Button module happens to have a behavior where it wont render itself until the first push is received.
If the Button didn't have that default behaviour then we'd have to cook up another way, possibly using the Sideview ShowHide module.
