Difference between revisions of "Record Page"
Ann Vincent (talk | contribs) m |
Ann Vincent (talk | contribs) m |
||
| Line 4: | Line 4: | ||
=Overview= | =Overview= | ||
| − | Record pages allow you to view the details of an individual item in an application. They contain both | + | Record pages allow you to view the details of an individual item in an application. They contain both the [[Standard Field|standard fields]] and [[Custom Fields – General Information|custom fields]]. Record pages can exist for [[Organization|organizations]], users, and [[Level 1 Entity|Level 1 entities]]. From the record page, you can perform actions on the record such as edit fields, change the status, add it to a [[SmartCard]], attach notes, assign contacts and accounts, and associate it with a Level 2 Activity. |
=Configuration - Essentials= | =Configuration - Essentials= | ||
Revision as of 15:26, 13 July 2021
 Please note that this page is currently under construction. There is more information to come.
|
Contents
Overview
Record pages allow you to view the details of an individual item in an application. They contain both the standard fields and custom fields. Record pages can exist for organizations, users, and Level 1 entities. From the record page, you can perform actions on the record such as edit fields, change the status, add it to a SmartCard, attach notes, assign contacts and accounts, and associate it with a Level 2 Activity.
Configuration - Essentials
When a new record is added to an application, the record page asks for the user to submit information to various standard and custom fields. While the standard fields are pre-defined by the system’s default settings, the custom fields can be created and managed by the Global Administrator. Each unique application will require unique custom fields depending on what is being tracked and what actions are required.
| # | Component Name |
|---|---|
| 1 | Header Contains: logo, Main menu items, header button group |
| 2 | Action Bar Contains: History button group and Action bar button group, Pagination control |
| 3 |
Action Bar Button Group |
| 4 |
Title Area |
| 5 |
High Visibility Options |
| 6 |
Hierarchical Navigation Bar |
| 7 |
Body |
| 8 |
Tab Area |
| 9 |
Left Navigation |
| 10 |
Submit Bar |
| 11 |
Tab Bar |
The body area of the Records page contains all your custom fields.
To set up custom fields for all the records in your application, navigate to Configuration Settings > (Level 1) tab > General Settings section > Custom Fields. Configuration settings for each application is located in the gear icon in the action bar.
To set up custom fields for organizations, navigate to Global Settings > Organizations tab > General Settings section > Custom Fields.
To set up custom fields for users, navigate to Global Settings > Users tab > General Settings section > Custom Fields.
Setting Up Custom Fields
Main Article: Custom Fields – General Information
[image goes here]
For a simple application, when creating a new custom field, you can select from a predefined list of field types depending on the end use. For example, a record containing a simple field for “About” can have the field type Text Box - Multiple Lines. A field for “Shipping Address” could have the type Special - Geo Mapping. See Category: Custom Field Types for full list of available field types to choose from, including dropdowns, radio buttons, checkboxes, date pickers, and more.
Once you select the appropriate field type, you can also give the custom field a name in the database (Field Name) and a display name that will be visible to users (Caption). The Display Order determines where in the form this custom field appears. The higher the number, the closer to the top of the form the field appears. A Description is not mandatory and will only be visible to Global Administrators, however filling out a simple description for each custom field will make it easier to track changes and remember what each field is for.
In the Permissions & Availability tab, you can further customize who can access the custom field and when. This allows you to tailor access to the custom field to a certain user role, a type category, or when a certain status change has been triggered.
Configuration - Advanced
Submit & Save Buttons
Main Article: Submit & Save Buttons
Submit & Save buttons are used to perform custom actions upon each record such as saving a record, changing the status, validate input, or add annotations. Like custom fields, submit and save buttons can also be customized to be active only for certain roles, statuses, or record categories. To access the settings of any individual custom field, navigate to the following:
UTA - Configuration Settings > (Level 1) tab > General Settings section > Submit & Save Buttons
Organization - Global Settings > Organizations tab > General Settings section > Submit & Save Buttons
Users - Global Settings > Users tab > General Settings section > Submit & Save Buttons
Record Layout Custom Fields
Main Articles: Custom Field Type: Layout - Title Bar, Custom Field Type: Layout - Tabbed Section
Title Bars and Tabbed Sections help organize your records page by grouping together similar custom fields. A title bar separates related content on the same records page. A tabbed section moves blocks of related content onto a separate tab. The placement of custom fields can be controlled through the Display Order.
Settings Explained
To access the settings of any individual custom field, navigate to the following:
UTA - Configuration Settings > (Level 1) tab > General Settings section > Custom Fields
Organization - Global Settings > Organizations tab > General Settings section > Custom Fields
Users - Global Settings > Users tab > General Settings section > Custom Fields
Display Text
The Display Text options help you determine how the custom field should be displayed to the user. Caption Location allows you to put the field label name either above, to the right, or the left of the input as well as hiding it altogether. You can also add additional instructions to display to the user if desired. Placeholder text will be greyed out text that pre-populates the input field. This can be useful to showing examples or hinting at the desired input format. Additionally, you also have the ability to add tooltip text. Filling out this section with helpful contextual information will make a small question mark icon appear to the right of the input form. When the user hovers over this icon, you tooltip text will appear.
Validation
Options within the validation section allow you to mark this custom field as mandatory or add custom validation to ensure the user’s input follows certain parameters. For example, a date of birth custom field may have additional custom validation to ensure the user’s input is a date that is in the past or is limited to a certain range of years. You can also choose what message to display to the user if they fail this validation check.
Feature Options
This section contains any additional features that can be enabled on the custom field. These features vary depending on the custom field type. For example, the Text Box - Single Line and Text Box - Multiple Lines contains a feature option for enabling hashtags as part of the user input.
Value Storage
SmartFields
Main Article: SmartField View
This section allows you to specify whether the custom field should be included in generated reports or system summaries.
Visibility Condition
Main Article: Visibility Condition
This section allows you to use additional logical statements to determine whether or not a field is visible. Common visibility condition statements are based on roles, types, statuses, and even field values.Bold text
