| 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 Entities
More information about this topic can be found here: /wiki/spaces/DOCS/pages/
...
Common Functionality
Member Search was implemented first and contains some special features not supported in the other cases.
...
searchFields: [...]...
Each implementation of the search framework contains a base search model that can expose information that is not represented as Workflow Attributes. These properties can be targeted by a search field.
target": "model.OwnerName"
...
To search against Workflow Attributes, use the "entity-scoped" syntax:
target": "ActivityInstance.Activity Type"
...
Each search field is given a label, and the label can be a fixed string or can be pulled from the Glossary.
"label": "Glossary.Singular(Activity)"
...
"searchType": "<value>"
ExactMatch: (default) the value in the database exactly matches value entered into search formTextboxBeginsWith: the value in the database starts with the search valueContains: the value in the database contains the search valueIncludeChildren: (Member Search only) searches against the specified Member and it's "children" in the Organization Hierarchy
...
Search values can be entered into the search form using a variety of different mechanisms.
"criteriaType": "<value>"
Textbox: (default)Picklist: renders as a dropdown list (see: TODO)MultiSelectList: renders as a multi-select listboxMemberAttribute: renders a Member Lookup attribute for choosing a specific Member
(Member Search specific)
RolePickListRoleStatusPickListMemberNameMemberType- MemberStatusPickList
MemberId
(Activity Instance Search specific)
ActivityTypeMemberKeywordDateRangeNumberRangeAutoComplete
Related Content
| Child pages (Children Display) |
|---|
| Jira Legacy | ||||||||
|---|---|---|---|---|---|---|---|---|
|
...
| 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.
...