This session creates, updates, and deletes ActivityBundles in bulk. The data for create and update is provided by the consumer via the form object. OsidForms are requested for each create or update and may not be reused.

Create and update operations differ in their usage. To create a ActivityBundle, a ActivityBundleForm is requested using getActivityBundleFormsForCreate() specifying the desired course offering and record Types or none if no record Types are needed. Each of the returned ActivityBundleForms will indicate that it is to be used with a create operation and can be used to examine metdata or validate data prior to creation. Once a ActivityBundleForm is submiited to a create operation, it cannot be reused with another create operation unless the first operation was unsuccessful. Each ActivityBundleForm corresponds to an attempted transaction.

The ActivityBundleForms returned from getActivityBundleFormsForCreate() may be linked to the originating request through the peer Ids of the ActivityBundleForm. In the case where there may be duplicates, any ActivityBundleForm of the same peer Ids may be used for a create operation.

Once a batch of ActivityBundleForms are submitted for create, a CreateResponse is returned for each ActivityBundleForm, although the ordering is not defined. Only errors that pertain to the entire create operation are returned from createActivityBundles(), errors specific to an individual ActivityBundleForm are indicated in the corresponding CreateResponse. CreateResponses may be linked to the originating ActivityBundleForm through the ActivityBundleForm Id .

For updates, ActivityBundleForms are requested to the ActivityBundle Id that is to be updated using getActivityBundleFormsForUpdate() where the reference Id in the ActivityBundleForm may be used to link the request. Similarly, the ActivityBundleForm has metadata about the data that can be updated and it can perform validation before submitting the update. The ActivityBundleForm can only be used once for a successful update and cannot be reused.

Once a batch of ActivityBundleForms are submitted for update, an UpdateResponse is returned for each ActivityBundleForm, although the ordering is not defined. Only errors that pertain to the entire update operation are returned from updateActivityBundles(), errors specific to an individual ActivityBundleForm are indicated in the corresponding UpdateResponse. UpdateResponses may be linked to the originating ActivityBundleForm through the ActivityBundleForm Id.

The delete operations delete ActivityBundles in bulk. To unmap a ActivityBundle from the current CourseCatalog, the ActivityBundleCourseCatalogAssignmentSession should be used. These delete operations attempt to remove the ActivityBundle itself thus removing it from all known CourseCatalog catalogs. Bulk delete operations return the results in DeleteResponses.