Configurable Screens > Using Configurable Screens
  
Using Configurable Screens
This section describes using Configurable Screens in the QAD .NET UI.
QAD provides a design tool for configuring selected screens. The design tool lets users in a designated UI design group disable fields for input, hide fields, set a predefined default value for a field, mark a field as required, add fields and frames, and indicate that navigation through a frame should occur automatically. By combining these features, designers can create a screen sequence that greatly streamlines data input for users.
Screen definitions are stored as UI templates, which can be assigned to user groups so that the screen appearance and behavior can vary based on the user’s role within an organization. Tools are provided so that administrators can resolve any conflicts that occur regarding screen assignment when a user belongs to more than one user group.
Configuring screens enables you to help the individuals in your company get their jobs done quicker and more effectively. By eliminating fields that are not used at your site, you can also reduce training time and potential data input errors. However, you must have a very clear understanding of how a particular function is being used before you change the data input requirements. Because of the inherent flexibility of the software, each company that implements a particular function may use different features. This can affect which fields are required and which are optional.
The following are a few examples of how this can occur:
Example: Generalized codes validation. Many programs support the use of generalized codes. If codes have been defined for a field in Generalized Codes Maintenance (36.2.13), built-in validation results in an error when the field is left blank. However, if no codes are defined, the field can be left blank and an error is not generated. Hiding a validated field without providing a valid default value creates a problem in the first scenario but not in the second.
Example: Optional modules. The behavior of some programs is affected by the implementation of optional related modules. For example, different fields and pop-ups display in Sales Order Maintenance depending on whether you are using available-to-promise features, Enterprise Material Transfer, or updating the Service/Support Management installed base. In addition, Container and Line Charges, Customer Consignment Inventory, and Logistics Accounting affect sales orders.
Example: Control settings. Settings in control programs can determine whether a field is required or even whether it displays on the interface. For example, the Invoice From Recording setting in Call Management Control determines if certain fields display in the last frame of Call Activity Recording (11.1.1.13).
These examples highlight that you must take care in planning the changes you want to implement. You must also thoroughly test the templates you create before using them in a production environment.
Note: The Configurable Screens function is available for non-component-based screens only. You can customize component-based screens using component-based Design Mode. See User Guide: QAD Financials for a description of this function.