Arctera™ Insight Surveillance Web Client User Guide
- Introducing Arctera Insight Surveillance
- Getting started
- Working with dashboard widgets
- Managing employees and employee groups
- Managing departments
- Managing reviewer assignment
- Managing research folders
- Managing department users
- Managing department-level archives
- Managing department-level searches
- Managing department-specific hotword sets
- Managing department-specific labels
- Managing department-specific review comments
- Viewing employees associated with departments
- Managing users, roles, and permissions
- Managing application-level archives
- Managing application-level searches
- Managing application-specific hotword sets
- Managing application-specific labels
- Managing application-specific review comments
- Managing search schedules
- Managing export operations
- Managing reviews
- Working with reports
- Enhanced reporting
- Departments API
- Users API
- Roles API
- User Roles API
- Classification Tags API
- Labels API
- Searches API
- ItemMetrics API
- Reviewer Mapping API
- MonitoredEmployees API
- Evidence of Review API
- Item Classification Metrics API
- Item Label Metrics API
- Item Hotword Metrics API
- Item Details API
- Managing Power BI templates for reporting APIs
- Managing application wide audit settings
- Working with audit viewer
- Managing application wide review setting
Item Details Async API
ItemDetailsAsync | This API submits the report generation request which executes asynchronously. The result of this API contains the identifier for the report, status, and location for retrieving the report data. This report displays items that have been archived and discovered within the Insight Surveillance application. It includes metadata such as subject and author, as well as a history of actions performed on the item, including label assignment, marking, escalation, appraisal, and commenting. The report identifier and locations in the result can be used to track the report generation operation. Note: If the number of records in the report exceeds 400,000 records, the result will be truncated. The extra records beyond the limit (400,000) are not included in the report. If the result is truncated, refine the filter criteria to narrow down the number of records and retrieve more specific data. |
To use the ItemDetailsAsync API, follow the steps below:
Call the ItemDetailsAsync API to submit a report generation request.
This asynchronous API supports GET and POST query methods. Use any of the following as needed:
GET https://<Reporting endpoint base URL>/OData/ ItemDetailsAsync?ReportName=<Name of the report>&StartDate=<YYYY-MM-DD>& EndDate=<YYYY-MM-DD>
POST https://<Reporting endpoint base URL>/OData/ ItemDetailsAsync
GET https://<Reporting endpoint Base URL>/odata/ ItemDetailsAsync?ReportName=<Name of the report>&StartDate= <YYYY-MM-DD>& EndDate=<YYYY-MM-DD>&DateType=CaptureDate or ItemHistoryDate& Departments=[<DeptID1>,<DeptID2>,...]&MessageTypes=[<MessageType ID1>,< MessageType ID2>,...]&IncludeItemHistory=[True or False]& ItemHistoryEventType=[1, 2, 3, 4, and/or 5]
POST https://<Reporting endpoint base URL>/OData/ItemDetailsAsync
The following parameters/filters can be used with the ItemDetailsAsync API when invoked using the GET and POST methods. The system uses the AND operator between the filters to return the result based on the specified filters.
ReportName
Mandatory
Specify the name of the report you want to generate.
The report name can be up to a maximum of 256 characters long.
Special characters are not allowed; only alphanumeric values are permitted.
StartDate
Mandatory
StartDate refers to the beginning of the date range used to filter items in Insight Surveillance. The interpretation of this filter depends on the selected DateType:
If DateType = CaptureDate, StartDate refers to the date the items were captured or ingested into Insight Surveillance.
If DateType = ItemHistoryDate, StartDate refer to the dates when specific actions - such as commenting, labeling, or escalation - were initially performed on the items.
Date in the YYYY-MM-DD format that is StartDate.
EndDate
Mandatory
EndDate refers to the end of the date range used to filter items in Insight Surveillance. The interpretation of this filter depends on the selected DateType:
If DateType = CaptureDate, EndDate refers to the date the items were captured or ingested into Insight Surveillance.
If DateType = ItemHistoryDate, EndDate refer to the date when specific actions - such as commenting, labeling, or escalation - were finally initially performed on the items.
Date in the YYYY-MM-DD format that is EndDate.
DateType
Optional
Specify the date type to return the count of item IDs based on their capture date or the item history date.
Select any of the following options as required:
This option is selected by default.
It is the specific date on which the item is captured into the Insight Surveillance application.
If you select this option, the result includes items captured within the specified date range inside surveillance, along with the metadata and complete history of those items.
Select this option if you want to get item count by the item history date.
It is a specific date, falling within the range of the StartDate and EndDate, on which the item's historical event occurred.
If you select this option, the result includes items captured within the specified date range inside surveillance, along with the metadata and complete history of those items.
String.
Departments
Optional
Specifies the departments to which the item belongs and returns item counts for items within that department.
JSON array of integers id (identifier fields) that is Department IDs.
As an input, this API can pass maximum of 1000 Departments IDs.
To include results for all departments of a specified customer in a report, do not specify any department IDs in a query.
To include results for specific departments of a specified customer in a report, specify department IDs in the query.
Note:
To get the Department IDs, See Departments API. Refer to the field only.
MessageTypes
Optional
Specifies the type of captured items and returns item counts for items that have the specified message type.
: JSON array of integers 'id'(identifier fields) that is MessageTypes IDs.
: As an input, the ItemDetails API can pass maximum 100 MessageTypes IDs on a single page.
IncludeItemHistory
Optional
Determines whether the history of items is included or excluded in the output.
Set this value as
to exclude history of items from the output. By default this value is set to False.Set this value as
to include history of items in the output.
ItemHistoryEventType
Optional
Includes or excludes the item history event type in the output based on the value set for the IncludeItemHistory field.
If the
= (default) and = , then, the report compares dates with the item's CaptureDate and does not include item history in the results. Refer to the sample scenario below.If the
= (default) and is set to 1 (Appraisal), 2 (Comment), or 4 (Action Status - Mark)), then, the report returns:If the
= and is set to 2 (Comment), 3 (Escalation), or 5 (Action Status - Label), the report returns:Items with comment, escalation, or label actions performed between the specified start and end dates are retrieved.
From these results, full metadata and history are returned for each item.
Refer to the sample scenario below.
Items that have comment, escalation, or label actions performed between the specified start and end dates.
From that result, full metadata and history is returned for those items.
Possible values of item history event type are:
1 - Appraisal
2 - Comment
3 - Escalation
4 - Action Status - Mark
5 - Action Status - Label
6 - Action Status - Preview
: Integer ID of the item.
As an input, this API can pass maximum of 10 ItemHistoryEventType IDs.
Sample input:
Sample response:
Sample input
Sample response:
Sample request:
Sample response:
Name
Description
reportId
Displays report ID. It is generated upon successful execution of API.
reportName
Displays report name. It is generated upon successful execution of API.
reportType
Displays the report type as Item Details.
reportDate
Displays the date of report generation after successful execution of API.
reportStatus
Displays report status. For more information on statuses, See Report Status API.
info
Displays a message if the report request has queued successfully or not.
newReportInstanceQueued
Specifies whether a new report generation request has been submitted or not. The Rate Limiting feature restricts submission of multiple requests with identical input parameters if attempted within one minute.
It returns the following values:
: The value is shown as False, if the input parameters of the current request are identical to the parameters of the already submitted request within one minute, a new report will not be queued. As a result, the details of the existing report request are returned.
reportStatusLocation
Displays a URL with report ID.
To view the status of this report, use the same URL.
reportDataLocation
Displays a URL for the location of report data.
To access the report data, use the same URL.
Call the ReportStatus API to get the status of the ItemDetailsAsync API report. See Report Status API.
Once the report is ready, call the ItemDetails API to retrieve the report data from the asynchronous API. See Item Details API.