Map Data Into Forms through Integration Data Mappings

Overview

Map data to automatically populate fields in Mirata forms from other systems integrated with Mirata, like SAP Service and Asset Manager.

Create an Integration Data Mapping

First, create an integration data mapping in the Admin Tool to set up your external data source field to a Mirata form field.

Define the Mapping

Enter a Name for the mapping, such as Work Order ID.

You can add a Description (optional).

Specify the Group, for example, SSAM Operation Context.

Choose the correct Integration, such as MDK for SAP Service and Asset Manager.

Select the appropriate Value Type such as String.

This must match both the form field type in Mirata and the field type in the integration application.

Define the data mapping Definition using an integration application field or a rule, such as an MDK rule for SAP Service and Asset Manager.

Click Save to save the mapping.

Use the Mapping in a Form

Next, use your data mapping in the form designer.

Add a Field and Link the Mapping

Add a field to your form.

This field will receive the integrated data.

Navigate to the field's Calculations.

Set the Initial Calculation to Integration Data.

Select the desired Integration Data Mapping, such as Work Order ID.

Save the form.

The value from the integrated application's field (e.g., Work Order ID in Asset Manager) will automatically populate the corresponding field in the Mirata form when it is created.

Sample Integration Data Mappings

Here are some common integration data mappings to use in your forms:

Work Order Number:

json

{
  "type": "string",
  "integration-data": "{OrderId}"
}

Operation Number:

json

{
  "integration-data": "{OperationNo}",
  "type": "string"
}

Operation Description:

json

{
  "integration-data": "{OperationShortText}",
  "type": "string"
}

Equipment Number:

json

{
  "integration-data": "{OperationEquipment}",
  "type": "string"
}

Equipment Description:

json

{
  "integration-data": "/MirataFormsIntegrationComponents/Rules/WorkOrders/Operations/GetOperationEquipmentDescription.js",
  "type": "string"
}

Work Order Priority:

json

{
  "integration-data": "{WOHeader/Priority}",
  "type": "string"
}

Work Order Planner Group:

json

{
  "integration-data": "{WOHeader/PlannerGroup}",
  "type": "string"
}