Creation of configuration file integration between ASMS and ServiceNow
The integration between the platform Aranda SERVICE MANAGEMENT (ASMS) and ServiceNow, is done by setting up a file in JSON format. It is based on the following conceptual model:

A continuación se presenta la definición del modelo conceptual:
Properties | Description | |
---|---|---|
Case: | It represents the relationship and basic information between cases in ASMS and ServiceNow. | See more |
model: | Represents the status information and additional fields in ASMS and ServiceNow cases. | See more |
typeRegister: | Represents the list of types of records to be related | See more |
service: | Represents the list of services to be listed | See more |
project: | Represents the list of projects to be related | See more |
Category: | Represents the list of categories to be related | See more |
Applicant: | Represents the list of applicants to be listed | See more |
responsibleGroup: | Represents the list of responsible groups to be related | See more |
Responsible: | Represents the list of responsible parties to be listed | See more |
Ci: | Represents the list of ICs to be related | See more |
Company: | Represents the companies responsible to relate | See more |
Client: | Represents the customers of responsible parties to relate | See more |
providers: | Represents the suppliers of responsible parties to be related | See more |
organizationalArea: | It represents the organizational area of managers to be related | See more |
Urgency: | It represents the urgency field in the relationship between cases in ASMS and ServiceNow. | See more |
Impact: | Represents the impact field on the relationship between cases in ASMS and ServiceNow. | See more |
Information to take into account:
- Case creation will always be from ServiceNow to ASMS.
- For datetime fields, consider the timeZone settings in ServiceNow.
- Instructions for getting the ASMS id’s used in the configuration file, using the ASMS API with the postman tool Instructions here
Below you can download the json structure that will be used throughout the documentation.