a list displays a set of records from a table within the content frame, each row in
a list represents one record and each column represents one field
views provide specific fields or columns to support different work activities,
enables users to quickly display the same list or form in multiple ways, sysadmins
can create views for lists or forms
to switch between the different views of columns on a list, open the list control
menu then select view and select the desired view
a list that is displayed to a user for the first time will be sorted by one of the
following:
order field
number field
name field
field specified as the display field for the table
context menus provide different levels of controls for a given list view and can be
access by selecting the list controls menu icon or by right clicking the list
header or column headers, there are 3 context menus
lis control menu
column option menu
list fields (right click) context menu
list collector add, remove or reoder fields, available items that are green and
followed by a + represent related tables and can be used dot walking to gather
information from a table, you cannot use dot walking using a form design, only form
layout
a filter is a set of conditions applied to a table list to isolate a subset of the
data and the components that make up a filter condition include
field
operator
value
filter conditions applied to the list are summarized in the breadcrumbs shown in
blue letters across the top of the list
field operators can be text value, numeric value or date value
list editor allous a field value to be edited in a list without opening the record
and can be contiguous and non contiguous (you can make edits to values that belong
to different records at the same time)
list editing is disabled or restricted for some tables
users with admin or personalize_list role can add or remove columns from a list
actions in the gear icon only personalize to the logged user
where the list layout configuration affects everyoen, the personalize list modifies
the layout of a list for an individual user
personalization should be used for a temporary situation, any global changes that
occur at the system level will not be reflected in a personalized list, if the
sysadmin configures a list view a user has personalized, they will no see those
newly added default changes
dot walking gathers information from a series of tables through reference fields
and can be used in places such as form layout, list views, reports and flow
designer
a list display a set of records from a table
list categories group records that agents need to do their work, workspace provides
many list categories but a sysadmin might create additional categories as needed
list categories appear in the list pane but they do not retrieve records when you
click them, the filtered lists under the categories do retrieve records, when
creating a list category you need must add a list filters od the category doesnt
appear
tables are a data structure or a database component which contain records
records are the data stored in the tables which contain fields
fields are individual pieces of data within a record
applications use tables and records to manage data and processes
the system dictionary contains the definition for every field from all tables
when a new record is created, the form view will be the same as the list view
its not recommended to add the same field to more than one section of a form unless
the field displays read only data, having two or more instances of an editable
field can cause data loss
form design works on classic forms and workspaces, however you will need to select
the appropriate application before opening form design
if you try to modify a form in form design and it turns pink, you are not in the
correct application
formatter is an element used to display information that is not a field in the
record
some formatters included in the base platform are
activity
process flow
parent breadcrumbs
approval summarizer
CI relations
related lists show records in tables that have a relationship to the current record
templates allow form fields to be populated automatically
templates creation should be restricted to select groups as it can be used to
bypass process
the governance on services and service offerings is critical, service owners should
provide service names to admins
true/false field displays as a check box on the form
dependent fields limits a fields available value
business services is used to auto assign groups to a record
