Search Features task and Work List task

Search Features task

The Search Features task provides a generic search workflow for searching features based on a combination of query criteria and in most cases should be sufficient. To implement a different query logic for a different user experience, you can create a new task or project extension.

The search result page is a feature list page. On this page, the page menu, feature list context menu, and map menu are all customizable. See the menu customization topics and the MenuCustomization extension sample for details.

Some pages and components in the search workflow are exposed and can be used for developing your own tasks or extensions. These components can be classified into two categories: lower-level worker components to build query filters, and application-level components related to the Search Features task to facilitate the user interface (UI).

The following are the lower-level worker components:

• Clause
• ClauseConnector
• Condition
• DataColumnCondition
• DateCondition
• GenericEqualsCondition
• IClausePart
• NumericCondition
• NumericRangeCondition
• Search
• SearchArea
• StringCondition
• UserDefinedCondition

The basic object model is that Search contains a number of Clauses, and Clause contains a number of parts (which are implemented as conditions). The Search class can then build and return a query filter by calling BuildQueryFilter(), which you can pass to the feature layer to get the features. See the assembly API for details about these components.

The application-level components are as follows:

• ChooseExtentPage
• ClausePartViewModel
• ClausePartViewModelEventArgs
• ClauseViewModel
• DataColumnClausePart
• DataColumnClauseViewModel
• SearchAreaClausePart
• SearchAreaClauseViewModel
• SearchCriteriaPage
• SearchEventArgs
• SearchFeaturesTask
• SearchHomePage
• SearchResultsPage
• SearchTaskViewModel
• SearchViewModel

At the application level, there are three view model classes that correspond to and wrap the Search, Clause, and Condition classes: SearchViewModel, ClauseViewModel, and ClausePartViewModel. These view model classes provide methods similar to the lower-level components but use a slightly different application programming interface (API) that is easier for the UI components and task to consume.

To build and execute searches or queries without any sort of UI, you can use the lower-level components. To modify or customize the existing Search Features task or provide your own UI, consider the application-level components.

Work List task

The Work List task is where a collection of features are stored for easy access by field-workers. For example, you can store a collection of features that need inspection by a specific field-worker on the Work List page. The Work List page is a feature list page that displays and manages the work list. On this page, the page menu, feature list context menu, and map menu are all customizable. See the menu customization topics and the MenuCustomization extension sample for details.