Merge based on sort order

The merge based on sort order merges events based on particular sort criteria. Any number of sorting criteria can be specified in the form of function attribute types. The following event for a function is merged with the predecessor event of the following function.

By default, alphanumeric and chronological sorting procedures are implemented in PPM. The method used is specified by the data type of the specified sorting criterion.
An example of a sorting criterion could be the AT_END_TIME function attribute with the TIME data type.

In a merge based on sort order, the imported process instance fragments may not contain rules. Process instance fragments with sequential functions are divided into minimal EPCs (event-function-event).

Warning

Make sure that the sorting criterion you defined is available at each function of the instances to be merged and includes the corresponding values.

In PPM 4.0 and above, you can use both merge methods in a client configuration.

Example

The AT_END_TIME function attribute is used for the merge based on sort order. The time stamp must be specified for each function of the instance.

<?xml version="1.0" encoding="ISO-8859-1"?>

<!DOCTYPE mergerconfig SYSTEM "mergerconfig.dtd">

<mergerconfig>

...

<mergehandling>

<eventmerge>

<mode>

<sortmerge>

<criterion name = "AT_END_TIME" />

</sortmerge>

</mode>

</eventmerge>

</mergehandling>

...

</mergerconfig>

If the sort attribute for several functions has the same value, AND rules are used to create parallel paths in the merged process instance.

Example

ppm_customizing_26

As the sort criterion used (AT_END_TIME) returns an identical value for the two functions FCT 1 and FCT 2, AND rules are used to create a parallel path in the merged process instance.