System settings

System settings affect the user experience of all connected clients.
Please note that, for the changes to take effect, the client has to be restarted.

The following settings specify how constraints regarding the uniqueness of certain values are enforced:

The possible values for these settings are:

Note: If these settings are violated during editing, creation or import of system components, a warning is issued. In this case, changes violating the constraints cannot be persisted.
No check is made for existing values if a constraint is turned on (previously set to “Not set”) and duplicate values remain in the system.

System name and System label color:

eBiss 3 allows naming your system and assigning a colored marker on the top right, to provide a method to easy, visually distinguish the eBiss systems in your server landscape.
Please use “System name” to name your system. If you want to add a colored marker for the system name also pick a color via “System label color”.
The colored marked will only show up if a name is provided for the system.

Activate change log

Used to activate the change log on MessageBoxes, Channels, Partners, Locations, TypeSets, Variables, EventListener, Repositories, Mappings and Jobs, see Versioning (and ChangeLog) . The change log can only be activated with an existing versioning license, see Modules.

Activate audit log

When the audit log is activated, access to messages is logged, see Audit Log. The audit log can only be activated with an existing versioning license, see (Module.

1)
Refers to the communication address
2)
This can be, for example, the vendor number of a trading partner.