Abstract: Techniques are described to enable a user to define data-transition rules that control how a handover component of a computer application transforms business objects of one type to business objects of another type. The handover component is logically situated between a preceding business process that uses a preceding type of business object and a second business process that uses a second type of business object. Based on the user-defined data-transition rules, the handover component performs a split/merge process that determines the succeeding business objects to be generated based on the preceding business objects received from the preceding business process and then generates the succeeding business objects based on the received preceding business objects and the user-defined data-transition rules.

Abstract: Among other disclosure, a data flow is an entity that completely or substantially encapsulates all or substantially all aspects of a flow of data from a preceding object instance part into a succeeding object instance part. A set of several single flows of data can provide the complete flow of data of an entire process step.

Abstract: Techniques are described to enable a user to define data-transition rules that control how a handover component of a computer application transforms business objects of one type to business objects of another type. The handover component is logically situated between a preceding business process that uses a preceding type of business object and a second business process that uses a second type of business object. Based on the user-defined data-transition rules, the handover component performs a split/merge process that determines the succeeding business objects to be generated based on the preceding business objects received from the preceding business process and then generates the succeeding business objects based on the received preceding business objects and the user-defined data-transition rules.