...
The distribution of the objects to process sub-objects is basically carried out via these object list definitions, but can be additionally limited by filters on the additional data. This results in completely different possibilities, which are less object data- but more process data-oriented. It is conceivable, for example, that the distribution is mapped completely with the help of additional data by defining and maintaining special data for the process flow in the additional data.
...
The order of the entries plays a central role in the automatic assignment of objects. If a new object is added at runtime, the system checks for the object in the sequence shown whether and to which definition the object can be assigned. Accordingly, it should also be ensured that the restrictions are "relaxed" with decreasing priority and not vice versa. For example: If two entries exist for an object type, one with and one without formula and the one without formula has the higher priority, then an object is always assigned to this definition and the other, restricted definition remains empty forever.
Object
...
Distribution
In order for the various objects in the process to be processed by corresponding tasks, they must be distributed. This distribution can basically be done completely manually. Especially with large object lists, however, it makes sense to automate the distribution as far as possible. This is possible by restricting the object list for each process sub-object already during process design. By default, the object list is inherited downwards within the hierarchy.
The automatic distribution is always based on the object list definitions of the process. For each process object the inherited definitions are displayed and can be selected explicitly. The selection of at least one entry deactivates the complete inheritance, so that only the explicitly selected definitions are inherited.
...
| Info |
|---|
In the best case, it is no longer necessary to manually adjust the distribution at runtime. However, manual processing can be very useful, especially when activities are multiplied and work packages are distributed to several locations. For this reason, when defining the distribution, special care must be taken to ensure that the object list is deactivated wherever it is not needed. |
Additional
...
Functions
The While the object list distribution is designed to setup which are process objects are using which real objects already at design time. Some process objects needs additional settings based on the object list. These objects are enhancing the object list by additional columns. E.g. a object creation task does not need access to the objects of the object list but needs to know where to place the newly created objects.
...
used to determine at design time which objects are processed by which process objects, there are some process objects that require additional settings in connection with the object list. For this purpose, the respective process objects extend the object list with additional columns. For example, tasks for creating objects do not require object distribution; instead, these tasks must be able to specify where the new objects are to be added.
...