Idea Summary
Introduce a native, declarative "Button" column type for Interactive Grid and Interactive Report regions. This feature would allow developers to easily create row-level action buttons that natively trigger Dynamic Actions, pass row primary key values or column data as parameters/Items to Submit, and execute server-side logic without requiring custom HTML templates or JavaScript event listeners.

Use Case
1. Row-Level Actions: Executing row-specific PL/SQL processes directly from a report or grid row (e.g., "Approve Record", "Cancel Order", "Send Email Notification", "Process Payment").
2. Modal / Sub-region Triggers: Opening a modal dialog or refreshing a dependent region based on the clicked row's ID.
3. Reducing Boilerplate Code: Eliminating the need to write custom HTML `<button>` tags with `data-*` attributes, manual jQuery selectors (`.btn-class`), and hidden page items just to capture row-level IDs in low-code applications.

Preferred Solution (Optional)
1. Add a new column type option named "Button" in Page Designer for Interactive Grid and Interactive Report columns.
2. Include declarative properties for Button Label, Icon, and Universal Theme Button Style classes (e.g., `t-Button--primary`, `t-Button--small`).
3. Allow Dynamic Actions to directly target the Button column (e.g., Event: "Click", Selection Type: "Column / Button").
4. Provide declarative access to the triggering row's data in the Dynamic Action context (e.g., automatically populating specified page items or exposing `#COLUMN_VALUE#` directly in the action scope).