Module 9: Form Patterns

Justification:

1. True: The statement is true. Form patterns are applied on the form’s design node and sub-patterns are applied to specific controls within the form. The form pattern impacts the layout of the entire form, while the sub-pattern impacts a specific part, such as a tab page or group control.

Related Lesson: Form Patterns and Sub-patterns

Justification:

1. A simple list form pattern is typically used to display a list of data for a simple entity, where there is often less than ten fields. An example of this would be the Customer Group form.
2. The details master form pattern is commonly used for displaying the data of a complex entity, such as a customer.
3. The Operational Workspace form pattern requires the Panorama tab style for a horizontal arrangement; this pattern is used to display data about a specific activity.
4. The Table of Contents form pattern is commonly used for Setup pages. Setup pages use the vertical tab style, which has the tabs arranged in a sequential order on the left pane. An example of this is the Accounts Receivable parameters form.

Related Lesson: Form Patterns and Sub-patterns

Justification:

1. The form statistics dialog shows the name of the form pattern applied to that form.
2. The form statistics dialog shows the pattern coverage percentage.
3. The form statistics dialog shows the number of form controls that are covered by a pattern, including both sub-patterns and the form pattern.
4. The form statistics dialog shows the total count of controls on a given form.

Related Lesson: Form Patterns and Sub-patterns

Justification:

1. True: The statement is true. The form patterns report will output as a .csv file and can be opened in Microsoft Excel to filter and view the different details relating to forms as well as their applied patterns.

Related Lesson: Check Form Pattern

Justification:

1. A form pattern may be chosen and applied during the development process, but it is not fully applied until the form is fully compiled and saved with the chosen pattern applied.
2. Building or rebuilding the form element builds the .NET module that the element is included in; however, the pattern is not fully applied until a compile and save is performed.
3. You must first set the form you want to preview as the Startup object for the project. This can be done by right-clicking the form from the Solution Explorer and selecting “Set as startup object.” Then, you may proceed with building and running the project by pressing CTRL + F5.
4. A rebuild of the form will cause the element to be rebuilt and compiled and checked for errors; however, it will not run the form unless it is set as the startup object first.

Related Lesson: Check Form Pattern

• A. While applying a form pattern is considered best practice, it is not mandatory.
• B. Applying a form pattern is highly recommended and considered best practice when you are developing a new form, but it is not mandatory.

• A. The forms pattern report is a .csv file that lists all the forms in the system. It is not a necessary step before previewing a form.
• B. The form statistics add-in gives an overview of the controls and pattern coverage on a specific form. It is not a necessary step before previewing a form.
• C. You must first set the form you want to preview as the startup object for the project by right clicking the form in the Solution Explorer window and selecting that option.
• D. A rebuild of the form will force the elements in a project to be rebuilt and compiled. It will not run the form unless the form was already set as the startup object.