Login
    Contents x
    Map Fields
    • 06 Dec 2023
    • 4 Minutes to read
    • Print
    • PDF
    Contents

    Map Fields

    • Updated on 06 Dec 2023
    • 4 Minutes to read
    • Print
    • PDF
    Article summary

    The primary purpose of the Map Fields tab is to configure the mapping between corresponding source attribute and target attribute of two different forms. It will establish the relationship between fields of source form and the target form. The mapping process ensures accurate transfer of values and the integrity between the source and target attribute. 

    User Persona: Application Designer

    Configure Map Fields 

    This section provides the details of the second stepper configuration of Form Relation.

    To configure the Map Fields tab, perform the following steps:

    1. Click ID hyperlink to open any existing form relation or click New to create a new form relation from scratch.
    2. After configuring the first stepper General, the Map Fields stepper gets enabled for a new form. You can directly navigate to the Map Fields stepper for an existing form. A sample screenshot is shown below:

    Figure: Form Relation - Map Fields

    The following table contains a brief description on Map Fields screen fields.

    Field NameDescription
    Source

    		Displays the information such as Module Name, Form Name and the Tenant the source from belongs to. This information is based on the information configured in General tab.
    TargetDisplays the information such as Module Name, Form Name and the Tenant the target from belongs to. This information is based on the information configured in General tab.
    Click it to delete any specific row. 
    Click to map the values. The Map Values pop-up is displayed.

    Figure: Map Values

    • Source - Displays the list of all fields available in Source form.
    • Target - Displays the list of all fields available in Target form.
    • Auto Map - The fields with same names on source form and target form gets mapped automatically on page load. The system displays the message mentioning the number of fields auto mapped. A sample screenshot is shown below:
      Figure: Auto Map Fields Message 

    • - Click this symbol to add a new row. The system displays the following validation message if you attempt to add a new row without mentioning values in the previous row.
             Figure: Validation Message
    • Default - The last row will be the default selected in the Source and blank target value in the Target. Any unmapped Source value will be grouped as default and be mapped to the defined Target value.

      Note
      The Auto Map is available only for value fields.
      The Default Row cannot be deleted. 

      For Example: The Map Value will not be available for Symptom or Description fields. A sample screenshot is shown below:

      Figure: Map Value

      System displays the following validation message if you map a non-mandatory source field to a mandatory target field.
      Figure: Validation Message
    Click it to add the next row to map the fields.

    Auto Mapping vs Manual Mapping

    The following table describes few pointers to choose between Auto Mapping and Manual Mapping.

    UseWhen
    Auto Mapping

    • Both forms have a standardized format
    • Both forms have large volume of data
    Manual Mapping
    • Both forms have a non-standardized format and varying structure
    • Both forms have small set of database

    Let's understand the usage of Auto Mapping and Mapping with the following use-cases.

    Auto Mapping

    The system identifies the common fields present in source form and target form based on field labels. All common fields with similar labels are mapped automatically. The values entered from source fields get automatically populated in the corresponding target fields. The system also displays a success message informing the number of automatically mapped fields.

     Let's explore the following use case.



    Use Case
    User Persona: Application Designer
    Solution
    While creating a form relation between the Source Form (Log an Incident) and Target Form (Raise an SR), both the forms have common fields such as Workgroup and Classification. These fields should get automatically mapped and the values from the source form should get populated in the corresponding fields of the target form.

    		To achieve this functionality, the Application Designer Sam needs to click Auto Map on Map Fields tab. And, as Workgroup and Classification are value fields, it gets automatically mapped from Source Form (Log an Incident) to Target Form (Raise an SR).

     Manual Mapping

    If there are no common fields in source and target forms, then the  Application Designer can manually map fields, as per the requirement. This mapping is done based on a Mapping Matrix. Click here to know more about the Mapping Matrix.  

    Mapping Matrix

     Let's explore the following use case.



    Use Case
    User Persona: Application Designer
    Solution
    While creating a form relation between the Source Form (Log an Incident) and Target Form (Raise an SR), the Priority field in the source form and Severity field in the target form are different in their label names. However, the Application Designer needs to map these two fields with different label names. This is the Manual mapping of fields.
    these fields should get automatically mapped and the values from the source form should get populated in the corresponding fields of the target form.

    		To achieve this functionality, the Application Designer Sam needs to perform the manual mapping to map the fields with different label names Severity (Log an Incident - Source Form) and Priority (Raise an SR - Target Form). 
    • When multiple Tenants are selected, the values are mapped at Tenant level. 
    • The fields with parent-child relationship, child field inherits the mapping from parent field and the respective values gets displayed while mapping the child values.
    • For multiple Tenants, the fields with parent-child relationship, child field inherits the mapping from parent field and the respective values gets displayed while mapping the child values.



    Was this article helpful?
    What's Next
    Change password!
    Changing your password will log you out immediately. Use the new password to log back in.
    Change profile
    Success!
    First name must have atleast 2 characters. Numbers and special characters are not allowed.
    Last name must have atleast 1 characters. Numbers and special characters are not allowed.
    Enter a valid email
    Enter a valid password
    Your profile has been successfully updated.
    Logout