Pierre 2/23/2021 9:41:26 AM
Not sure what you mean.
- The presence of the button can be governed by the values of the underlying record (via the button filter)
- To have different actions with the same button, it is a bit painful today. I deal with it by assigning calculated values to a field (Ex [Next Trigger]) (ex "T01", "T02", "T03"). I have then Triggers activated by Record Changes on the [Next Trigger] field.