Understand requirements and limitations when modeling composite operations.
Composite operations support client parameters, personalization keys, default
values, and composite MBO attributes bound to a single composite operation
invocation.
In general it is possible to combine any number of child updates, creates, and
deletes in a single operation replay message. A complete composite graph of
arbitrary depth and breadth can be constructed (potentially spanning save
operations) and be submitted as a single replay operation. The client API
constructs the replay message such that it contains all the modified nodes in
the graph and their ancestor nodes.
SAP Mobile Server checks the graph version in the cache and compares it to the
graph version in the operation replay message to be sure they agree prior to
invoking the EIS. If the versions do not match, a conflict is detected and an
error is generated in the SAP Mobile Server log file.
Propagation of load arguments into MBO attributes is only supported on the root
node of an MBO graph.
Composite operations are only allowed on the root of a composite
graph.
Operations defined on a child MBO in a composite graph only allow
mapping the attributes of the child MBO when defining the input
mappings.
JDBC does not support composite operations.
Entity Read operations cannot be composite.
Operations cannot have the names create,
update, or delete for a child MBO in a composite graph, if the child MBO is used
in a composite operation.