The module generator distinguishes between configurations and module. A configuration is the blueprint that becomes an module when it is activated.

A configuration can be created, edited and tested. It is generated from a self-created configuration or from a configuration supplied by Modell Aachen in the catalog. In this way, empirical values from customer projects are passed on to all customers.

After activation, the module remains linked to the configuration. If the settings of a configuration are changed, this is, after activation, transferred to the associated module.

List of modules

Key users can access the module management via the tool menu.

The table in the Active module tab shows how many module are being used from the booked quota. Without a booked quota, the module generator can be tried out and any configurations can be created and tested free of charge, but not used operationally.

The table lists active and archived modules and provides the following information:

• Title: Name of the module
• State: Distinguishes between Active and Archived. 
  • An active module can be used by the configured group of employees. 
  • An archived module is kept for documentary purposes. When archiving, the system asks which users may still see the archived module in the future.
• Actions: Module management.
  • Archive: Archives the module. A quota is released.
  • Set activate: Activates the module when the quota is sufficient.
  • Delete:  Only archived module can be deleted.
• Configuration state: Shows whether the configuration contains changes that have not been released for the module.

List of configurations

In the Configurations tab, all saved configurations are displayed with the following information:

• Configuration name: The name forwards directly to the configuration of the module.
• Last changed: Date of the last configuration change 
• Actions: Provides selection between testing and deleting. 
  • Testing creates a temporary module in a new browser window to quickly and easily get an impression of the configuration status.
  • Deleting allows only configurations that have no associated module to be deleted. 
• Used in module: Shows for which module the configuration is used.
• Area of module: Only relevant for multisite. Restricts visibility to an organizational unit.

Translated with www.DeepL.com/Translator (free version)