Supporting Layouts in Vault CRM
Layouts control how records for each object display to users. Each layout is associated with an object type. Admin users can create and manage layouts for different objects to ensure the appropriate layouts display for the appropriate end users. See Configuring Object Layouts for more information about creating and managing layouts. Vault CRM supports a subset of the available functionality for object layouts in Vault.
Who can use this feature?
- Browser, iPad, iPhone Users
- Users do not require an additional license
- End Users
Supporting Functionality for Layouts for
End Users
The table below outlines which layout functionality is and is not supported in Vault CRM:
|
Functionality |
Description |
Supported in Vault CRM? |
|---|---|---|
|
Layout profiles |
Define sets of users with access to specific object layouts, providing greater flexibility for customers to control layouts for the same object type for different groups of users according to business needs. See Configuring Layout Profiles for more information. Vault CRM only supports defining one layout per object type in a layout profile. |
|
|
Field controls |
Displays as a field with specific behavior or enables specific behavior within a detail form section |
|
| Section controls |
Displays as a section with specific behavior or enables specific behavior on the page |
|
|
Section attributes |
Markers used to configure the specific behavior of a section control |
|
|
Required and read-only fields |
Indicate if a field in a layout is required or read-only. Required fields must be populated to save the record. Read-only fields cannot be edited. |
|
|
Layout rules |
Dynamically hide irrelevant fields, sections, pages, and layouts on a record based on business needs. See Configuring Layout Rules for more information. |
|
|
Pages |
Organize sections into separate pages on a layout |
|
|
Text sections |
Add text fields as sections on a layout |
|
|
Help sections |
Display help content to end users in a separate section |
|
|
Detail form sections |
Displays labels and values for selected object fields. Can contain help sections to inform and instruct users. |
|
|
Related object sections |
Allow users to view and create records for related objects |
|
|
Related documents sections |
Allow end users to add and view related documents |
|
|
Showing sections based on lifecycle state |
Associate a layout with a specific state in a lifecycle to display specific information related to that state |
|
|
Switching layouts when viewing a record |
Switch between layouts when viewing a record for an object type with multiple layouts |
|
Required and Read-Only Fields for Call Reporting on Browser
For call reporting on the Browser platform, required and read-only field functionality at the layout level is supported as follows:
- The call_channel__v field on the call2__v object can be marked as read-only on call2__v layouts
- The following fields on the call2__v object can be marked as required or read-only on call2__v layouts:
- account_plan__v
- Any custom fields
- The following fields on the call2_discussion__v and medical_discussion__v objects can be marked as required on call2__v layouts:
- account_tactic__v
- product__v
- product_strategy__v
- medical event__v (medical_discussion__v object only)
Required and read-only functionality is not supported for Unique Activities group calls on Browser.
