Versions Compared

Old Version 1

changes.mady.by.user Seth Petry-Johnson

Saved on

compared with

New Version 2

changes.mady.by.user Seth Petry-Johnson

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Info
titleSummary

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

Related Content

Child pages (Children Display)


Info
titleTerminology

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. 

Technically speaking, a "queue" is just a "search" page with a default filter that does something meaningful.