Register the "model" property | Aranda Integration Center

The property “model” relates the States and Additional ASMS Fields, the configuration file has the following JSON for model:

{
  "model": [
    {
      "id": 0,
      "reference": "",
      "state": [
        {
          "value": "",
          "id": 0,
          "commentary": {
            "Key": "",
            "value": ""
          }
        }
      ],
      "additionalFields": [
        {
          "id": 0,
          "field": {
            "key": ""
          },
          "mapping": [
            {
              "id": 0,
              "value": ""
            }
          ]
        }
      ]
    }
  ]
}

1. With the help of a Aranda Service Management (ASMS) Get the IDs of the values for the property Model.

2. Choose the model you will use for the integration, with the help of an Aranda Service Management (ASMS) administrator obtain the model ID associated with the project, service and category, previously assigned.

3. Type the values in the “model.id” from the configuration file:

{
  "model": [
    {
      "state": [
      ],
      "id": 15,
      "additionalFields": [
      ]
    }
  ]
}

Note: No need to register the property “reference” of “model” because only one category was registered.

Case Statuses

4. With the help of a Aranda Service Management (ASMS) Get the IDs of the values for the property State.

5. The property State ASMS relates to ownership Status of Jira Server.

6. Get the values for the Jira Server Status property, in the postman collection shared at the bottom of the Configuration, you will find an example of how to check these statuses.

7. Establish an equivalence between the values for the States as follows:

Status JiraServer	ASMS Record Type	ID ASMS Record Type	VALUE Status JiraServer
New	New	187	1
In Progress	In Progress	188	2
On Hold	On Hold	189	3
Resolved	Resolved	190	5
Closed	Closed	191	6

8. Type the values in the “model.state” from the configuration file:

{
  "model": [
    {
      "state": [
        {
          "value": "1",
          "id": 187
        },
        {
          "value": "2",
          "id": 188
        },
        {
          "value": "3",
          "id": 189
        },
        {
          "value": "5",
          "id": 190
        },
        {
          "value": "6",
          "id": 191
        }
      ],
      "id": 15,
      "additionalFields": [
      ]
    }
  ]
}

Solution

9. In ASMS by configuration, cases require the “Solution” property to have a value. The “solution” property is determined by the state in which the case is located.

To solve this requirement, the configuration file allows you to add a value statically or obtain it directly from Jira Server, using the following property:

{
  "commentary": {
    "key": "",
    "value": ""
  }
}

Where:

“key”: Name of the Jira Server property where the solution will be obtained. “value”: Static value to be assigned to the ASMS solution.

10. Assign a Jira Server field that you will relate to the ASMS “Solution” field

11. Type in the configuration file the relationship of the ASMS solution field to the Jira Server field.

Keep in mind that not all states require a solution, it depends on the configuration of the platforms.

{
  "model": [
    {
      "state": [
        {
          "value": "1",
          "id": 187
        },
        {
          "value": "2",
          "id": 188
        },
        {
          "value": "3",
          "id": 189,
          "commentary": {
            "Key": "close_notes"
          }
        },
        {
          "value": "5",
          "id": 190,
          "commentary": {
            "Key": "close_notes"
          }
        },
        {
          "value": "6",
          "id": 191,
          "commentary": {
            "Key": "close_notes"
          }
        }
      ],
      "id": 15,
      "additionalFields": [

      ]
    }
  ]
}

Additional fields

12. In ASMS and Jira Server, the creation of additional fields is allowed. To include the additional fields in the integration, follow the instructions below.

13. We recommend that you create a table with the fields you want to add in the integration as follows:

field in Jira Server	field in ASMS	Jira Server field id
Fixed field	Fixed field	u_campo_fijo 286
Short text	Short text	u_texto_corto 287
towns	towns	u_glide_list 288
Configuration Item	Configuration Item	u_reference_12 298

14. Choose the type of integration to which each field will be related: FIELDVALUE, VALUE, or MAPPING and write the information to the json file.

The value property is only required when constant values are desired.

{
  "model": [
    {
      "state": [
      ],
      "id": 0,
      "additionalFields": [
        {
          "type": "VALUE",
          "id": 286,
          "value": "un valor que quiero que sea constante",
          "field": {
            "key": "u_campo_fijo"
          }
        },
        {
          "type": "FIELDVALUE",
          "id": 287,
          "field": {
            "key": "u_texto_corto"
          }
        },
        {
          "type": "MAPPING",
          "id": 288,
          "field": {
            "key": "u_glide_list"
          }
        },
        {
          "type": "FIELDVALUE",
          "id": 298,
          "field": {
            "key": "u_reference_12"
          }
        }
      ]
    }
  ]
}

15. To complete the configuration in the MAPPING types, you have to add the mapping property.

16. To complete the configuration of the MAPPING type, list the ids of the values in ASMS and Jira Server and write them in the mapping property, where id is the identifier of the value of the list in ASMS and value in identifier of the value in the list of Jira Server.

Example for a list of values of the Mapping, with the help of an ASMS administrator, identify the IDs of each value of the additional field in ASMS and the IDs of each value of the additional field in Jira Cloud

field in Jira Cloud	field in ASMS	Id value Jira Cloud Id value ASMS
Countries	Countries	10100	35
Countries	Countries	10101	34

{
  "model": [
    {
      "state": [

      ],
      "id": 0,
      "additionalFields": [
        {
          "type": "VALUE",
          "id": 286,
          "value": "un valor que quiero que sea constante",
          "field": {
            "key": "u_campo_fijo"
          }
        },
        {
          "type": "FIELDVALUE",
          "id": 287,
          "field": {
            "key": "u_texto_corto"
          }
        },
        {
          "type": "MAPPING",
          "id": 288,
          "field": {
            "key": "u_glide_list"
          }
        },
        {
          "type": "FIELDVALUE",
          "id": 298,
          "field": {
            "key": "u_reference_12"
          }
        }
      ]
    }
  ]
}

Continuar: Registrar la propiedad “Urgency” (paso 5) ↪
↩ Return