Use specialized form components
As mentioned previously, there are several specialized form components available for model driven apps. This unit contains more details on several of the most common ones.
A reference panel is a specialized section that can be added to main forms that offers interaction with related data in the context of the hosting table row. It can contain subgrids of related tables and display related data without having to navigate to a different form. To get the full value of a reference panel, you must also have Quick View forms configured. Each form can only have a single reference panel, but each reference panel can contain multiple subgrids.
Drilling into the right side, you will notice two icons, one for each of our subgrids configured for this reference panel. You can toggle between them as you need to view rows.
Drilling into the left side, you will notice the tabs behind the grid. Those are the recently viewed rows for this table on our reference panel.
While viewing individual rows, you will see the Quick View form for the table. All columns from a Quick View form are displayed as read-only.
Bing Maps can be displayed on a form for the account, contact, lead, quote, order, invoice, competitor, and system user tables. You can remove the Bing Maps area in the form editor or add it back by using the Bing Maps button on the Insert tab of the form editor.
Use a timer control with forms where rows need to meet a specific time-based milestone. A timer control shows how much time is available to complete an action in the resolution of an active row or how much time has passed since the time to complete the action has passed. At a minimum, timer controls must be configured to show success or failure in completing the action. In addition, they can be configured to display warnings when the conditions are approaching failure.
A timer control can be added to a form for any table, but they are most frequently used for the case table, especially when linked to columns that track service level agreements. You can add multiple timer controls in the body of a form. You can’t add them to the header or footer.
Quick view control
A quick view control on a model-driven app form displays data from a row that is selected in a lookup on the form. The data displayed in the control is defined using a quick view form. The data displayed is not editable, but when the primary column is included in the quick view form, it becomes a link to open the related row.
You can add iFrames to a form to integrate content from another website within a form.
The Timeline control provides a combined place to view customer interactions including activities and notes all in one location. The timeline quickly allows you to see when the interaction occurred and what is new since last visit to the row. Using filters users can quickly trim down what is visible. The control properties allow you to change things like what the default create row type is, and what activities show in the timeline.
Previously, we provided an overview of custom controls; now we are going to look deeper into configuring them on a form. The controls available are determined by the column data type. It must be bound to a column on the form, in this case for a Contact it is bound to the contact row’s last name.
Applications such as LinkedIn Sales Navigator have widgets available for use on forms in the same manner. This item below has several configuration options.
Editable subgrids can be added to forms in much the same way that other custom controls can be added. Details about editable subgrids can be found later in this module.
Inline editing and grouping is now available on the host form.