| Info | ||
|---|---|---|
| ||
In complex installations it is often desirable to have multiple ways to view the core types of data: Members, Activities, and Learning Plans a.k.a., Applications. For example, there may be multiple contexts in which a user may need to view or search Member data, and the relevant filter criteria, result columns, and access control business rules may be different in each one. System Administrators can use advanced configuration features to create separate search screens for each scenario, without needing any custom programming in the core application. |
Supported Features
- Activity Instance Search
- Learning Plan Instance Search
- Member Search (DRAFT)
Related Content
| Child pages (Children Display) |
|---|
...
| title | Terminology |
|---|
The terms "queue" and "search" are both to describe this feature, but indicate different use cases.
A queue is a page that shows users a list of things that they should work on next. This is often used to represent things like a "review queue" where the default criteria return the list of things the user needs to worry about.
A search is a page that displays multiple search criteria fields and allows users to run ad-hoc searches.
...
More information about this topic can be found here: /wiki/spaces/DOCS/pages/3808526732