For an object
tree with MBOs in a composite (cascading) relationship,
SubmitPending submits changes found in
the entire hierarchy. If each MBO in the hierarchy has its own CUD operations, the
submitted object tree replays in this order:
- Create and Update: a preorder traversal, i.e. parent -> left child ->
right child. That is, create the parent before the children.
- Delete: a postorder traversal, i.e. left child ->right child->parent.
Left and right in this context means from the first child in the children
list to the last child. For a tree with multiple operation types, for example root
(update) and two children (one create and one update) and each child has two
children, the order of the operation is: root (update), child one(create),
children of child one(create), children of child two (delete), child two (delete).