You can set the popup for each row on the task. 

But if you want to disable the multirow select on the subject then for the windows gui you can use the model extender disable_multirow_select to do so. However for the universal gui this option does not exist yet. Feel free to create an idea for this if you feel multiple developers could benefit from this feature. 

Also check this topic:
 

​@Harm Horstman ​@Erwin Ekkel For the Universal GUI we have this on the radar too. Meta will implement a formal setting during this Sprint to Disable multi-select on a Subject, which will be released with 2025.1. Universal GUI implementation will soon follow.

So, it is clear to me that a simple solution is not available yet

​@Erwin Ekkel 
The disable_multirow_select option is a global setting, right? In that case not useful for us.

​@Arie V 
Ideally it should be a checkbox in the Table Tasks, I assume this is how it will work in 2025.1. And will this than also work in the Windows GUI?

ETA 2025.1?

​@Harm Horstman On your first question: that setting can be configured per Subject. It appears that you worked with it before: 

On your second question: it is currently planned to be a Subject setting which determines whether or not multiple rows can be selected, this can then also be used to prevent running Tasks on multiple records at once. Is the pop-up for each row not enough to steer the behavior for Table Tasks?

I think it should be a setting per subject per task. Some tasks you want to execute for multiple rows and for others this can be not diserable

​@Harm Horstman I get that having the ability to set this per Table task (or Report?) allows for more flexibility, but this is currently not in scope. 
 

Please raise an Idea to gather votes and feedback from the Community.

Imho - there is a distinctive difference between multi-selecting(aka creating a collection) and executing a task on said collection. There are more things to do on a collection besides executing a task or do you consider deleting the collection also as a task in this context ​@Harm Horstman , ​@Arie V ?

​@Ricky Agreed, disabling Multi-select on a Subject will also prevent multi-row Delete / Mass update / Export selection and as such has more generic impact.

Disabling multi-row execution for a particular Task provides more granular control, which is not a priority at the moment given the options that are already available. In fact, we might consider covering this in the design of Inline Tasks: 

I see a simple solution, make a setting in table tasks and disable a task when multiple rows are selected and the table task setting says, that multirow execution is not allowed.

Of course I know ways to work around this, but this costs a lot of time to implement. 

I believe this can be an important feature, because some tasks you really want users to consider execution for each individual row.

Idea for this follows.

​@Harm Horstman In such cases, would you use visible/editable Task parameters, Popup for each row or Ask confirmation settings?

Honestly, I can hardly imagine that you have a Task for which it is so important that it is being executed on a particular row, without any user-interaction after clicking the Task button. If the Task would simply execute upon clicking the Task button, then a user-error is made even more easily than a situation in which the user first selects multiple rows and then presses a Task button.

But please enlighten me and give a clear Use Case for which the current settings are failing your (10X faster) need in the Idea I asked you to raise!

I can see the benefit of the idea ​@Harm Horstman is looking for.

We do have situations where we have a “Calculate” button to gather possibly loads of data. We only allow this task to be executed for one records only as the result depends on it, A different record would overwrite the data again, so no use to execute it for multiple records. We now have the extender applied, but this now means that other request by customers to have some simple actions available that benefits from multi select cannot be achieved.

Process flows don’t always work as one might expect when selecting multiple records, like navigating to something afterwards. The task is run for all records, but the navigation only happens once. To not give the wrong idea to our user, we want to prevent this one task to not allow multi select.

I can even see a situation where we would want Junior employees to not be able to use multi select, but a Senior is fine. With in mind that multiple variants of a task will become available to link to the same table/view in the future, it would be possible to mark the one variant with a disallow were dis feature available.

There are some workarounds possible in some cases so we can Warn or Block user actions, but they technically are not user friendly as one can first press a button to get the answer that we actually did not want to allow it. It would be nice that such tasks would become unavailable with an indicator that multi select s not allowed with them.