Skip to content

Commit 9929f98

Browse files
docs: preferredSearchOperator and blockedSearchOperators
1 parent 73104b6 commit 9929f98

File tree

2 files changed

+5
-1
lines changed

2 files changed

+5
-1
lines changed
240 KB
Loading

docs/user/using-the-capture-app.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -646,10 +646,14 @@ The Capture app supports the workinglists in tracker programs, but when you open
646646

647647
![](resources/images/search-by-attributes-find-button.png)
648648

649-
These steps will take you to the search page. There, based on the configuration of your organisation, will see the different attributes you can search with. An example of how this looks is the following.
649+
These steps will take you to the search page. There, based on the configuration of your organisation, will see the different attributes you can search with. An example of how this looks is the following.
650650

651651
![](resources/images/search-by-attributes-on-scope-program-overview-0.png)
652652

653+
To enhance search performance, you can configure the **preferredSearchOperator** or **blockedSearchOperators** metadata in Maintenance. Tracked entity attributes with the following value types apply these settings: TEXT, LONG_TEXT, EMAIL, PHONE_NUMBER, PERCENTAGE, ORGANISATION_UNIT, and USERNAME. If preferredSearchOperator is not defined, the search falls back to the first available operator in [LIKE, SW, EQ] that is not listed in blockedSearchOperators. Attributes with other value types ignore the preferredSearchOperator. Helper text messages are displayed below the attribute search fields to guide the user.
654+
655+
![](resources/images/search-by-attributes-on-scope-program-preferredSearchOperator.png)
656+
653657
To execute a search now:
654658

655659
1. Fill in the attributes you want to search with.

0 commit comments

Comments
 (0)