Skip to content

Method for obtaining reporting log fields for the current user

POST

The method returns the log fields for the current user.

Unlike the method for obtaining the fields of the reporting log (for all users), this method forcibly adds a filter by the current user.

Filtering, sorting, setting fields, etc. happens in the same way as for other partial-load methods. See, for example, the description of the method "[Search by requests] (/documentation/page/733)"

Request Body

application/json
object

Offset from the beginning of the search, i.e. if we want to get from the 10th record, then we transfer 10

Format"int32"

Limit (how many records will be returned)

Format"int32"

A collection of fields to return in search results

integer[]
Format"int64"

Name of the field by which sorting must be done. Since release 2.0.0-65, the orderByFields collection should be used for sorting. In the meantime, there is no need to worry about it. ”

object[]

Array of fields to sort by.

"orderByFields": [
{"field": "creationDate"},
{"field": "manualStatusId", "direction": "desc"}
]

In this example, sorting is done by fields creationDate and manualStatusId . Also, the result is sorted in descending order. For sorting direction, use the manualStatusId parameter. If the direction field is not specified, then sorting by the field is performed in ascending order. If both sorting methods are passed in the kernel request, then the old sorting method is ignored. These changes are effective from release 2.0.0-65. See also the description of the orderBy and orderDirection parameters

Sorting direction of search results DESC - descending ASC - by growing Since 2.0.0 release -65 for sorting direction, pass the direction in the orderByFields collection

Number of records returned

Format"int32"
object[]

Conditions for searching (filtering) all types of contracts, the presence of the searchFields parameter is required, but it can be an empty collection (search conditions may not be specified). It is strongly recommended to set filtering parameters

Name of the box to filter by. The rules for forming this field are as follows: Any fields from entities Contract and from list of dynamic parameters that are not foreign keys . For example: " name ", " CreationDate " and so on. A foreign key attribute is an indication in the parameter description to a method that allows by ID ( by parameter value - get the object). Example: clientId. For fields that are foreign keys - you can get any fields object whose ID is specified in the field. For example: in the Application object there is a clientId field, which is a foreign key. This means that we can request any field of the client object: client.id, client.lastName, and so on. There are also options in which we can request fields from deeper entities, if there are foreign keys in the object. For example: client.passport.seria - allows you to get a series of client passports, from which the application was made

Value for grouping search parameters (filtering) in the OR condition.
The field is optional and is used in cases when you need to search not all conditions by AND, but also by OR.
For example, you need to find all records with the value XXXX in field1 and YYYY or ZZZZ in field2.
In this case, you can use the ** ornumber field. ** The value can be a number or a symbol, but unique within one group of OR conditions. The reserved value is -1

** Example 1 **:

{ "field": "contract.id", "value": " 10134756 " },

{ "field": "loanAmount", "value": " 10000 ",
"ornumber": " 1 ", },

{ "field": "name", " value ":" 5% ",
"Ornumber": " 1 ", },
This example will search for all entries that have contract.id 10134756 and at the same time one of the conditions is met field loanAmount is equal to 10000 or name starts with 5.
That is, in an SQL expression: contract.id = 10134756 AND (loanAmount = 10000 OR name like" 5% ")

** Example 2 **:

{ " field ":" name ", " value ":" 1% ",
"Ornumber": " 1 ", },

{ " field ":" name ", " value ":" 5% ",
"Ornumber": " 1 ", },

{ " field ":" loanAmount ", " value ":" 10000 ",
" ornumber ":" 2 ", },

{ " field ":" loanAmount ", " value ":" 20000 ",
" ornumber ":" 2 ", },

In the expression SQL language: ( name like " 1% " OR name like "5 % ") AND (loanAmount = 10000 OR loanAmount = 20000)

Responses

OK

*/*
object
object[]
Format"int64"
Valid values"error""ok"
Format"int64"