Obtaining results

To view the monitoring results for entities, go to the main page of the service, find the pool you need using the search function, and click the relevant file.

It is necessary to determine the time period (or use the option to upload the latest new triggers) and the format of the results received (“json” or “csv”).

Clicking the download icon will allow you to access the results through your browser’s built-in downloader.

Where can I find the already downloaded files with triggers?

Reformatted files can be accessed through the file-sharing interface (menu > data transfer > F2 file sharer)

It is necessary to set the value of the “Module” parameter to “Monitoring,” select the required period for which the uploads occurred, and click “Search” button.

We receive a list of folders that match the specified search criteria:

Folders are created by date, consolidating files with triggers for a specific day; the name also includes the pool number and the upload method (“latest” – most recent triggers). You can download the entire folder by clicking the download button in the quick action panel, or browse through the files inside:

Now there is an option to download each file separately.

Attachments:

Data aggregation by entities (summary):

A trigger of type summary performs data aggregation by subject and is activated when there is a quantitative change in the set of deals matching the specified conditions (e.g., filtering by status, subject type, etc.). For example:
On 10.09, the subject had 6 deals that met the filter conditions.
On 12.09, one deal was closed and thus no longer counted in the filtered results.
On the same day (12.09), the subject opened a new deal that matches the filter..
As a result, when the summary trigger fires on 12.09, the value of the field dlrefCount remained unchanged (6), but a trigger event was generated because the composition of deals changed within the same quantity.

For summary trigger events, fields in the baseData array are not populated.
In summary-type triggers, the result is generated for all agreements that meet the filtering conditions. Each agreement is displayed as a separate entry in the result.
For example, if there were 6 agreements and one of them was deleted, the result will contain 5 entries corresponding to the remaining agreements.
All cases generated during this trigger event are linked by a common eventId.