List Administration

Administrators can control the sort sequence, allow personal lists, restrict filters and breadcrumbs, allow context ranking and more.

Users can customize the layout for any list view by personalizing a list. Administrators can configure options related to list personalization.

You can write scripts to specify which list elements, such as links, filters, and buttons, are present.

All lists have a default sort sequence based on the type of fields present in the list.

Users with the appropriate roles can configure various aspects of lists. Configuration changes apply to all users.

You can add a property to allow for a larger number of breadcrumb entries in the filter.

Speed up how fast lists load by removing the calculation of the total number of records in a list.

Administrators control the data presented to end users in a list, the controls that appear, and the behavior of the controls.

The Action script field, on the Context Menu form, defines a script. The script runs when someone selects the context menu option.

The list editor allows users to edit field values directly from a list without navigating to a form.

The list editor enforces existing access control rules (ACLs) and additional security controls to restrict editing from a list.

Context ranking allows a user to sort a collection of records preferentially; that is, independently of the attributes of those records.

The Dynamic actions script field, on the Context Menu form, defines a script. The script populates a list context menu with dynamic options, such as filters or views.

This access control prevents everyone except an administrator from editing the Short Description field of an incident record in a list.

This access control prevents everyone from editing an incident with a category of Software in a list. It is defined by a script.

This access control prevents everyone from editing all fields in the Incident table in a list.

This access control prevents everyone from editing a Critical Incident in a list. It is defined by a condition.

Users can set user preferences for list editing by personalizing a list (available when the list mechanic is activated).

The onShow script field defines a script that runs before the context menu is displayed to determine which options appear in the context menu.

Ranking definitions for user stories are part of the SDLC (scrum process) application.

The Show/hide filter used in the list configuration, lists the fields to configure in the filter conditions.

If you have the admin role, you can activate the Context Ranking plugin (com.glide.sorting). This plugin activates related plugins if they are not already active.

You can enable or disable personal lists through the UI Macros module.

You can apply a new sort order to the records in a list.

You can configure the list control settings that affect the list editor.

You can configure list calculations for columns, which calculate column totals, minimums, maximums, and averages.

You can configure list controls, such as buttons and filters.

Configure list editor properties that control whether lists can be edited and, in List v2, which field types cannot be edited.

You can configure a list to choose which columns appear in a list, create list views, and create fields on the table.

You can control who can create personal lists.

You can customize the content and behavior of list context menus.

Enable context ranking for a related list by creating a ranking definition.

You can enable hierarchical lists to make data from related lists directly accessible from within a list.

Detail rows provide additional information about records in a list.

Administrators can manage personal lists.

After you create a ranking definition for a table, related lists based on that table and context include options for ranking the list and displaying the list by rank.

The Context Ranking feature enables all scrum users to manually sort a related list of stories by priority.

The record list view allows users to navigate to different subsets of a table using breadcrumbs and filters. You can limit access to parts of the table by restricting active links in breadcrumbs or by suppressing breadcrumbs and filters for specific roles.

By default, no related list tabs are visible in a hierarchical list and only a single related list is displayed at a time. The column headers are hidden by default.

Use list controls to suppress filters and breadcrumbs on defined tables for users with specific roles.

You can use a script to restrict filters and breadcrumbs to specific roles, either on a per-table or global basis. Using a script is an advanced option that offers additional flexibility compared to using list control.