The multi-configuration server is composed of two main parts:
- Base configuration: This is the master configuration, which contains all modules / fields / settings used across all other configurations. If a module / field does not exist in the base configuration, it will be unavailable in all other configs.
- Sub configurations (multiple configurations): These allow you to customise a base configuration, to suit the individual needs of you users (for example, Salespeople seeing a different interface/data to Managers).
Therefore, your base configuration should contain everything that is to be used in each sub-configuration. You cannot map a module/field at a sub-configuration level, if it does not exist in your base config. For example, if viewing Base Configuration, selecting Map Modules will show all fields from the data source not currently mapped. If viewing a sub configuration, selecting Map Modules will show all fields from Base Configuration not already mapped in the current sub configuration.
This ensures that regardless of the individual configurations, all fields mapped from the data source are structured identically in all Swift MEAP™ configurations. Everything is added to a single source (Base Configuration) and once mapped, it is then enabled at a sub-configuration level.
Sub configuration features
...