Ensuring Consistency when Transporting Changelists

Since edited development objects are released again when a changelist is activated, it is possible that more changes have been made to and activated for the same development object between the time when it was activated and the transport of the changelist. These changes are recorded in other open changelists. As the change versions of development objects are chronologically dependent on each other it is necessary that the changelists are transported in chronological order. This means that the sequence of the development results is maintained (and the status in the target system remains constant).

To achieve this, the changelists get a sequential number (or, sequence number) when they are activated. Using this sequence number, the Change Organizer can be certain that the changelists are attached to transport requests in the right order.

If, for example, a development object is edited multiple times, then change versions of it exist in multiple changelists. If only the newest changelist is attached to a transport request, the Change Organizer can recognize if all older changelists have already been transported. If this is not the case, the Change Organizer automatically attaches the older changelists to the transport request.