GENF5200 - Maintain Integration Mapping Values

This form enables the mapping of Callista values to External values that are acceptable to an interfacing system.

Callista fields are sometimes able to handle a wide variety of values, some of which may not be allowed in an interfacing system.

For example, Callista SMS can handle Title values which include upper/lower case and special characters, for example ‘A/Prof’. These titles may need to be transferred to Tribal Admissions, which does not allow lower case or characters such as forward slashes in the Titles code. This would create issues when transferring person titles to and from Tribal Admissions, so the problematic Callista values are recorded in this form and mapped to External values which are accepted by Tribal Admissions in this case. The mapping records of Mapping Type TITLE created in this form translate Callista values into values that can be accommodated in Tribal Admissions.

If the external system can accommodate a Callista value, then there doesn't need to be a record in this form (and the value will be transferred as is).

The table below provides an example of how information can be recorded in this form.

This form is accessed via the main menu.

The Integration Mapping Values block contains:

• Mapping Type
• Internal Value
• External Value

To create a new Mapping :

• Enter Insert mode
• Select the Mapping Type and record an Internal Value and External Value
• Save.

Rules/Notes:

Only Mapping Types available via the LOV may be used.

For a given Mapping Type, mapped values must be unique. i.e. An Internal Value cannot be mapped to more than one External Value and an External Value cannot be mapped to more than one Internal Value.

External Values must satisfy the limitations of that field in the external system.
e.g. If the Mapping Type is TITLE, then the External Value must be uppercase letters only and 1-12 characters long to be accepted by Tribal Admissions.

When the Mapping Type is TITLE, the Internal Value must match a Title in ENRF01N0.

The value of the fields cannot be changed after the record is saved. The user has to delete the record then insert a new one with the required values.

To delete a Mapping:

• Find the record to be deleted.
• Locate the cursor in the record to be deleted.
• Delete record.
• Save.