Map UR fields with target table fields
Define the fields that you want to map between the universal request and the target table fields that you already configured. This configuration enables you to copy the values of mapped fields from the universal request to the new ticket, and vice versa.
Before you begin
Role required: ur_admin
To map automatically the fields, select Map fields automatically related link. This action maps all fields that are common between UR and the service ticket and vice versa.
Note: Field mappings will take precedence over transfer template configuration, if you’ve already defined them.
Procedure
Navigate to All > Universal Request > Administration > Mapping Configuration.
Open the configuration for which you want to map the fields.
| Mapping type | Description and action |
|---|---|
| Direct transfer mappings | Map the fields to create service level tickets when a ticket is transferred from one department to another.On the Transfer Mappings tab,
|
| Associated ticket mappings | Map the fields to create an associated ticket for universal request.On the Associated ticket Mappings tab,
|
| Create UR mappings | Map the fields to create automatically a universal request when a request is raised from any of the available channels. Note: Before you perform this step, ensure that you’ve created a new Before insert business rule to call the respective API. For more information, see Create a business rule to automatically create universal request. On the Create UR Mappings tab,
|
**Note:** The **Type** field indicates the type field mapping selected, such as Transfer, Associated Ticket, or Create UR.
- Select Update.
Parent Topic:Configure mappings