Page History

...

• selectsearchload. Available from ACD v.3.22       

...

           This filter will allow to handle with large number of objects matching Search query. Recommended in case if more than 10 000 entries match base filter queryQuerystring.

Contains 3 fields:

1. Search field.
2. Select field. By default populated with first N records received with basic Search queryQuerystring. Can be repopulated by data received after user will add a string to search in "search" field based on base Search queryQuerystring. 

   Example: Base search query Base Querystring defined in filter is: "objectClass:nrfRequest AND nrfSourceDN:* AND nrfRequester:*". With "re" in "search" field "select" field will be populated with records received from elasticsearch using next query: "objectClass:nrfRequest AND nrfSourceDN:* AND nrfRequester:* AND nrfSourceDN:*re*". Attribute in added query part and '*' placement may be changed using new settings "Filter loaded data dependent on value from" and "How to filter pre-loaded data"

   

3.  Field with selected records. 

Main feature - this filter makes a new query to Elasticsearch on search instead of searching on results preloaded on filter creation. This also allow to set "Maxiumum Maximum Size of Records to retrieve" less than for selectsearch filter and increases performance.

In ACD v.3.2 select, selectsearch and selectsearchload  filters will receive additional element on the bottom of the filter containing information about total amount of records matching filter`s Search queryQuerystring, Max Limit, number of loaded records and unique records shown in filter (if "Make Unique Values" is checked in settings). 

...

Value to Filter the Attribute

Leave it blank for none hidden filters!  May contain regexp to filter values. Example: regexp /1|3/ will leave only records where attribute value is either 1 or 3.

Querystring

Enter a querystring if you want to make a preselection of all attribute values that are available in the filter. e.g. In a user report you only want to select users that are in a subcontainers of ou=users,o=data, you can enter the following query in a filter of the attribute parent:

...

Add the same attribute name as in field Attribute to Filter on. (in simple cases)

*  contain attribute which value will be set as "Key" of selected option and used as value in resulting report query.

Query Valueattribute

Add the same attribute name as in field Attribute to Filter on.(in simple cases)

*  contain attribute which value will be set as "Value" of selected option and displayed to user.

Image Added - nrfRequest report is based on objects with objectClass:nrfRequest. This objects have attribures like nrfRequester, nrfTargetDN and nrfApprovalInfo(in custom case of Scwarz Group) which contain a DN of Users. To implement such a report and filter reports using Surname and givenName all three settings Attribute to Filter on, Query keyattribute and Query Valueattribute must contain different values.

In example "Approver 2 Given Name" filter have 

1. Attribute to Filter on: nrfApprovalInfo, 
2. Query keyattribute: dn, 
3. Query Valueattribute: givenName 
4. Querystring: "objectClass: inetOrgPerson AND givenName:*" - Users who have givenName.

Selected value is "Yann" which is a givenName. And on the bottom of the filter displayed selected key -it is "cn=ysommer,ou=users,o=data".

Accordingly on report creation ACD will send a query containing  Must statement with attribute name from Attribute to Filter on  {"query_string":{"query": "nrfApprovalInfo: (\"cn=ysommer,ou=users,o=data\")"}}

Make Unique Values

Check this box in most cases. If there are multiple similar values for the selected attribute, it only shows the value once.

...