Repository management filter with name and lastModified fields
- Updated: 2020/04/22
Repository management filter with name and lastModified fields
This example filter is based on the Repository Management API fields and parameters. This filter example searches on the bot lastModified and name fields.
This filter searches for bots in the Control Room
repository with the string "finance" in the name of the files
modified between January 7, 2020 and January 9, 2020.
Note: The Repository management API
uses role based access. That means users can only see the files and folders to which
they have access.
{
"sort": [
{
"field": "directory",
"direction": "desc"
},
{
"field": "name",
"direction": "asc"
}
],
"filter": {
"operator": "and",
"operands": [
{
"operator": "substring",
"value": "finance",
"field": "name"
},
{
"operator": "gt",
"value": "2020-01-07T00:00:00.001Z",
"field": "lastModified"
},
{
"operator": "lt",
"value": "2020-01-09T00:00:00.001Z",
"field": "lastModified"
}
]
}
}
- sort
-
- field: the name of the field used to sort the response.
- direction: the sort order. It can be asc, ascending, or desc, descending.
- filter
-
Filter consists for an operator, value, and field. Filters are operands when used in conjunction with a boolean operator, such as and.
-
operands: filters are used as operands when
combined in a filter by using a boolean operator. There are two
available boolean operators:
- or: one of the conditions must be met.
- and: all of the conditions must be met.
-
operator: there are 11 operators
NONE, lt, le, eq, ne, ge, gt, substring, and, or, not
. And and or are used to evaluate multiple filters together. The other operators are used to evaluate values within individual filters. Not all operators work with all fields. - field: the name of the field used in the filter.
- value: the value of the field to be evaluated.
-
operands: filters are used as operands when
combined in a filter by using a boolean operator. There are two
available boolean operators: