In a record, we are showing a report of type 'tasks per process model'

There is no functionality available currently like that..

Could you provide more details about the use case? You could handle such a requirement using design techniques such as setting up and triggering an exception flow on all the 'bundled' tasks on completion of one task in the bundle.

Thanks gauravg568, here is the use case.
I have created a portal report of type 'tasks per process model' and in a record I am showing all the tasks which are present in the report using queryProcessAnalytics. When I click on each task I am able to view the task in Tasks tab and submit it.So, my requirement is instead of submitting each task individually is there any possible way to bundle all the pending tasks and submit at once.

@sudarsand If I understand your question correctly, I assume that you are trying to perform a bulk submit. This could be achieved by implementing as follows:
1. Proceed with the setup you have got as of now which queries a portal report in first place and gives you a dataset that consist of task ids and corresponding process ids.
2. Create a process which accepts the task ids (with their corresponding process ids) and thereby submits them. To the best of my knowledge, there could be numerous ways of doing so and some of them are as follows:
a. Exception - Add an exception on the user input task which would be triggered upon the change in the value of a boolean variable. This boolean variable can be set (Smart services exists for setting and getting PVs, namely Set PV, Get PV at https://forum.appian.com/suite/tempo/records/type/components/item/i4BCLGOdlMUpdGVqT-RV7oRg74uEGJO7ST7vajpgHr5N88A8C7XkID6LIPzexYr/view/summary, Alternatively you can opt for IFM at https://forum.appian.com/suite/tempo/records/type/components/item/i8BCLGOdlMUpdGVqT-RV7oRg74uEGJO5CMZACzz_5W0L-UUHaRsMA-2Or_cSO-8rg/view/summary if you don't want to miss the Process History) in the process (Target the process by making use of the process id) which we are going to submit the task. As and when the process (which submits the task by accepting task id and corresponding process ids) sets the boolean variable in the target process, the user input task proceeds further because of the trigger of exception. The advantage of this approach is that, we can set the desired process variables in the exception path as we may need to capture some information out of every human intervention. This approach doesn't necessarily requires task id(because we are depending on a boolean variable), but it would be good to have the same information in hand. More or less, a similar functionality can be planned by using 'Messaging' as well.
b. Submit the task by using 'Task Puppetter' smart service at https://forum.appian.com/suite/tempo/records/type/components/item/i4BCLGOdlMUpdGVqT-RV7oRg74uEGJO7S_739EUwkk7M6h8UA_WBzwdrDriAdqK/view/summary. A task id is sufficient if we opt for this, but we might miss the exception path advantages here.
3. Enhance the SAIL interface, i.e. the tempo report which has got the report data from query analytics by adding an ability to trigger the process (created in Step - 2) with the selected tasks by using the Start Process Writer plugin at https://forum.appian.com/suite/tempo/records/type/components/item/i8BCLGOdlMUpdGVqT-RV7oRg74uEGJO5yQeCToV_iK9c-uZFaHQndbxbAQOV2CNBg/view/summary.
Not sure if I have conveyed properly, but please feel free to ask questions incase if you have any. Let's see if any other practitioners could come up with a better approach.