Searching the Help
To search for information in the Help, type a word or phrase in the Search box. When you enter a group of words, OR is inferred. You can use Boolean operators to refine your search.
Results returned are case insensitive. However, results ranking takes case into account and assigns higher scores to case matches. Therefore, a search for "cats" followed by a search for "Cats" would return the same number of Help topics, but the order in which the topics are listed would be different.
Search for | Example | Results |
---|---|---|
A single word | cat
|
Topics that contain the word "cat". You will also find its grammatical variations, such as "cats". |
A phrase. You can specify that the search results contain a specific phrase. |
"cat food" (quotation marks) |
Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase. |
Search for | Operator | Example |
---|---|---|
Two or more words in the same topic |
|
|
Either word in a topic |
|
|
Topics that do not contain a specific word or phrase |
|
|
Topics that contain one string and do not contain another | ^ (caret) |
cat ^ mouse
|
A combination of search types | ( ) parentheses |
|
Generate Change Report
This call generate a change report about the attributes of the given CIs.
URL
changeReports/generate/blacklist
changeReports/generate/whitelist
changeReports/generate/all
Method
POST
Headers
Required:
Authorization: Bearer <token>
Note <token>
is the token that was returned by the Authentication call.
Example:
Authorization: Bearer eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJleHAiOjE0Njc5ODQ5MTcsImN1c3RvbWVyIjoxLCJ1c2VybmFtZSI6InN5c2FkbWluIn0.Ph8WHtzvpvfuH1j0CtwHqyBhX1uLlfhr0eQQ7m0_gT0
Request type
JSON
Response type
JSON
URL Parameters
Required:
none
Optional:
none
Payload
There are three cases for each of the URLs above:
Case 1: Requesting the following JSON to <host>/rest-api/changeReports/generate/blacklist
{ "dateFrom": "1454364000000", "dateTo" : "1485986400000", "viewName": "yourView", "attributes": [ "description","name "] }
generates a report that contains no information about the attributes written in list "attributes"
.
Case 2: Requesting the following Json to <host>/rest-api/changeReports/generate/whitelist
{ "dateFrom": "1454364000000", "dateTo" : "1485986400000", "viewName": "yourView", "attributes": [ "description","name "] }
generates a report that contains information just about the attributes written in list "attributes"
.
Case 3: Requesting the following JSON to <host>/rest-api/changeReports/generate/all
{ "dateFrom": "1454364000000", "dateTo" : "1485986400000", "viewName": "yourView", }
generates a report that contains information about all attributes.
Note Details about attributes:
dateFrom represents the date from which changes of attributes should be taken into consideration at the generated report.
dateTo represents the limit date to which changes of attributes should be taken into consideration at the generated report.
viewName is a view that has as result some CIs on which report will be based on.
attributes is a list of attributes which should or should not appear in the generated report.
Success response
Code: 200
Content: has two main objects
changes represent all the changes to the found CIs
{
"changes":{ "<ci-id>":{ "ciId":"<ci-id>", "displayLabel":"<display-label>", "className":"class-name>", "properties": [ { "name": "name", "value": "value" }, { "name": "name", "value": "value" } ], "changes":{ "<attribute-name>":[ { "attribute":"<attribute-name>", "oldValue":"<attribute-old-value>", "newValue":"<attribute-new-value>", "changer":"<changer>", "changeDate":"<date-of-change>" }, { "attribute":"<attribute-name>", "oldValue":"<attribute-old-value>", "newValue":"<attribute-new-value>", "changer":"<changer>", "changeDate":"<date-of-change>" },
...
],
"<attribute-name>":[ { "attribute":"<attribute-name>", "oldValue":"<attribute-old-value>", "newValue":"<attribute-new-value>", "changer":"<changer>", "changeDate":"<date-of-change>" }, { "attribute":"<attribute-name>", "oldValue":"<attribute-old-value>", "newValue":"<attribute-new-value>", "changer":"<changer>", "changeDate":"<date-of-change>" },
...
]
}
},
...
},
}
{ "changes":{ "4278e81d3dd6640a835e419d2865905d":{ "ciId":"4278e81d3dd6640a835e419d2865905d", "displayLabel":"create222", "className":"node", "properties": [ { "name": "Display Label", "value": "USER LABEL" }, { "name": "Create Time", "value": "Fri Jan 20 14:13:40 EET 2017" }, { "name": "Description", "value": "description" } ], "changes":{ "name":[ { "attribute":"name", "oldValue":"create2", "newValue":"create22", "changer":"User:{UISysadmin###UCMDB},LoggedInUser:{admin###UCMDB}", "changeDate":1484741091500 } ] } } }, }
Error response
none
We welcome your comments!
To open the configured email client on this computer, open an email window.
Otherwise, copy the information below to a web mail client, and send this email to ovdoc-asm@hpe.com.
Help Topic ID:
Product:
Topic Title:
Feedback: