Package Editor

Package Editor

The package editor lets you define which objects will be exported. Splitting up objects in different packages helps to load/unload them independently during runtime, but is no necessity.

Every package needs a name 1 and can also have an optional description text.
The selection of objects 2 works very similar to the selection of types and templates in the data layout editor. Container objects can have the following states:

The icon on the left side (checkmark or X) indicates whether the container object itself is part of the export. The icon on the right side (arrow down or dash) indicates whether its child objects are included automatically or not. If they are included, every child object that will be created in the future is automatically part of the export.

Included objects of a type or with a template that is filtered out by the data layout are marked with a conflict icon 3. At the bottom of the package editor a counter displays how many objects won't be exported due to the defined data layout 4.

Additional type/template restrictions

In some cases it can be useful to filter out object types or templates only for specific packages. To define additional filter rules for only one package, click on the button "Type/template restrictions" in the upper right of the package editor 5.

This opens a reduced data layout editor, where all object types and templates that are already filtered out by the ruleset's overall data layout are greyed out. It's not possible to include these types or templates for a specific package.