Relationship of additional states and fields to ServiceNow class properties
This section indicates the relationship of the states between the platforms and the additional fields according to the configuration of the platforms
{
"model": [
{
"id": 0,
"state": [
{
"value": "",
"id": 0,
"commentary": {
"Key": "",
"value": ""
}
}
],
"additionalFields": [
{
"id": 0,
"field": {
"type": "",
"key": "",
"SearchBy": ""
},
"mapping": [
{
"id": 0,
"value": ""
}
]
}
]
}
]
}
Properties
The following is a description of the properties of the above json
Properties | Description | |
---|---|---|
Id | Model identifier in ASMS | |
state | Relationship of ASMS and ServiceNow status values | See |
additionalFields | Relationship of the additional fields between ASMS and ServiceNow | See |
Relación de los estados
To relate the states, the integration provides the following json schema:
{
"value": "",
"id": 0,
"commentary": {
"value": "",
"Key": ""
}
}
The following is a description of the internal properties of the state object
Properties | Description |
---|---|
value | ServiceNow status identifier (sys_id if it is a “Reference” type field or value if it is a “Choice” type field) ServiceNow Properties |
Id | Status Identifier in ASMS |
commentary | Relates the solution field to the change of state in ASMS, where “key” is the identifier of the field in ServiceNow and “value” is the value to be added in these fields |
EXAMPLE: ASMS/ServiceNow Status Ratio
To create the list of states, follow the instructions below:
- Get the IDs of ASMS states.
- Get sys_id or value from ServiceNow statuses.
- Assign the following status equivalence:
- The property commentary (Represents the “Case Solution”), relates to an equivalent field “close_notes” on ServiceNow.
Status in ServiceNow | State in Aranda | ID STATE ARANDA | VALUE STATE SERVICENOW |
New | NEW | 1 | value_new |
Closed | CLOSED | 13 | value_closed |
- Type the ID STATE ARANDA On Property “id” and the VALUE STATE SERVICENOW of its equivalent taken from the CMDB de ServiceNow On Property value:
[
{
"id": 1,
"value": "value_new",
"commentary": {
"Key": "close_notes"
}
},
{
"id": 13,
"value": "value_closed",
"commentary": {
"Key": "close_notes"
}
}
]
Relación entre los campos adicionales y los campos de las clases de ServiceNow
Below is an informative image of how the additional fields might look on the ASMS platform, grouped into the additional information segment
⚐ Note: Additional fields are created according to the customer’s needs, this image is only representative.

additionalFields internal properties
{
"id": 0,
"field": {
"type": "",
"key": "",
"SearchBy": ""
},
"mapping": [
{
"id": 0,
"value": ""
}
]
}
The following is a description of the internal properties of the additionalFields object
Properties | Description | |
---|---|---|
Id | Additional field identifier in ASMS | |
field | ServiceNow Field Information, Learn More | see |
mapping | The relationship between ASMS and ServiceNow field values, where “id” is the identifier in ASMS and “value” is the identifier in ServiceNow (sys_id if it is a “Reference” type field or value if it is a “Choice” type field) |
Listado de los tipos de campo adicionales soportados
Listado de relación entre los tipos de campos de las plataformas:
ASMS | Field ID in ServiceNow | Field Name/Label in ServiceNow |
---|---|---|
Short Text | String | String |
Paragraph | String | String |
True or False | true/false | True/False |
Date | glide_date | Date |
Date and Time | glide_date_time, calendar_date_time | Date/Time, Calendar Date/Time |
Numeric | Integer, Longint | Integer, Long |
Decimal | decimal | Decimal |
List | choice, glide_list, reference | Choice, List, Reference |
Catalog (List) | reference, choice | Choice, Reference |
Currency | currency, price | Currency, Price |
Link | URL | URL |
Time | glide_utc_time | UTC Time |
⚐ Note: Associating 2 different fields to those listed in the previous table results in a runtime error***