Key Mappings

The metadata must be adjusted to allow key mapping (S_Keytab). It is no longer necessary to create statements. Configuration is done via the GUI (Field attributes of a field).

The following field attributes must be adjusted:

Field attribute

Value

Lookup search

^{LookupEntityS_KeytabKeyMappings}

Lookup Preselection Fields

^{MasterKey.KeyMappings.EQUAL={ContactReason.Activity}}

^{MasterKeyRange.KeyMappings.EQUAL=S_ANLASS}

^{SlaveKeyRange.KeyMappings.EQUAL=S_ERGEB}

^{Active.KeyMappings.EQUAL=1}

Validation Preselection Fields

^{MasterKey.KeyMappings.EQUAL={ContactReason.Activity}}

^{MasterKeyRange.KeyMappings.EQUAL=S_ANLASS}

^{SlaveKeyRange.KeyMappings.EQUAL=S_ERGEB}

^{Active.KeyMappings.EQUAL=1}

The fields

MasterKeyRange.KeyMappings (Master Key Range)
MasterKey.KeyMappings (Master Key)
SlaveKeyRange.KeyMappings (Slave Key Range)
SlaveKey.KeyMappings (Slave Key)

are required fields. Empty keys are not allowed.

Figure: Configuration of lookup preselection fields

The pre-filters must be defined in the Administration menu via Key mappings. In the following example, if the key INQUIRY is entered in the event, you can only look up the key FOLLOW-UP for the result in the activity.