...
Their proven platform, deep values, and knowledgeable executives make EasyVista always trying to advance ITSM
Connect EasyVista with Devo SOAR
Navigate to Automations > Integrations.
Search for EasyVista.
Click Details, then the + icon. Enter the required information in the following fields.
Label: Enter a connection name.
Reference Values: Define variables here to templatize integration connections and actions. For example, you can use https://www.{{hostname}}.com where, hostname is a variable defined in this input. For more information on how to add data, see 'Add Data' Input Type for Integrations.
Verify SSL: Select option to verify connecting server's SSL certificate (Default is Verify SSL Certificate).
Remote Agent: Run this integration using the Devo SOAR Remote Agent.
API URL: URL of EasyVista Host.
Username: User name to log in with.
Password: Password to log in with.
After you've entered all the details, click Connect.
Actions for EasyVista
Tickets List
Tickets List allows a list of tickets to be obtained (a ticket includes incident, service request, change request, investment request, problem and event)
Input Field
Choose a connection that you have previously created and then fill in the necessary information in the following input fields to complete the connection.
Input Name | Description | Required |
|---|---|---|
Search | Jinja-templated search fields. Example: rfc_number:I161026_000005. (Default is no search filter) | Optional |
Limit | Maximum number of tickets to display. (Default is 100) | Optional |
Sort | Jinja-templated sort in ascending or descending order. Syntax: field1[+asc | +desc],field2[+asc |
Fields to Display | Jinja-templated comma separated fields to display. Example: submit_date_ut,end_date_ut. (Default is all fields) | Optional |
Output
JSON containing the following items:
...
| Code Block |
|---|
## Ticket Details
Ticket Details allows information about a specified ticket to be obtained (a ticket includes incident, service request, change request, investment request, problem and event)
### Input Field
Choose a connection that you have previously created and then fill in the necessary information in the following input fields to complete the connection.
| Input Name | Description | Required |
| :---------------- | :------------------------------------------------------------------------------------------------------------------------------------ | :------- |
| Ticket Identifier | [Jinja-templated](doc:jinja-template) ticket identifier of the ticket to display. Example: {{parent_column}} | Required |
| Fields to Display | [Jinja-templated](doc:jinja-template) comma separated fields to display. Example: submit_date_ut,end_date_ut. (Default is all fields) | Optional |
### Output
JSON containing the following items:
- has_error: True/False
- error: message/null
- result: Analysis details.
``` {json}"data":{
"E_PRB_TFS_TICKET":{...}
"E_PRB_RC_WHY3":{...}
"E_Legal_Policy_State":{...}
"E_PRE_ROOT_CAUSE":""
"RFC_NUMBER":"170831_055316"
"E_PRB_ROOT_CAUSE":{...}
"ESTIMATED_PERCENT_COMPLETE":""
"E_ADDITIONAL_RECIPIENTS":{...}
"E_KCL_Check_Amt":{...}
"E_PRB_RESOLUTION_CAT":""
"AVAILABLE_FIELD_3":""
"DYNAMIC_DETAILS":{...}
"SUBMITTED_BY":""
"E_SPEND_PO_NEEDED":""
"E_PRB_DATA_LexisNexis":{...}
"E_PRB_DATA_Associates":{...}
"E_Legal_Medical_Reference":{...}
"E_PRB_DETECTED_DATE":""
"E_KCL_Mkt_Audience":{...}
"E_PRB_RELATED_PROBLEM":{...} |
Update a Ticket
Update a Ticket allows a specified ticket to be modified (a ticket includes incident, service request, change request, investment request, problem and event).
Input Field
Choose a connection that you have previously created and then fill in the necessary information in the following input fields to complete the connection.
Input Name | Description | Required |
|---|---|---|
Ticket Identifier | Jinja-templated ticket identifier of the ticket to display. Example: {{parent_column}} | Required |
Fields to Update | Jinja-templated JSON containing fields to be included with the ticket. Example: { "ANALYTICAL_CHARGE_ID":"123", "asset_id": "27618" }. All available fields are: analytical_charge_id, asset_id, asset_serial, asset_tag, available_field_x, ci, ci_id, ci_serial, comment, continuity_plan_id, description, external_reference, impact_id, known_problems_id, net_price_cur_id, origin_tool_id, owner_id, owning_group_id, release_id, rental_net_price_cur_id, request_origin_id, requestor_phone, root_cause_id, submit_date_ut, system_id, urgency_id | Optional |
Output
JSON containing the following items:
...
| Code Block |
|---|
## Close a Ticket
Close a Ticket allows a specified ticket to be ended (a ticket includes incident, service request, change request, investment request, problem and event).
### Input Field
Choose a connection that you have previously created and then fill in the necessary information in the following input fields to complete the connection.
| Input Name | Description | Required |
| :------------------------------------ | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :------- |
| Ticket Identifier | [Jinja-templated](doc:jinja-template) ticket identifier of the ticket to display. Example: {{parent_column}} | Required |
| Identifier of the topic of the ticket | [Jinja-templated](doc:jinja-template) Identifier of the topic of the ticket. Required if the ticket needs to be requalified before closing: used to specify the SD_CATALOG_ID | Optional |
| Comment | [Jinja-templated](doc:jinja-template) Comment explaining the closing of the ticket. Example: Closing the ticket because {{parent_column_reason}} | Optional |
| Delete Actions | Used to indicate the measures to be taken for ongoing actions in the ticket. (Default is False) | Optional |
| End Date | [Jinja-templated](doc:jinja-template) closing date of open actions associated with the ticket and the anticipated closure action. By default, the current date (now). Note: The closing date of the ticket is always the current date, i.e. the date on which the method was called. It cannot be modified. Example: {{parent_column}} | Optional |
| Final Status (GUID) | [Jinja-templated](doc:jinja-template) identifier (GUID) of the topic of the ticket. Required if the ticket needs to be re-qualified before closing: used to specify the SD_CATALOG_ID | Optional |
### Output
JSON containing the following items:
- has_error: True/False
- error: message/null
- result: URL details.
``` {json}"data":{
"HREF":"https://ABC"
"error":NULL
"has_error":false
} |
Assets List
Get a list of assets (an asset includes equipment, license and contract).
Input Field
Choose a connection that you have previously created and then fill in the necessary information in the following input fields to complete the connection.
Input Name | Description | Required |
|---|---|---|
Limit | Takes a job ID and fetches its report. Works with either File or URL jobs. | Optional |
Sort | Jinja-templated sort in ascending or descending order. Syntax: field1[+asc | +desc],field2[+asc |
Fields to Display | Jinja-templated comma separated fields to display. Example: asset_tag,serial_number. (Default is all fields) | Optional |
Search | Jinja-templated search fields. Example: employee.e_mail:btalma@itassetservices.com. (Default is no search filter) | Optional |
Output
JSON containing the following items:
...
| Code Block |
|---|
## Asset Details
Asset Details can fetch information about a specified asset to be obtained (an asset includes equipment, license and contract)
### Input Field
Choose a connection that you have previously created and then fill in the necessary information in the following input fields to complete the connection.
| Input Name | Description | Required |
| :---------------- | :--------------------------------------------------------------------------------------------------------------------------------- | :------- |
| Asset ID | Column name from parent table to lookup URL values. | Required |
| Fields to Display | [Jinja-templated](doc:jinja-template) comma separated fields to display. Example: asset_tag,serial_number. (Default is all fields) | Optional |
### Output
A JSON object containing multiple rows of result:
- has_error: True/False
- error: message/null
- result: Scan details.
``` {json}"data":{
"MONTHLY_FIXED_COST":""
"E_SERVER_FUNCTION":{...}
"D_HARDWARE_GUID":""
"CONTRACT_TYPE_ID":""
"E_PII_Data":{...}
"E_CMDB_APPLICATION_MAJOR_MINOR":{...}
"E_TD_SEC_AUDIT_NOTES":{...}
"SCHEDULED_END":""
"BEFORE_LOAN_LOCATION_PATH":""
"E_CMDB_CERT_ALTERNATE_NAME":{...}
"AVAILABLE_FIELD_3":""
"RENEWAL_VALUE_CUR_ID":""
"DELIVERY_NUMBER":""
"UPDATED_BY_DISCOVERY":"0"
"E_GTS_AVP_OWNER_ID":""
"CATALOG_ID":"1"
"E_SSO_ALIGNED":""
"TERM":""
"NEXT_MAINTENANCE_DATE":""
"NOTICE":""
"WARANTY_TYPE_ID":""
"ASSET_LABEL":""
"E_LAST_UPDATED":"" |
Employees List
Get a list of employees.
Input Field
Choose a connection that you have previously created and then fill in the necessary information in the following input fields to complete the connection.
Input Name | Description | Required |
|---|---|---|
Limit | Column name from the parent table to lookup hash values. | Optional |
Sort | Jinja-templated sort in ascending or descending order. Syntax: field1[+asc | +desc],field2[+asc |
Fields to Display | Jinja-templated comma separated fields to display. Example: asset_tag,serial_number. (Default is all fields) | Optional |
Search | Jinja-templated search fields. Example: employee.e_mail:btalma@itassetservices.com. (Default is no search filter) | Optional |
Output
A JSON object containing multiple rows of result:
...
| Code Block |
|---|
## Employee Details
This action allows information about a specified employee to be obtained.
### Input Field
Choose a connection that you have previously created and then fill in the necessary information in the following input fields to complete the connection.
| Input Name | Description | Required |
| :------------------ | :-------------------------------------------------------------------------------------------------------------------------- | :------- |
| Employee Identifier | [Jinja-templated](doc:jinja-template) employee identifier of the employee to display. Example: {{parent_column}} | Required |
| Fields to Display | [Jinja-templated](doc:jinja-template) comma separated fields to display. Example: last_name,e_mail. (Default is all fields) | Optional |
### Output
A JSON object containing multiple rows of result:
- has_error: True/False
- error: message/null
- result: Report details.
``` {json}"data":{
"E_AD_GUID":{...}
"AVAILABLE_FIELD_3":""
"DELEGATION_FROM":""
"AVAILABLE_FIELD_2":""
"CELLULAR_NUMBER":""
"VIP_LEVEL_ID":""
"PLANNING_ID":""
"SUPPLIER_ID":""
"EMPLOYEE_ID":"2"
"AVAILABLE_FIELD_4":""
"IS_SYSTEM":""
"LOCATION_ID":"188"
"DEFAULT_COST_CENTER_ID":""
"COST_PER_HOUR_CUR_ID":"4"
"DEPARTMENT_ID":"1202"
"LOCATION_PATH":"HO Third Floor"
"NOTIFICATION_TYPE_ID":"1"
"TITLE_ID":""
"E_WFH":{...}
"COMMENT_EMPLOYEE":{...} |
List Configuration Items
This action allows a list of configuration items (CIs) to be obtained.
Input Field
Choose a connection that you have previously created and then fill in the necessary information in the following input fields to complete the connection.
Input Name | Description | Required |
|---|---|---|
Limit | Column name from the parent table to lookup hash values. | Optional |
Sort | Jinja-templated sort in ascending or descending order. Syntax: field1[+asc | +desc],field2[+asc |
Fields to Display | Jinja-templated comma separated fields to display. Example: last_name,e_mail. (Default is all fields) | Optional |
Search | Jinja-templated search fields. Example: employee.e_mail:btalma@itassetservices.com. (Default is no search filter) | Optional |
Output
A JSON object containing multiple rows of result:
...
| Code Block |
|---|
## Configuration Items Details
This action allows information about a specified configuration item (CI) to be obtained.
### Input Field
Choose a connection that you have previously created and then fill in the necessary information in the following input fields to complete the connection.
| Input Name | Description | Required |
| :---------------- | :-------------------------------------------------------------------------------------------------------------------------- | :------- |
| CI identifier | [Jinja-templated](doc:jinja-template) configuration identifier. Example: {{parent_column}} | Required |
| Fields to Display | [Jinja-templated](doc:jinja-template) comma separated fields to display. Example: last_name,e_mail. (Default is all fields) | Optional |
### Output
A JSON object containing multiple rows of result:
- has_error: True/False
- error: message/null
- result: Report details.
``` {json}data":{
"MONTHLY_FIXED_COST":""
"E_SERVER_FUNCTION":{...}
"D_HARDWARE_GUID":""
"CONTRACT_TYPE_ID":""
"E_PII_Data":{...}
"E_CMDB_APPLICATION_MAJOR_MINOR":{...}
"E_TD_SEC_AUDIT_NOTES":{...}
"SCHEDULED_END":""
"BEFORE_LOAN_LOCATION_PATH":""
"E_CMDB_CERT_ALTERNATE_NAME":{...}
"AVAILABLE_FIELD_3":"NA"
"RENEWAL_VALUE_CUR_ID":""
"DELIVERY_NUMBER":""
"UPDATED_BY_DISCOVERY":"0"
"E_GTS_AVP_OWNER_ID":"1133" |
Release Notes
v2.0.0- Updated architecture to support IO via filesystemv1.0.1- Added 10 new actions.
...