This session creates, updates, and deletes OrderItems 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 an OrderItem, an OrderItemForm is requested using getOrderItemFormsForCreate() specifying the desired order, product, and record Types or none if no record Types are needed. Each of the returned OrderItemForms will indicate that it is to be used with a create operation and can be used to examine metadata or validate data prior to creation. Once an OrderItemForm is submiited to a create operation, it cannot be reused with another create operation unless the first operation was unsuccessful. Each OrderItemForm corresponds to an attempted transaction.

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

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

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

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

The delete operations delete OrderItems in bulk. To unmap an OrderItem from the current Store, the OrderItemStoreAssignmentSession should be used. These delete operations attempt to remove the OrderItem itself thus removing it from all known Store catalogs. Bulk delete operations return the results in DeleteResponses.

Like all OsidSessions, OrderItemBatchAdminSessions are dedicated to single processing threads and a single authenticated user.