'Delete task' Action on UX page

Isha

We have a 'Delete Task' action button on an UX page.
The Action button is driven by a 'Run Action' line item which is TRUE if the Confirm Delete Boolean is checked.
This setup works, but only if the user selects the full record (row) where Confirm Delete is TRUE.

Currently, If a user checks Confirm Delete Boolean on the UX page, but does not select the row, the Delete Task action button remains disabled.

• The Delete Task action button only activates after the user clicks on the whole record which needs deletion, which makes the process cumbersome.

How can I configure the Delete action button so it becomes active as soon as any Confirm Delete Boolean is ticked, without requiring the user to select the whole row?

TheresaR

@Isha it sounds like your "delete task" action is context dependent, meaning it requires you to select the row in order to determine the context needed for the action to run. If that is not your intended behavior you need to re-think how the action and input should interact.

If you want them to delete items one-by-one then you could pivot the list that is in rows to the context/page section so that a user would select an item from the drop-down, then tick the "Confirm Delete" and run the action.

If you wanted them to be able to delete multiple items, you could leave the grid card as is, allowing them to select multiple "Confirm Delete" booleans, and then rebuild your delete action so it is not context dependent.