I have a case configuration that includes a specific activity type (lets call it activity type A) in the standard timeline. This is useful for users who want to create and manage a case directly within CiviCRM, as it ensures that important activities are set up in the case for them.
I have a Drupal webform for users who don't have Civi access to enable them to create a case and populate an instance of activity type A within the case.
The webform is set up such that case processing is turned on and a new case of the required type is created. Activity processing is turned on, and activity type A is set up within the webform such that an existing activity of scheduled status gets updated, and that activity is filed on the case that is created by the webform.
My assumption with this configuration is that as the form submission gets processed, the case (complete with its default scheduled instance of activity type A) is created, and the submission data is used to populate that activity record.
However, what appears to be happening is that the case is being created, and a new activity (type A) is also being created and populated, and filed on the case, such that the resulting case has two instances of activity type A (one populated with my data, and a second, empty one - presumably the default instance created when the case was created.
So, given that I don't want to remove the instance of activity type A defined in the standard timeline of the case configuration, how can I alter the settings within the webform such that the webform identifies and populates this activity rather than making a new one?