...
- Users: All users are displayed in a single screen
- Handheld data: All items are displayed in a single screen
- DS Modules: All items are displayed in a single screen
- Queues: All items are displayed in a single screen
- Cleanup settings: Cleanup settings are performed in the server against a single set of records. As there is one cleanup job and all fields/modules are configured in the Base Configuration, any cleanup rules required should be entered in the Base Configuration cleanup screen. The drop down selection menu allowing users to select individual configuratons will be removed in a future release as it has no function.
- Administrator Settings: All settings in the "Administrator" menu are used for all configurations, the only exception is "Device Messages"
- Scheduled jobs: There are still single getupdates, cleanup and queuejob processes being run on the server, using a common admin id. You cannot have separate scheduler jobs for each configuration, all "configurations" are processed together. You can have different getupdates/download rules in a configuration but a single job will handle all configured rules. If mutiple rules are configured for a specific job, this does have a performance impact. Cleanup rules are configured at a "Base configuration" level, individual multi-config cleanup rules are ignored.
- Web Service Configuration / Custom Db Settings: In Map Settings->Module Settings, editing a module allows you to change the WS Config / Custom Db fields. These have no effect at a multi-config level, only the settings stored in the "Base Configuration" will be used.
- System keys: As all admin settings are common to all configurations, this includes system keys. Therefore, any keys that used to set distribution methods / server defaults, will be used for all "configurations".
...