Batch Submission by Batch Group

If multiple batch jobs are submitted for the same batch control, only one job runs at a time; the other jobs wait in the queue. There are some use cases where a batch is submitted from an online transaction to defer heavy processing to batch. If multiple users are performing the same action for different records, the jobs are queued up.

In this release, there is the concept of a Batch Group where multiple batch controls may get created for the same purpose and get associated, via an option, to a Batch Group. The existing F1SubmitJob "Submit Batch Job" script was enhanced to submit a job for the requested batch control or any of the batch controls associated with it using the Batch Group option. If the requested batch control is associated with a batch group, then the batch control with a low number of in progress batch jobs is submitted.  

Note that associating a batch control with a batch group should be done with caution. You should ensure that all batch controls in the group can run concurrently without interfering each other. 

As part of this enhancement, the Additional Information option of the Batch Control Query portal was also enhanced to support a search by batch control options. 

When applicable, pool-based batch submission supports a more efficient way of delegating user-centric tasks to be performed via batch processes that can run in parallel.

Steps to Enable

You need to update the logic that submits the batch job to call F1SubmitJob passing the batch group.