Hi David,
Thanks for your update.
In Scheduler, the batch operation has been used, so that it triggers when concurrent action takes place. For example, when we edit a single occurrence of an appointment in recurrence series, a new appointment gets inserted and at the same time the parent recurrence appointment also needs to be updated (recurrence rule alone needs to be updated). Therefore, now the batch operation triggers with the newly added value and the changed value sending it to the controller side parameter which can be referred from the following screenshot –
Here just edit a single occurrence of a recurrence appointment is edited by clicking on the Edit Appointment option -
In the below image, you can see the newly added appointment object as well as the edited appointment together in the parameter –
In another scenario, when we create same appointment for more than one resources simultaneously, the batch operation triggers with more than one value in insert operation and you can refer it from the below screenshot for this scenario.
Here, creates an appointment for 2 resources,
Now, the 2 appointment objects get added to the parameter list as shown below,
In such cases, the batch operation takes place in Scheduler.
Kindly check with these cases and revert us, if you need any further assistance on this.
Regards,
Sellakumar K
