Vertical-independent Configuration

Info Areas

• Base info areas: Info areas that are identical in all verticals (e.g. Rep (ID), Station (AS) etc.). Use the --writedbstr parameter to generate the file mm_rel_base.txt, which contains a list of all base info areas, see mmba.exe Parameters.
• Base info areas with different codes: Info areas whose contents are identical, but whose info area codes differ. These info areas have an additional Base info area code which is used in XML reports and to define variables (in the Variable info area).

• Info areas containing Base fields: Info areas present in all verticals, but whose fields are only partially identical (e.g. Company). Fields common to all verticals have Base field numbers. Use the --writedbstr parameter to generate the file mm_dbfnr_base.txt: This file contains the common fields in these info areas together with the Base field numbers, see mmba.exe Parameters.

Fields

The following number ranges apply to Base fields (see above):

The file mm_dbfnr_base.txt contains all Base fields and the Base field numbers (see above). Base fields numbers are displayed as the third field number in the window containing all fields in an info area, see Displaying all Fields in a Mask.

Catalog

Base catalog numbers exist for variable catalogs using the following number ranges:

The file mm_catno.txt contains the Base catalog number for Base catalogs (in the last column), see mmba.exe Parameters.

There is no differentiation between Base and vertical-specific fixed catalogs. Vertical-specific fixed catalogs are located in the number range 10-29. Please note that the order of catalog entries (and consequently their codes) may differ between verticals (e.g. in the Activity info area).

Distributing the Base configuration

Base configurations can be transferred to the same vertical using Aurea CRM’s communication mechanisms. CRM.cockpit must be used to transfer the configuration to other verticals to ensure that IDs are converted correctly. For more information, refer to the CRM.cockpit documentation.

Base configurations defined in CRM.designer can be transferred using Aurea CRM bulkloader or CRM.cockpit. For more details, refer to the Aurea CRM web Technical & Installation Guide.

Mixed purpose:

To develop a base configuration for just 2 verticals, use the following mmdb.ini entries:

[CORE]

Vertical = xxxx

The following values are possible:

This results in the common elements of two verticals being displayed on the Base station: All fields, catalogs and info areas common to both specified verticals can then be used by the Base configuration.