The following guide refers to a custom mapping process between "custom fields" (@IDMS_CST_FIELD
, @IDMS_CST_PROPMETA
) and properties from an Inquiry request object.
Here, we are exploiting the mapping functionality by using just one table (@IDMS_MAP_OBJECT
) where the fields:
IDMS_MappingSystemRelationshipCode
IDMS_MappingObjectTypeCode
have the following respective values:
- InquiryAPI
- InquiryBufferCSTField
Step-by-step guide
Navigate to ~/SetupEntities/CustomFieldsMappingGridList?RelationCode=InquiryAPI
- Columns "From code" and "To code" display the respective codes that will be mapped
Create a mapping
By clicking on the top right, the user can create mapping.
The same popup as above opens where the user enters the mapped fields
- "From" field refers to the request's property name
- "To" field refers to which custom field the value of the "From" property will be saved
When a custom field is used, it disappears from the "To" dropdown list, until it is not used again in a mapping, to avoid duplicate usage
Edit a mapping
Using the action column on the right, the user can edit the mapping.
If the user clicks edit a popup opens.
- "From" field refers to the request's property name
- "To" field refers to which custom field the value of the "From" property will be saved
Delete a mapping
Using the action column on the right, the user can delete the mapping.
By clicking on delete, a confirmation popup opens.
Example
Following a small example with how the custom fields mapping works for an Inquiry request.
First of all, we have the setup of the mappings.
Then, we have a request object. Below, we can see only the part of the custom fields that are provided, according to the mapping. Not all fields are needed.
The data from the request object are shown in the UI, via the ~/InquiryBuffer/InquiryBufferEdit?inquiryCode=XXX
.
For each mapping, if the request object provides any values for that mapping, they are presented at a separate section named "Extra Details".
Add Comment