You can preset CA User Activity Reporting Module filters for an incident report in XML format and add them to the getReportViewer URL using the IncidentFilterXML term. You can nest multiple filters, using AND and OR terms and parentheses. IncidentFilter specifications work in the same way as Filter specifications, and share the same elements and operators.
IncidentFilter XML specifications apply only to incident queries contained in reports. However, a report can contain both event and incident queries. To access and filter such a report, your API URL can contain both Filter XML and IncidentFilter XML specifications.
Important! IncidentFilterXml terms are complex, and the API performs no validation. Invalid filter terms result in a query error. For this reason, we recommend that you take particular care in constructing your filter terms.
IncidentFilter XML Specification Example
This example shows a getReportViewer call with a filter statement. The filter terms are shown expanded for clarity.
https://ELMSERVER:5250/spin/calmapi/getObject.csp?type=getQueryViewer&objectId=Subscription/panels/Incidents_by_Priority=ELMSERVER&incidentfilterXml=
<Filter logic="AND" lparens="1" col="incident_createtime_gmt" colfunc="" oper="GREATEQ" val="1285854741" rparens="0" filterTag="" substituteValue="false" isDynamic="true"/>
<Filter logic="AND" lparens="0" col="incident_createtime_gmt" colfunc="" oper="LEQ" val="1285876341" rparens="1" filterTag="" substituteValue="false" isDynamic="true"/>
"&incidentfilterxml=" specifies that an incident filter statement follows.
The filter specifies all incidents created within a specified time span.
|
Copyright © 2013 CA.
All rights reserved.
|
|