Relationship of additional states and fields to HPTechpulse CI properties
The relationship of the states between the platforms and the additional fields is represented by the following JSON:
{
"category": [
{
"id": 0,
"reference": "",
"keys": [],
"projectId": 0,
"additionalFields": [
{
"id": 0,
"key": "",
"mapping": [
{
"id": 0,
"value": ""
}
]
},
{
"id": 0,
"key": "",
"value": [""]
},
{
"id": 0,
"key": ""
}
],
"state": [
{
"id": 0,
"reason": 0,
"value": ""
}
]
}
]
}
Where:
Properties
| Properties | Description | |
|---|---|---|
| Id | Category identifier in CMDB | |
| Reference | Unique identifier to create a relationship between category and ci concepts | see |
| Keys | List of deviceType to migrate to the Aranda CMDB by category | |
| projectId | Identifier of the project to be related to the CI’s | |
| additionalFields | Relationship of additional fields between CMDB and HPTechpulse fields | See |
| state | Relationship of CMDB Status Values and HPTechpulse Device Statuses | See |
Relación entre los campos adicionales y los campos de las clases de Techpulse
The relationship between the additional fields and the equivalent fields of Techpulse is made using the following JSON structure:
additionalFields internal properties
{
"id": 0,
"key": "",
"value": [""],
"mapping": [
{
"id": 0,
"value": ""
}
]
}
Where:
| Properties | Description |
|---|---|
| Id | Identifier of the additional field in CMD |
| Key | Field identifier in Techpulse |
| value | Allows you to add values to additional fields as constant values |
| mapping | Value relationship for CMDB and Techpulse fields, where “id” is the identifier in CMDB and “value” is the identifier in Techpulse |
List of additional supported field types
Currently, there is no type listing for the courses on Techpulse; therefore, they are all considered string-type.
These can be mapped to short text, long text, date, and list fields in the CMDB.
List of states
To relate the states, the integration provides the following json schema:
{
"value": "",
"id": 0,
"reason": 0
}
Where:
| Property | Description |
|---|---|
| value | Status ID in techpulse Techpulse states |
| Id | Status ID in CMDB |
| reason | Status Change Reason Identifier in CMDB |
EXAMPLE: CMDB / Techpulse State Relationship
To create the list of states, follow the instructions below:
- Get the IDs of the CMDB states.
- Get the IDs of Techpulse states.
- Assign the following status equivalence:
| Id status in CMDB | Status in CMDB | Value state techpulse |
|---|---|---|
| 1 | NEW | Enrolled |
| 13 | CLOSED | Archived |
- Type the Id status in CMDB On Property “id” and the Value state techpulse of its equivalent taken from Techpulse On Property value:
[
{
"id": 1,
"value": "value_new"
},
{
"id": 13,
"value": "value_closed"
}
]