User Guide: QAD .NET User Interface - QAD.com

User Guide 

QAD .NET User Interface 

QAD .NET User Interface Overview 

Using Programs in QAD .NET UI 

Simplifying HTML Screens 

Using the Process Editor 

Configuring Administrative Settings 

78-0663A 

QAD .NET UI 2.1 

March 2007

This document contains proprietary information that is protected by copyright and other 

intellectual property laws. No part of this document may be reproduced, translated, or modified 

without the prior written consent of QAD Inc. The information contained in this document is 

subject to change without notice. 

QAD Inc. provides this material as is and makes no warranty of any kind, expressed or 

implied, including, but not limited to, the implied warranties of merchantability and fitness for a 

particular purpose. QAD Inc. shall not be liable for errors contained herein or for incidental or 

consequential damages (including lost profits) in connection with the furnishing, performance, 

or use of this material whether based on warranty, contract, or other legal theory. 

QAD and MFG/PRO are registered trademarks of QAD Inc. The QAD logo is a trademark of 

QAD Inc. 

Designations used by other companies to distinguish their products are often claimed as 

trademarks. In this document, the product names appear in initial capital or all capital letters. 

Contact the appropriate companies for more information regarding trademarks and 

registration. 

Copyright © 2007 by QAD Inc. 

QAD Inc. 

6450 Via Real 

Carpinteria, California 93013 

Phone (805) 684-6614 

Fax (805) 684-1890 

http://www.qad.com

Contents 

About This Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 

Other Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 

Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 

QAD Web Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 

Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 

Chapter 1 QAD .NET User Interface Overview . . . . . . . . . . . . . . . . . 5 

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 

Features of QAD .NET UI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 

Configurable Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 

QAD .NET UI Main Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 

QAD .NET UI Functional Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 

File Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 

Edit Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 

Tools Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 

Workspace Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 

Window Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 

Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 

QAD .NET Keyboard Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 

Application Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 

Using Menu Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 

Favorites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 

Adding Menus to Favorites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 

Organizing Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

iv User Guide — QAD .NET User Interface 

Menu Search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 

Application Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 

Chapter 2 Using Programs in QAD .NET UI . . . . . . . . . . . . . . . . . . 33 

Using QAD .NET UI Browses and Lookups . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 

Navigating in Browses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 

Column Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 

Grouping Data in Browses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 

Creating Excel Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 

Accessing Links in Browses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 

Searching in Browses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 

Saved Session Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 

Using Browse Charting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 

Using Browse Collections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 

Using Product Structure Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 

Using HTML Maintenance Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 

Sample HTML Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 

Entering Data in HTML Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 

Using HTML Calendars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 

Using the Actions and Go To Menus in HTML Screens . . . . . . . . . . . . 62 

Sending URL Links in E-Mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 

Understanding HTML Program Overlay Frames . . . . . . . . . . . . . . . . . 67 

Working with HTML Program Selection Lists . . . . . . . . . . . . . . . . . . . 68 

Navigating HTML Screens with the Keyboard . . . . . . . . . . . . . . . . . . . 71 

Understanding Messages in HTML Screens . . . . . . . . . . . . . . . . . . . . . 72 

Using HTML Reports and Inquiries . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 

Using Character Terminal Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 

Requesting Application Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 

Creating Custom Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 

Using Special UI Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 

Using Browse Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 

Using Fixed Assets Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 

Transaction Comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Contents v 

Chapter 3 Simplifying HTML Screens . . . . . . . . . . . . . . . . . . . . . . . 87 

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 

Planning Template Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 

Error Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 

Assigning Templates to Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 

Administering Simplified Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 

Simplified Screens Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 

UI Template Conflicts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 

Impact of MFG/PRO Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 

Creating a UI Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 

Creating a Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 

Simplifying Program Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 

Chapter 4 Using the Process Editor. . . . . . . . . . . . . . . . . . . . . . . . 105 

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 

Scalable Vector Graphics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 

Sample Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 

Managing Process Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 

Getting Started with the Process Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 

Using Process Editor Context Menus . . . . . . . . . . . . . . . . . . . . . . . . . 110 

Using Process Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 

Associating URLs with Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 

Using Property Editors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 

Process Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 

Grid Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 

Style Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 

Node Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 

Connector Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 

Process Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 

Accessing Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 

Administering the Process Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 

Configuring Context Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 

Configuring Process Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

vi User Guide — QAD .NET User Interface 

Chapter 5 Configuring Administrative Settings . . . . . . . . . . . . . . 133 

Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 

Defining User Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 

Defining Browse URL Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 

Defining URLs to External Web Pages . . . . . . . . . . . . . . . . . . . . . . . . 138 

Defining Links to Other MFG/PRO Programs . . . . . . . . . . . . . . . . . . 139 

Using Browse URL Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 

Monitoring User Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 

Defining Program Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 

Adding Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 

Program Information Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 

Report Format Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 

Displaying Company Logo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 

Removing Report Footer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 

Setting Default Browser Text Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 

Setting Different Colors for Alternate Rows . . . . . . . . . . . . . . . . . . . . 149 

Setting Report Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 

Excluding Some Reports from New Format . . . . . . . . . . . . . . . . . . . . 150 

Glossary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 

Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Other Documentation 2 

Online Help 2 

QAD Web Site 2 

Conventions 3 

About This Guide

2 User Guide — QAD .NET User Interface 

This guide covers features of the QAD .NET user interface (UI) for 

MFG/PRO eB2.1. It discusses using QAD .NET UI features such as 

browses and menus; using MFG/PRO functions in the QAD .NET UI; 

using administrative tools to simplify screens; and configuring optional 

settings. 

Information about other setup tasks is included in Installation Guide: 

QAD User Interfaces. 

Other Documentation 

For details about installing and configuring the QAD .NET UI software, 

see Installation Guide: QAD User Interfaces. 

For a list of all documents, see the documentation portion of the QAD 

Support Web site. 

Online Help 

You can access an online version of the information in this guide while 

using the QAD .NET UI. The QAD .NET UI also supports the help 

functions provided by the QAD applications that are executing. See 

“Requesting Application Help” on page 76 for details on help features. 

QAD Web Site 

The QAD Web site provides a wide variety of information about the 

company and its products. You can access the Web site at: 

http://www.qad.com 

For MFG/PRO users with a QAD Web account, product documentation is 

available for viewing or downloading at: 

http://support.qad.com/

You can register for a QAD Web account by accessing the Web site and 

clicking the Accounts link at the top of the screen. Your customer ID 

number is required. Access to certain areas is dependent on the type of 

agreement you have with QAD. 

Most user documentation is available in two formats: 

• Portable document format (PDF). PDF files can be downloaded from 

the QAD Web site to your computer. You can view them with the free 

Adobe Acrobat Reader. A link for downloading this program is also 

available on the QAD Web site. 

• HTML. You can view user documentation through your Web browser. 

The documents include search tools for easily locating topics of 

interest. 

Features also include an online solution database to help MFG/PRO users 

answer questions about setting up and using the product. Additionally, the 

QAD Web site has information about training classes and other services 

that can help you learn about MFG/PRO. 

Conventions 

This document uses the text or typographic conventions listed in the 

following table. 

If you see: It means: 

monospaced text A command or file name. 

italicized A variable name for a value you enter as part of an operating 

monospaced text system command; for example, YourCDROMDir. 

indented 

A long command that you enter as one line, although it 

command line appears in the text as two lines. 

Note Alerts the reader to exceptions or special conditions. 

Important Alerts the reader to critical information. 

Warning Used in situations where you can overwrite or corrupt data, 

unless you follow the instructions. 

About This Guide 3

4 User Guide — QAD .NET User Interface

Chapter 1 

QAD .NET User 

Interface Overview 

The following topics introduce the QAD .NET User Interface (UI) and 

illustrate its key features. 

Introduction 6 

QAD .NET UI Functional Menus 10 

Application Menus 20 

Favorites 23 

Menu Search 25 

Application Area 28


Introduction 

QAD products are designed for many types of users with a wide variety of 

UI needs: users in the back office need UIs that help them process 

electronic paperwork efficiently; users in the front office want dashboard 

views of data; and planners for the shop floor need UIs that let them see 

how best to juggle tasks and machine assignments. 

To support these needs, a UI needs to have the following qualities: 

Usability. The UI should enable users to do their jobs quickly and 

effectively through a consistent and intuitive model that is convenient 

and complete. 

Flexibility. Since a single UI cannot anticipate and match each 

individual user’s needs, UI elements need to be easily adjusted for 

each user or group of users who share a similar role and who do a 

similar set of tasks. 

Performance. A UI should let users do their jobs quickly and 

efficiently. 

Ease of deployment and update. Because UI software must often 

reside on each client machine, deployment of updates can represent a 

major effort for customers. This process needs to be as smooth and 

non-invasive as possible. 

The QAD .NET UI provides a common framework for multiple QAD 

applications. This framework—based on Microsoft .NET technology— 

has excellent performance and provides best-practice usability and 

deployment features, as well as extensive ways for users to adapt the UI 

to their preferred work style. 

Since the UI is based on Microsoft .NET technology, it incorporates 

familiar UI metaphors, reducing the need for users to learn how to 

navigate QAD applications.

Features of QAD .NET UI 

Using QAD .NET UI, you can: 

• Have multiple workspaces open simultaneously and multiple 

programs in any specific application open at the same time. 

• Quickly rearrange windows within a workspace to best facilitate 

tasks. 

• Use an enhanced menu system that: 

• Provides full search capability 

• Displays menus of all applications running in the UI 

• Displays only those menu choices that a user has security access 

to execute 

• Supports a user-defined menu that applies across applications 

QAD .NET User Interface Overview 7 

• Create your own menus by dragging standard menus to your 

Favorites so that frequently performed tasks are organized for ease of 

access. 

• Display MFG/PRO records using enhanced browses that feature: 

• Drag-and-drop arrangements of columns that can be hidden and 

resized 

• Single-click column sort 

• Simple searches for matched strings in a specific column or 

advanced search that lets you build complex queries, including 

discontinuous range searches 

• Custom views based on user-defined data groups 

• Drill-down and linking 

• Save browse search criteria for later reuse. 

• Output browse data directly to Microsoft Excel, print to an output 

device, or view data in a print preview mode. 

• Simplify a subset of HTML program screens, hiding fields and entire 

frames, supplying default values, and making fields display only.


Configurable Interface 

Many aspects of the QAD .NET UI can be tailored and adapted for 

specific users and environments. The following are a few examples: 

• Browses can be configured to display information in a predefined 

order and to include or exclude columns; these settings are then saved 

for future use. This is discussed in “Using QAD .NET UI Browses 

and Lookups” on page 34. 

• Browse colors and fonts can be personalized by each user, described 

in “MFG/PRO Options” on page 15. 

• Screens can be simplified by hiding or disabling fields, defining 

default values, defining required fields, and automatically skipping 

entire frames. These activities are described in Chapter 3, 

“Simplifying HTML Screens,” on page 87. 

• Users can create their own personal Favorites menu of frequently 

used programs. These menus can be renamed and rearranged in any 

way the user wants. See “Favorites” on page 23. 

• Users can add links so they can easily access one program from 

another, as described in “Creating Custom Links” on page 78. 

• Links to external URLs, to MFG/PRO programs, and to drill-downs 

can be embedded in browses so that users can easily access supplier 

or customer Web sites, other MFG/PRO programs, or more detailed 

browse views for additional information, as described in “Accessing 

Links in Browses” on page 42. 

• Users can decide for each program whether it runs in an HTML UI or 

in a character UI; see “Menu Properties” on page 22. 

QAD .NET UI Main Page 

When you start the application, you are prompted for your user ID and 

password. Optionally, you can choose from a list of supported languages. 

MFG/PRO security is checked when you log in the same way it is 

checked in other interfaces. When security has been defined in Menu 

Security Maintenance (36.3.10), you can see only the menu items you 

have access to.

Click Options to select from available languages. 

Note If you have multiple Desktop systems available, you can optionally 

select from a list of systems during log in. See “Display System Selection 

List” on page 16 for details. 

After you complete the log-in screen, the QAD .NET UI main page 

displays. 

3 

5 

4 

1 

Vertical resize bar 

Horizontal resize bar 

After you log in, the status message area briefly displays the date and time 

of your previous log-in, along with your user name and user ID. For 

example: 

Last logon: 06/07/05 16:35:02 (Jane Smith,"jas") 


Select the system you want to use. 

2 

Logged in user ID 

Fig. 1.1 

QAD .NET UI 

Login 

Fig. 1.2 


Main Page


Fig. 1.3 

.NET UI File Menu 

Note The date is in the format YY/MM/DD: for example, March 5, 2007, 

would be 07/03/05. 

The key elements of the main page are: 

1 A set of QAD .NET UI functional menus—File, Edit, Tools, 

Workspace, Window—that let you operate within the QAD .NET UI 

Note The Workspace menu displays only when the logged in user 

has access to more than one workspace. 

2 An application area for running QAD applications 

3 A search function for finding application menu items to execute 

4 An application menu area 

5 The Favorites area for your custom menu structure as you choose to 

design it 

You can resize the menu area and application area by using the vertical 

resize bar and dragging it to the right or left. You can also resize the 

Application menu area and the Favorites area by dragging the horizontal 

resize bar up or down. 

Note The ID of the currently logged in user displays in the bottom right 

corner of the screen. 

Each of the screen areas is discussed in detail in the following sections. 

QAD .NET UI Functional Menus 

File Menu 

Program history

The File menu commands include: 


Logoff/Login. Log off from all applications running in the QAD .NET 

UI. After you log off, this command changes to Login. This lets you 

log in as another user without closing the QAD .NET UI. 

Note To close the QAD .NET UI, use Exit, not Logoff. 

Page Setup. Define page settings for print output, such as margins 

and orientation. 

Print Preview. Generate a preview of browse data or the active HTML 

screen so that you can verify that it is correct and make adjustments 

before printing. 

Print. Open the print dialog so that you can print the data for a browse 

or the screen for other programs. 

You can also access print from the Print icon in browses. See “Using 

QAD .NET UI Browses and Lookups” on page 34. 

Program History. Display the last six programs that you have opened. 

Exit. Close the QAD .NET UI and log off any open applications. 

Edit Menu 

The Edit menu commands include: 

Cut. Place selected text on the clipboard and remove it from the 

current location. 

Copy. Place selected text on the clipboard and leave it where it is 

currently located. 

Paste. Place the contents of the clipboard in the current cursor 

location. 

Menu Search. Activate the Menu Search bar so you can search for a 

program to execute. See “Menu Search” on page 25 for details on 

searching.


Tools Menu 

The Tools menu commands include: 

Options. View administrative information and set personal options for 

browses and other application settings. 

Internet Properties. Update the same settings that display when you 

select Internet Options from the Tools menu in Internet Explorer. See 

the help provided with Internet Explorer for details about how these 

options are set. 

Manage Workspaces. Activate and deactivate workspaces from a list 

and reorder them. 

System Info. Display information about the version of QAD .NET UI 

that is running, the time the QAD .NET UI was started, and the total 

amount of physical memory the QAD .NET UI is using. (If N/A is 

displayed, operating system is not giving the QAD .NET UI 

permission to access system information.) View log information by 

clicking on View Log: the log file opens in the text editor associated 

with files ending in the “.log” extension on your system. 

Administration Options 

Choose Tools|Options, click Administration, and expand the various 

options to view and modify administration settings. A brief description of 

the setting displays in the help area at the bottom of the screen.

On-screen help 

This screen can be used for viewing and modifying settings related to 

logging, navigation, the MFG/PRO plug-in, and automatic updates. 

The Logging section displays details set during installation that can be 

modified if needed. 

Log Level. Indicate the threshold for limiting the type of information 

logged. Values are off, debug, information, warning, and error. The 

Debug setting records the most details and the error setting records 

the least. 

Maximum File Size. Specify the maximum number of kilobytes that 

can be written to the log file before it is backed up. 

Number of Backups. Specify the maximum number of backup log 

files to maintain in the system. 


Status Message Display Time. Specify the minimum time in seconds 

that login and other status messages remain in the status area. 

The Navigation section has the following settings: 

Allow Multiple Applications. When set to True, multiple instances of 

the application can be launched. Otherwise, when you have one 

instance of the application running and you click on the QAD 

Applications icon, instead of launching another instance of the 

program, the currently running program is activated. 

Fig. 1.4 

Administration 

Options


Set this to True if you need to log in as different users to perform 

different functions or for testing. 

Show Did You Know Messages. Select True to display messages 

about interface features when you log in to the system. 

The Plugins section displays information about the plug-in adapters that 

are used for the applications that run within the QAD .NET UI. Currently, 

only a plug-in for MFG/PRO exists. 

Assembly Location. Displays the path to the plug-in implementation. 

Authenticated. True indicates the current user has access to the 

plug-in. 

Provider. Displays the name of the company providing the plug-in. 

The Updates section controls automatic updates. 

Check for Updates. When this is True and a more recent version of 

the executable is found on the home server, the user is prompted 

during login to update the client. When this is False, the system does 

not check for updates. 

Home Server. Specify the address of the main application server to 

check for updates. This value is set during installation.

MFG/PRO Options 

From the Options window, click MFG/PRO to define options that affect 

the MFG/PRO application. 


The Browse Preferences let you choose settings that affect the appearance 

of browses. 

Cell Font. Specify the font name, style, and size to use for cell data 

values. This field displays a standard Windows font dialog where you 

can select a font, font style such as bold or italic, and font size. Or you 

can click the plus icon next to the Cell Font attribute to expand the 

values associated with it and specify them one at a time. 

Note Specifying the underline font attribute has no effect. This 

attribute is used by the system to indicate a link that can be clicked to 

drill down in a cell. 

Link Font Color. Choose the color to use for hot-linked data values. 

You can choose system colors, Web colors, or custom colors from a 

color palette. 

Row Alternating Color. Specify the background color for every other 

row in the browse display. 

Fig. 1.5 

MFG/PRO Options


See “Monitoring 

User Sessions” 

on page 144 for 

details. 

Row Background Color. Specify the background color for data rows 

in browses. 

Rows Per Page. Specify the number of data rows to retrieve for each 

page of data in the browse. This must be a number between 1 and 

1000. The default is 100. 

Under the General options, the date and time of the last logon of this user 

display. 

If you have more than one installed version of QAD Desktop, use the 

System Preferences settings to manage them. This can be useful if you 

have a test and production system that you are using at the same time. 

Application Server URL. This field displays the QAD .NET UI 

AppServer host, port, and, path. 

Desktop URL. This field displays the Desktop Web App URL. 

Display System Selection List. Set this to True to display a list of 

installed systems for selection after prompting for log-in information. 

The user can then select which system to access. 

IP Address, Session ID. These fields display information that might 

be useful to a system administrator in trouble-shooting activities. The 

session ID is the one that also displays in Session Master 

Maintenance (36.20.10.15). 

System Name. Choose the default system name from the list of 

available systems. Users will automatically be logged in to this 

system when Display System Selection List is False. 

The Terminal settings let you choose preferences for the display of 

programs run in the character UI. 

Background Color. Choose the color to use for the screen 

background. 

Bold Color. Choose the color to use for any text in the application that 

has the bold attribute. 

Font. Specify the font name and style to use for text strings on the 

character UI. This field displays the standard Windows font dialog 

described for Cell Font.

Note For optimal viewing, you should select a monofont font, such 

as Courier New (the default). The size attribute has no effect on 

display. The character screens are automatically resized to fit the 

available space. 

Foreground Color. Choose the color to use for text strings on the 

character UI. 

Manage Workspaces 

Choose this command to disable or enable workspaces or to change 

workspace order. 


Bold indicates the active 

workspace. 

Drag and drop to reorder 

the workspaces. 

Click to add this workspace 

to the Workspace menu. 

When the check box next to a workspace is selected, its name displays on 

the Workspace menu. 

You can reorder items in the Workspace list by clicking and dragging. The 

list order determines the order of display on the Workspace menu and at 

the bottom of the page. It can also affect Next and Previous workspace 

processing if you use the keyboard shortcuts. The workspace in bold text 

is currently active. See Table 1.1 on page 19 for a list of keyboard 

shortcuts. 

Fig. 1.6 

Manage 

Workspaces


Workspace Menu 

When you have access to more than one workspace, the Workspace menu 

lets you choose the one you want to work in from those that are available 

to you. The values that display on the menu are configured in Tools| 

Manage Workspaces. 

In MFG/PRO, a workspace represents a domain. However, other QAD 

applications can also have their own workspace. When you first log in, 

you must choose a workspace. When you exit the .NET UI, the active 

workspace is saved and displays when you log in again. 

Note See “Saved Session Values” on page 48 for details about other 

values that are maintained between sessions. 

You can change your active workspaces by selecting one from the list on 

the Workspace menu. When you change workspaces, any programs you 

have running in the current workspace remain open. You can return to the 

workspace later to complete any open transactions. 

Note The first time you access a workspace, the system must build the 

appropriate menu hierarchy for that workspace. This may take a few 

moments, but only occurs during the initial selection. On subsequent 

logins, menus are refreshed based on any changes made in the system. 

This also may cause a brief delay. 

Window Menu 

The Window menu displays a list of all programs currently open in the 

active workspace. 

Choose Close All Windows to close all open windows in a workspace. 

Change the active window by selecting one from the list. The currently 

active window displays with a check mark next to its name in the list. 

Help 

The Help button on the upper left side of the window menu opens the 

QAD .NET User Interface Guide unless the mouse focus is on a particular 

program or field, in which case clicking Help opens program or field help. 

As a shortcut, you can press the F1 key instead of clicking the Help 

button.

QAD .NET Keyboard Commands 

Some QAD .NET UI menu commands have keyboard options. In 

addition, you can use key combinations to move through windows and 

workspaces, and to access the menu and menu commands. General 

keyboard navigation options are listed in the following table. 

Note Navigation specific for browses is found in Table 2.1 on page 36; 

for HTML screens, information is in Table 2.2 on page 71. 


Command Keystroke Action 

Print Ctrl+P Prints the current browse. 

Menu Search Ctrl+M Activates the menu search bar. 

Previous 

Ctrl+F6 Displays a list of workspaces with focus on the 

Workspace 

previously active workspace. 

Next Workspace Ctrl+Shift+F6 Displays a list of workspaces with focus on the 

next workspace. 

Previous Window Ctrl+Tab Displays a list of windows with focus on the 

previously active window. 

Next Window Ctrl+Shift+Tab Displays a list of windows with focus on the next 

window. 

Access Menu Bar Alt Places focus on menu bar. Use the arrow keys to 

move through the menus 

Return from Menu Esc Returns cursor focus to field that was in focus 

Bar 

before Alt was pressed. 

Cut Ctrl+X Places selected text on the clipboard and 

removes it from the current location. 

Copy Ctrl+C Places selected text on the clipboard and leaves it 

where it is currently located. 

Paste Ctrl+V Places the contents of the clipboard in the current 

cursor location. 

Application Help F1 Displays help supplied by the currently running 

application. 

Close Alt+F4 Standard windows shortcut for closing the 

currently active window. 

Up arrow When focus is on search results, moves to menu 

search bar. 

Down arrow When focus is on menu search bar, moves to 

search results. 

Table 1.1 

Keyboard 

Navigation in 

QAD .NET UI


Fig. 1.7 

Applications 

Menus 

Fig. 1.8 

Right-Click Menu 

Options 

Application Menus 

The Applications section displays the menu choices for the QAD 

applications running in the QAD .NET UI. 

When the system is installed, the default menu organization is 

automatically loaded. Menu substitution is not supported in the 

QAD .NET UI; only items on the menus are included. 

Using Menu Options 

Right-click a menu item to display menu options.

With this menu option, you can: 


• Use Add to Favorites to add the selected menu item to your personal 

menus in the Favorites space below, described in “Adding Menus to 

Favorites” on page 23. 

• Use Design to display the screen for creating or modifying simplified 

screen templates. Design is only enabled when the program you select 

can be simplified. Otherwise, it is disabled. 

Chapter 3, “Simplifying HTML Screens,” on page 87 describes how 

to design simplified screens. 

Note You must also be a member of the group designated as UI 

designers in the UI administration page before the Design option is 

enabled. 

• Use Properties to display information about this menu item and to 

determine the UI display mode; see Figure 1.9. 

Program Auto Start 

You can automatically start any favorite menu item when you log in to the 

QAD .NET UI. For any menu item saved under Favorites, right click the 

item and select Auto Start. With Auto Start selected, the menu item starts 

automatically when you next log in. Favorite menu items that start 

automatically are displayed in bold. You can have more than one menu 

item start automatically. To disable this feature, right-click the item and 

deselect Auto Start. 

Note Only one process map can have Auto Start selected. Having 

multiple process maps with Auto Start selected will launch the Process 

tab but the display will be blank.


Fig. 1.9 

Menu Properties 

See “Defining 

Program 

Information” on 

page 145. 

See “Defining 

Program 


page 145. 

Menu Properties 

The following figure illustrates the Menu Properties window. 

The Menu Properties window displays: 

• The title of the menu item. 

• The current working domain and domain currency. If the specific 

program updates data that applies to all domains, All Domains 

displays next to the working domain currency. This is determined by 

settings in Program Information Maintenance (36.3.21.1). 

• Details about the program currently executing, including the program 

name and menu number. 

• If the user executing the program has been assigned a simplified 

version of the program, the name of the assigned UI template 

displays. 

• If a value has been specified for this user in the Name field in Menu 

System Maintenance (36.4.4), it displays as the Alias. The alias 

typically represents a shortened form of the longer menu name. 

• Version details for Desktop and MFG/PRO. 

Use the Open With drop-down to determine whether a program displays 

as an HTML screen (Desktop) or as a character-based terminal (Terminal) 

screen. Some programs include a .NET User Interface option for the


inclusion of additional features with the QAD .NET UI. For example, 

when you open Product Structure Maintenance with the .NET User 

Interface option, you have access to interactive drag-and-drop features. 

Initially, each program’s display mode is determined by settings in 

Program Information Maintenance (36.3.21.1). Each user can change this 

setting on a program-by-program basis using the Properties option. These 

choices are retained from session to session. 

Note Custom browses saved in the Favorites area only display in 

Browser Viewer mode. 

Menu Item Icons 

The icons listed here display next to menu items and indicate the type of 

associated program. 

Icon Description 

Favorites 

Report program 

Maintenance or control program; also displays next to 

URLs linked to browse cells 

Miscellaneous programs that do not fit another category, as 

well as any custom programs you add to the menus 

Browse 

Process map created with the Process Editor in Desktop 

Each user can easily create a personalized menu system in the Favorites 

area using options or drag-and-drop techniques. 

Adding Menus to Favorites 

Right-click a menu folder or menu item in the Applications area and 

choose the Add to Favorites option, shown in “Using Menu Options” on 

page 20. The menu appears at the bottom of the list in the Favorites area. 

Table 1.2 

Menu Icons


Fig. 1.10 

Create New Folder 

Fig. 1.11 

Rename or Remove 

Item 

Select the menu folder or item you want and drag it from the Applications 

area to the Favorites area. 

You can add a menu more than once if you want. 

Organizing Menus 

You can organize your Favorites into folders and subfolders, rename 

menu items and folders, rearrange the order of folders and items, and 

remove menu items you no longer want. 

To organize menus into a hierarchy, right-click in the menu space and 

choose Create New Folder. 

You can then drag the folder to any position and drag menu items or other 

folders into it. 

To rename or remove a menu item, right-click the item and choose the 

option you want. You can also display properties and go into design mode 

for enabled programs.


When you right-click a folder, you can also create a new subfolder within 

the currently selected folder. 

Menu Search 

You can use the search bar to quickly find menu items by short name 

(alias), description, program name, and menu number. Search supports an 

auto-completion feature. You can type a minimal number of characters 

and press Enter to expand the phrase you entered with the first match. 

When only a single match exists, the program is executed. 

Even though menus are listed by menu description, search by menu 

number, alias, and program name is supported to accommodate users who 

are familiar with other MFG/PRO user interfaces. 

Search locates all items that contain the search string, not just those that 

start with it. This is true of numeric as well as alphabetic input. Matches 

beginning with the search string display at the top of the results; matches 

that contain it display lower down. 

Example Typing Customer finds Customer Maintenance before 

Controlled Customer Maintenance. Typing 1.1 finds 1.1.1 before 2.1.1 or 

3.1.1. 

Search results display directly in the application menu area. 

You can use Search for multiple purposes: 

• Find programs based on one or more menu label keywords, program 

name, or menu number. For example, enter sales to display all menu 

labels that include the word sales. 

Fig. 1.12 

Create New 

Subfolder


Fig. 1.13 

Menu Search 

Results 

• Execute a specific program based on full menu label, program name, 

or menu number. For example, enter Item Master Maintenance, 

ppptmt.p, or 1.4.1 and then press Enter to display Item Master 

Maintenance. 

• Execute a specific program based on a shortcut defined in the Name 

field of Menu System Maintenance (36.4.4). 

Example Menu is the shortcut for Menu System Maintenance; enter 

menu and press Enter to display this screen. 

The system displays results as you type, so you can select what you are 

looking for as soon as it is uniquely identified. 

The following figure shows the results that display after typing 11 in the 

search bar. Click the Clear Search Text button to restore the menu view. 

Click to clear 

search text 

Note When a program has been added to more than one menu, each 

occurrence displays in the search results. This is likely to occur if you 

have added programs to Favorites. A tool tip displays the full path to the 

menu. 

Pressing Enter after typing 11 in the search bar narrows the results even 

more.

After using Search, you can right-click an item in the search results to 

display options. 


Available in search 

mode only 

In addition to the options that you have when you right-click a menu in 

non-search mode, you can choose Find in Menu in search mode. 

Choosing this option displays the currently selected menu item in location 

in the menu hierarchy. 

You should be aware of these additional considerations when using 

Search: 

• If you enter sales order, the search finds only menu labels containing 

that exact string. 

Fig. 1.14 

Menu Search 

Results After 

Pressing Enter 

Fig. 1.15 

Menu Options after 

Search


Fig. 1.16 

Open Programs in 

Application Area 

• A shortcut—specified in the Name field of Menu System 

Maintenance (36.4.4)—is always found first during a search. For 

example, Add is defined as the shortcut for Item Master Maintenance. 

If you enter add in Search, Item Master Maintenance displays first 

and executes if you press Enter. 

Application Area 

The programs you choose to run from the menu display in the application 

area of the QAD .NET UI. You can open multiple programs and organize 

them in different ways. 

The number of programs a specific user can have open at the same time is 

defined during installation. See Installation Guide: QAD User Interfaces 

for details. 

Note You can have multiple instances of an HTML program or browse 

open. For example, you can have multiple instances of Sales Order 

Browse or Sales Order Maintenance open. However, you can have only a 

single instance of a character screen, process map, or help window. 

The following figure illustrates the default way multiple programs are 

organized, using tabs across the top of the screen. 

Close 

this tab.

You can click a tab to activate it or click the “x” on the tab to close it. 

You can use the keyboard to navigate through open programs. Ctrl+Tab 

displays a list of open programs you can select from, with focus on the 

next window. Ctrl+Shift+Tab displays the same list with focus on the 

previous window. 

You can create additional tab groups in either horizontal or vertical 

layout. Right-click any tab to display the tab options. 

Click Close to close the current program. 


Click New Horizontal tab group to split the screen horizontally and move 

this program to the new area. The following figure illustrates two 

horizontal groups. 

Fig. 1.17 

Tab Options


Fig. 1.18 

Horizontal Tab 

Groups 

Fig. 1.19 

Vertical Tab Groups 

Click New Vertical Tab Group to split the screen vertically and move this 

program to the new vertical area.


You can only create groups of one type. After you have created the first 

vertical group, the option to create a horizontal group is not available; the 

same is true after you create a horizontal group. However, you can create 

as many of one type of group as you want. 

When multiple groups exist, other options to move to the next or previous 

tab group display when you right-click a tab. Use these options to move 

programs from one screen area to another. Or you can simply drag 

programs where you want them. 

You can create multiple horizontal views of a browse by dragging the 

border widget located above the horizontal scroll bar on the upper right 

side of the browse view. Similarly, you can create multiple vertical views 

of the same browse by dragging the border widget located on the left of 

the vertical scroll bar. Creating multiple horizontal and vertical views of a 

browse is useful when working with a large browse that is difficult to 

view in a single pane. 

Click Close All to close all the tabs or click Close Others to close all the 

tabs except the currently active tab. 

To help you navigate complex screens, the QAD .NET UI includes 

navigation buttons along the left side of some screens. For example, the 

screen for Purchase Order Maintenance includes navigation buttons 

Fig. 1.20 

Next/Previous Tab 

Group Options


Fig. 1.21 

Navigation Buttons 

indicating the parts of a purchase order: Header, Tax Info, Lines, and 

Trailer. 

Navigation Button Area. 

You can hide the navigation buttons by clicking on the black triangle 

located in the upper right corner of the pane. To view the navigation pane, 

click the black triangle again. Your system administrator can set whether 

this feature is available on your system.

Chapter 2 

Using Programs in 


This following topics cover how to use functions within the QAD .NET 

User Interface (UI). 

Using QAD .NET UI Browses and Lookups 34 

Saved Session Values 48 

Using Browse Charting 49 

Using Browse Collections 54 

Using Product Structure Maintenance 57 

Using HTML Maintenance Programs 59 

Using Character Terminal Screens 74 

Requesting Application Help 76 

Creating Custom Links 78 

Using Special UI Features 80


Fig. 2.1 

Sales Order Browse 

Using QAD .NET UI Browses and Lookups 

The QAD .NET UI lets you view browse data defined with MFG/PRO 

Browse Maintenance (36.20.13) and View Maintenance (36.20.18) using 

advanced features of .NET technology. Any browse defined using 

standard MFG/PRO functions can be viewed from the QAD .NET UI, 

including custom browses developed to meet your specific business 

requirements. 

Browses and lookups in the QAD .NET UI have a consistent appearance 

and features. The only significant difference is that browses can be added 

to the menus and invoked from a menu, while lookups must be associated 

with a field and displayed from a program. 

Note Since lookups are not invoked from a menu, you cannot save 

search criteria in lookups or add the saved searches to your Favorites. 

The following figure illustrates Sales Order Browse. 

Navigation 

buttons 

Selected 

row 

Sortable 

column 

Blue text 

for drilldowns 

Save and retrieve browse search 

Total number of records

Some of the features of browses include the following: 

• Any column with arrows in the title bar can be sorted. Click the 

heading to sort in ascending order; click again to sort in descending 

order. Columns that cannot be sorted are generally non-indexed 

fields. Sorting by such fields would degrade system performance. 

• Blue underlined text indicates values where you can drill-down for 

additional details. Right-click any value to display a list of associated 

links: either a more detailed browse, a related MFG/PRO program, or 

an external Web page. See “Accessing Links in Browses” on page 42 

for details about the kinds of links available in browse data fields. 

• Use the navigation buttons in the top left to move through the records. 

The buttons from left to right move to the first set, previous set, next 

set, last set. See “Navigating in Browses” on page 36 for details. 

• Use the Records To Show drop-down to determine how many records 

display at one time in the browse. The default value can be set using 

the Rows Per Page setting in Tools|Options. 

When you display a large number of records, it may take some time 

for the system to retrieve them. In this case, a dialog displays, letting 

you know the approximate wait time. You can cancel and specify a 

smaller number by using search conditions to reduce the number of 

records. 

Important Use caution in displaying all records, especially when the 

number of records is large. Attempting to display a large number of 

records at once can adversely affect performance. Instead, use the 

Advanced Search conditions to focus on the specific records you 

want to review. 

• Drag columns by their headings to rearrange the display. 

Using Programs in QAD .NET UI 35 

See page 16 for 

details on Rows 

per Page. 

Fig. 2.2 

Data Retrieval 

Progress


Table 2.1 

Browse Navigation 

• Click the Excel icon to generate an Excel worksheet with the browse 

data. For details, see “Creating Excel Output” on page 41. 

• Click the printer icon to print the browse data. The standard Windows 

print dialog displays so that you can select a remote or local printer or 

print to file. You can also use the Print and Print Preview commands 

on the Menu to print the browse data. 

Important Make sure that the printer is online before trying to print 

to it. No error displays when you attempt to print to an offline printer. 

• Specify simple or complex search criteria using multiple attributes 

and ranges. 

• Save browse search criteria for reuse in a file and then retrieve them 

later, or create customized browse searches and add them to the 

Favorites menu area. See “Searching in Browses” on page 44 for 

details. 

Navigating in Browses 

You can use the navigation buttons in the top left to move through browse 

records. 

Icon Keyboard Action 

Alt+Up Arrow Key First set of records 

Alt+Left Arrow Key Previous set of records 

Alt+Right Arrow Key Next set of records 

Alt+Down Arrow Key Last set of records 

You can also use Tab and Shift+Tab to move through the buttons and 

fields in the browse toolbar. In this case, pressing Enter is the same as a 

right-mouse click. When you are in the browse search panel, pressing 

Enter executes the search with the current conditions. 

After you have selected a row, you can use the up arrow or right arrow 

keys to move the row selection up one row; the down arrow and left arrow 

keys move the row selection down one row.

You may notice slower performance during paging when a large number 

of records is displayed. Paging performance may worsen as you get to the 

bottom of the list. To reduce this problem, click a relevant column to 

reverse the sort and page through those records at the top of the list. 

Column Options 

Right-click a column heading to display a list of options. 

With the column options, you can: 

• Use Autosize Columns to resize browse columns based on the size of 

the displayed data. By default, the browse displays with columns 

already autosized. If you turn this option off and manually adjust 

column sizes, your settings for each browse are retained between 

sessions. If a cell’s data exceeds the column width, three dots (...) are 

displayed on the right. 

Note When you are viewing all records in a browse (Records to 

show set to All) and Autosize Columns is on, the autosized column 

widths are based on the first 500 records for performance reasons. 

• Use the Group By functions to create and manage custom views of 

the browse data. 


Fig. 2.3 

Browse Column 

Options


Note Group By functions are available only when all records are 

being viewed. 

• Use Summary to get a summary of the data in the browse column. If 

the data in the column is numerical, you can get a summary based on 

the following: 

Count. Displays the number of items in an x-axis group. (This is the 

only summary option available for non-numerical data.) 

Sum. Displays the sum of the values in the column. 

Average. Displays the average of the values in the column. 

Minimum. Displays the minimum of the values in the column. 

Maximum. Displays the maximum of the values in the column. 

The summaries are displayed below the column in a Summaries area. 

• Use Hide Column to remove a column from display. 

• Use Reset to Factory Settings to return to the default column display 

settings. 

• Use Columns to display a list of all columns defined for the browse 

and toggle the show/hide settings. You can use this to restore a 

column that was previously hidden. 

• Use Properties to display technical information about the data in the 

column. This includes the name of the current program and the 

database table and field where the data for the column is stored. 

Grouping Data in Browses 

You can group data in a browse by one or multiple column headings. This 

gives you a quick way of building custom views of your data, which can 

then be exported to Excel. The groups are maintained in the Excel 

workbook as pivot tables. 

Note You must be displaying all available records in order to use the 

group by functions; otherwise, the results could be misleading. 

You begin this process in two ways:

• Right-click a column heading and choose Show Group By Box. This 

creates an area at the top of the browse where you can drag column 

headings to use as groups and subgroups. This area gives a clear 

visual indicator of the organization of the data. 

• Right-click a column heading and choose Group By Column Name. 

Column Name will reflect the name of the current column. This 

creates an immediate single-level grouping. You can create as many 

groupings below this one as you want. 

After you have created groups, you can use the plus (+) or minus (–) icons 

to open or close the group data for viewing. You can also use the Expand 

All Groups or Collapse All Groups options on the right-click menu to 

quickly open and close all groups of data. 

Using Group By Box 

The following figure illustrates Sales Order Browse after right-clicking a 

column heading and choosing Show Group By Box. You can then drag a 

column heading to the boxed area to create a grouping. Red arrows 

indicate when a dragged column heading can be dropped. 

Drag 

column 

heading 

here. 


Fig. 2.4 

Group By Box


Fig. 2.5 

Group By Box with 

Two Groups 

Fig. 2.6 

Group By Item 

Number 

Figure 2.5 illustrates the Sales Order Browse after dragging the Item 

Number and Due Date columns into the group by box. The due date, 

which was dragged after item number, is a subordinate grouping. You can 

see the effect on the browse data when you click the plus icon to expand 

the information. 

Note To select the due date column, you must first expand one of the 

item number groups. 

Graphical 

display of 

column 

grouping 

Using Group By Column Name 

The following figure illustrates Sales Order Browse after right-clicking 

the Item Number column and choosing Group By Item Number. The 

effect is the same as using the group by box, but you do not have the 

graphical representation of the grouping as a reference.

To add more groups, expand an existing group to display the data, rightclick 

the column heading you want to use as a subgroup, and choose 

Group By Column Name again. 

Creating Excel Output 

All browse data can be exported to Excel. The export creates three 

worksheets in an Excel workbook, which is opened for display. 

Data. This page contains the actual data columns and headings from 

the printed browse. 

Search Conditions. This page displays any search conditions used to 

filter the printed data. The conditions listed are field name, operator, 

value and, for a range operation, the ending value. 

Info. This page lists details about the report generation including the 

ID of the user generating the report, the date the report was generated, 

the name of the browse, and the browse program. 

If you have grouped data in the browse, the grouping is preserved in 

Excel as pivot tables. 

After exporting to Excel, you can use the Excel chart features to create 

visual displays of your data, such as the following pie chart showing 

quantity on hand of various inventory items. 


Fig. 2.7 

Grouped Data in 

Excel


Fig. 2.8 

Graphed Data in 

Excel 

Accessing Links in Browses 

See page 15. Browse data columns can contain multiple types of links, which display 

in colored text in individual browse cells. You set link attributes using the 

Cell Font and Link Font Color settings in Tools|Options. You access the 

link by right-clicking in the cell to display the linked choices. 

• Browses can contain links to other browses. These links are defined 

in Drill Down/Lookup Maintenance (36.20.1). 

• Browses can contain uniform resource locator (URL) links defined in 

Browse URL Maintenance (36.20.10.11). Setting up these links is 

discussed in “Defining Browse URL Links” on page 137. 

Two different kinds of URL links can be defined: 

• Links to external Web sites, such as a supplier Web site associated 

with a supplier ID or to an intranet resource, such as a document 

containing the design specifications for an item. Right-click to 

display the list of links; select one to launch a new browser window 

and display the intranet or Internet resource to which that URL refers. 

Example A supplier ID in the Supplier Browse is associated with a 

URL link to that supplier’s company Web site. When you right-click 

the supplier ID underlined in blue text, you can choose the URL to 

launch. This automatically launches a Web browser to display the 

supplier’s Web site. 

• Links to other MFG/PRO menu-level programs. These links let you 

use browses as a means of navigating directly to maintenance 

programs while passing specific data values to them. Right-clicking 

and selecting one of these links opens the program from within the 

browse and fills in any fields that are part of the link.

Example The supplier ID field in the Supplier Browse is associated 

with a link to Supplier Maintenance. Right-clicking this supplier ID, 

underlined in blue text, displays available links. Selecting Supplier 

Maintenance automatically launches Supplier Maintenance with the 

currently selected supplier ID filled in so you can make any required 

updates. 

More than one browse, URL, or program link can be associated with a 

browse field. Right-click in a cell or column containing links to display a 

list of all the links associated with that cell or column. 

The following figure illustrates a list that displays when you right-click a 

cell with two associated drill-down browses. 

Clicking the first link displays a drill-down of information associated with 

the customer in the active browse cell. The following figure shows how 

this looks. 


Fig. 2.9 

Browse Data 

Window with Links 

Fig. 2.10 

Drill-Down and 

Main Browse 

Windows


Fig. 2.11 

Browse Search 

The drill-down displays with advanced search criteria set to equal the 

customer number in the active browse cell. You can drill down to another 

browse from the current drill-down. Each open drill-down displays 

another subtab. 

Searching in Browses 

The QAD .NET UI provides extensive, configurable browse search 

capabilities that let you create both simple and complex queries. You can 

save these queries to reuse later. 

Note Saving and reusing search criteria is supported in browses, but not 

lookups. 

Search this 

column. 

Values start 

with this. 

Initially, one search condition displays. 

Get data 

1 Choose the field that you want to search from the drop-down list. 

2 Choose a search operator from the drop-down list; the default is starts 

at. 

3 Enter a value in the search box or select a value from the associated 

lookup.

4 Click Go to initiate the search. 

Note Only indexed fields can be selected for the simple-search function. 

For character fields, the asterisk (*) matches any number of characters 

when the search operator is equals or contains. 

Using Advanced Search 

To narrow the focus of the search more, click Advanced Search. The 

button title changes to Hide Search Criteria; clicking it again hides the 

advanced-search panel. 

Note Search conditions in a hidden advanced-search panel still affect the 

browse result. In this case the button displays with red text. 

Clears all 

search criteria. 

Choose a search 

operator. 

Enabled for 

range operator 

only. 

Add or remove 

search criteria. 

Button label changes to Hide Search Criteria. 

To refine your search further, click the plus (+) icon to add another search 

row. You can add as many rows as needed, each with different search 

values and operators. If you choose the range search operator, the second 

search box is enabled for the ending value of the range. 


Fig. 2.12 

Browse Advanced 

Search


You can use the following operators with search: 

Equals The system returns records with values that exactly 

match the value you specify. For character fields, 

you can use the asterisk (*) as a wild card for partial 

matches. 

Starts with The system returns records that start with the value 

you specify. 

Contains The system returns records that contain the value you 

specify in any position. For character fields, you can 

also use the asterisk (*) as a wild card. 

Note This operator can be used with character fields 

only. 

Less than The system returns records with a value less than the 

one you specify. 

Greater than The system returns records with a value greater than 

the one you specify. 

Range You must specify two values. The system returns 

records that match the first or last value specified and 

all others within that range. 

When you are finished searching, you can click the Hide Search Criteria 

button to remove the search criteria display. 

Important Hidden search criteria still affect the browse results; to restore 

the results to the way they were before you began the search, use the 

minus (–) icons to remove the search criteria or click the red icon to clear 

all criteria. 

When you use advanced search and specify several search criteria, note 

the following: 

• Multiple criteria for the same field are treated as a logical OR 

condition. 

• Multiple criteria for different fields are treated as a logical AND 

condition.

Example You specify the following search conditions: 

• Sales order equals SO*153. 

• Sales order contains 43. 

• Sold to greater than 100. 

The search results include orders sold to customers 101 and higher that 

start with SO followed by any characters and end with 153 or orders sold 

to customers 101 and higher that contain 43 in the order number. 

Saving Searches 

If you want to save search settings for reuse later, you can save them to a 

file and then load the file to run the search. You can also optionally add a 

menu item to your Favorites menu that represents specific browse 

settings. 

To complete these actions, you use these buttons on the browse: 

Save Browse Settings Load Browse Settings 

To save settings, complete these steps: 

1 Click the browse Save button. The Save Browse Settings dialog 

displays. 


Fig. 2.13 

Save Browse 

Settings


Fig. 2.14 

Save to Favorites 

Prompt 

2 Specify a name for the criteria. Do not specify a file extension. 

The name you specify is concatenated to the name of the currently 

running browse with an .xml extension. These files are saved in a 

BrowseSearches subfolder beneath the Application Data 

folder on your local drive and have the following format: 

UserSpecifiedName.browsename.xml 

Example You are saving a set of search criteria for Sales Order 

Browse (sobr009.p) that finds orders for customer 100. You specify 

SoldTo100 as the name. The physical file name is 

SoldTo100.so009.xml. 

3 Click Save to save the data. You are prompted to add the browse to 

your Favorites. 

4 Click No if you only want to save the browse in file format; click Yes 

to add the browse to your Favorites with the name specified in step 2. 

5 To reuse the settings, select the item from the Favorites menu or click 

the Load button to reload the criteria from the BrowseSearches 

folder. 

Saved Session Values 

The system remembers many of the choices you make during a 

QAD .NET UI session. When you log in the next time, the interface 

reflects the way you last used it. 

Note These settings are saved on your computer. If you log in to the 

QAD .NET UI from a different computer, the session values are not 

restored. 

Some settings are saved for a specific workspace; if you have access to 

more than one workspace, some saved values apply to all.

Values retained from session to session that apply to all workspaces 

include: 

• Any changes to the sizing of the menus and application area. 

• Any change you make to a browse, such as hiding columns, moving 

columns, or toggling the Autosave Columns feature. Resizing of 

columns is saved only when Autosize is not enabled. Note that: 

• Group-by fields are always cleared when a browse is reloaded. 

• The group-by box is always hidden when a browse is reloaded. 

• Sorted columns are cleared when a browse is reloaded. 

• The last user ID specified during successful login and the associated 

language setting. 

• The last workspace activated. 

• The list of disabled workspaces specified with Tools|Manage 

Workspaces and the display order for the workspaces. 

• The choice of program display mode made with the Properties dialog: 

either Desktop or Terminal. 

Values retained from session to session within a workspace include: 

• The content of Favorites. 

• The history of last-used programs that displays on the File menu 

Using Browse Charting 

With the new browse charting feature, you can quickly generate graphical 

representations of browse data. You can toggle between the standard 

browse display (called the grid view) and the new chart view. Using the 

chart view editor, you can select data in a browse and have it displayed as 

a pie chart or bar graph, for example. 

Using Programs in QAD .NET UI 49


To create charts from browses: 

1 Start a browse and click on the Edit Chart Design icon. 

Edit Chart Design icon 

2 Design a chart using the Browse Chart Designer. 

The Browse Chart Designer lets you choose settings that define a chart: 

X-Axis Label. Enter the label for the chart’s x-axis data. 

X Variable. Select the variable for the x-axis data from a pull-down 

menu listing the available columns in the browse. 

Y-Axis Label. Enter the label the chart’s y-axis data.

Y-Variables. Select the variables for the y-axis data from a pull-down 

menu listing the available columns in the browse. You can select up to 

five variables, depending on the type of chart you would like to use. 

For example, for a stacked bar chart you can select two or more 

variables. 


Group By X Values. Select Yes if you want to display all the common 

x-axis data together in groups. Select No if you want to display the xaxis 

data individually. The x-axis data can be grouped in the 

following ways: 

Count displays the number of items in an x-axis group. 

Sum displays the sum of the values in an x-axis group. 

Average displays the average value in an x-axis group. 

Minimum displays the minimum value in an x-axis group. 

Maximum displays the maximum value in an x-axis group. 

Chart Title. Enter a title for the chart. 

Chart Type. Select from among the following types of charts: 

• Column Chart 

• Column Chart 3D 

• Bar Chart 

• Bar Chart 3D 

• Pie Chart 

• Pie Chart 3D 

• Stacked Column Chart 

• Stacked Column Chart 3D 

• Stacked Bar Chart 

• Stacked Bar Chart 3D 

Preview. Click the Preview button to view the chart before you save 

it.


3 Click Apply to view the chart. 

Note Rendering charts with many elements can be CPU intensive. 

To prevent users from attempting to render large charts that could 

degrade their computer’s performance, the system checks the number 

of elements in a chart before rendering the chart and provides a 

warning if the number of elements might degrade performance. In a 

chart without grouping, the number of elements in a chart is the 

number of records in the browse display. In a chart with grouping, the 

number of elements is the number of groups of records. The default 

value for the maximum number of elements allowed before a warning 

is displayed is 100 by default. An administrator can change this 

default setting by editing the ChartElementsForChartWarning 

setting in the QAD .NET UI Application Settings file (by default, 

TomcatInstallDir\webapps\qadhome\client\plugins\mfg 

pro\default.xml).

4 You can toggle between the chart view and the grid view of the 

browse by clicking on the Show Grid View or the Show Chart View 

icons. If you are in chart view, the Show Grid View icon is displayed, 

and if you are in grid view, the Show Chart View icon is displayed. 

5 While in chart view, you can do the following: 

Rotate and Zoom 3D Charts 

You can rotate 3D charts by pressing the Alt key and moving the mouse. 

Similarly, you can zoom 3D charts by pressing the Alt key and moving 

the mouse’s scroll wheel. 

Search Charts 

The QAD .NET UI’s browse search capabilities apply to the chart view as 

well as the grid view. By using the search capabilities you can 

interactively change the chart view of the browse. 

Hide Titles and Legends 

Chart titles and legends are shown by default. 

Show Chart View icon 

You can hide (or show) titles by right-clicking and selecting Hide Titles 

(or Show Titles). Similarly, you can hide (or show) the legend by rightclicking 

and selecting Hide Legend (or Show Legend). 



Launch Chart in New Window 

To launch a chart in a new window, right-click on the chart and select 

Launch in New Window. 

Copy Chart to Clipboard 

You can copy the chart to the clipboard so you can paste it in other 

applications. To copy the chart to the clipboard, right-click in the chart 

area and select Copy to Clipboard. 

Edit Chart Design 

To return to the chart editor, click the Edit Chart Design icon. 

Interactive Charting 

For any item in the chart that has a drill-down, you can have a split-screen 

view of both the chart and the drill-down browse, which can also be 

displayed as a chart. When you click on an item in the first chart, the drilldown 

chart will automatically change to reflect the changed data for the 

drill-down. Clicking on an item in the chart also selects the associated 

row in the browse. Conversely, clicking on a row in a browse also selects 

the associated item in the chart. 

Using Browse Collections 

To help you browse and maintain related item, site, sales, location, and 

customer data, you can now define collections of related browse and 

maintenance programs. In a browse collection, a main browse drives the 

fields selected in the other browses and programs. The QAD .NET UI 

displays the other browses and programs in the lower part of a horizontal 

split-screen, with the main browse located in the upper part. 

For example, you could define a browse collection called Sales that 

includes a Sales Order browse with a Site browse, Customer browse, and 

Sales Order Maintenance program.

If you click on a sales order in Sales Order, the associated browses and 

Sales Order Maintenance program automatically have the data for that 

order entered. You can just click on the Customer tab to see the 

information on the customer for that order, or click on the Sales Order 

Maintenance tab to see the sales order. 


Fig. 2.15 

Browse Collection


Fig. 2.16 

Sales Collection 

Using the new Browse Collection program, you can define your own 

browse collections that you can then save under Favorites. To define 

browse collections: 

1 Select Administration|Browse Collection. 

2 To start a new collection, click the New button. (To edit an existing 

program group, click Load.) 

3 From the Browse Definitions window, select the browse that you 

want to use to drive the fields of other programs or browses. (To 

select the browse, click on the right-hand square of a row.) 

4 Next, you add browses or programs that can be driven by the browse 

you have just selected. Click Add Browse or Add Program. 

5 Locate the table with the Target Field and Source Field columns. The 

Target Field column includes the fields that can be driven by 

whatever source fields you want to select. To select a source field, go 

to the appropriate source field cell and select a field from the pulldown 

menu, which lists all the available fields from the browse you 

first selected. Note that programs allow only one field to be the target.

6 If you decide you want to remove one of the browses or programs, 

select the browse or program and click Remove. 

7 To preview the collection, click Preview. 

8 To save the program group as a favorite, click Save. The system 

prompts you to name the browse collection. The browse collection 

definition is saved as an XML file on your local machine where you 

are running the QAD .NET UI. 

Using Product Structure Maintenance 

The Product Structure Maintenance program now includes a new 

graphical tool for creating, viewing, and editing the structure of bills of 

materials. This tool is only available with the QAD .NET UI. 

Important To access the tool, the program must be set so that it opens in 

QAD .NET UI mode. To do so, in the left navigation area, right-click and 

select Properties. Set Open with: to .NET User Interface and click OK. 

To create a product structure: 

1 Open Product Structure Maintenance. 

Note the blank workspace in the upper part of the display, located 

above the browses for Items and Product Structure Codes. 


Fig. 2.17 

Product Structure 

Maintenance


2 Drag a component (an item or product structure code) from a browse 

to the workspace. 

The component is now added to the product structure. The interface 

displays pertinent fields along the top, including Component, 

Description, Unit of Measure, Quantity, Reference, Start Date, and 

End Date. Note that you can edit the Quantity, Reference, Start Date, 

and End Date fields, while the other fields are read-only. 

You can undo a component added to the product structure by 

selecting the component, right-click, and select Undo Add. 

You can undo changes to the product structure by clicking the Undo 

Product Structure Changes icon. Clicking this icon reverses the 

changes you have made to the selected component and all 

components under the selected component in the product structure 

hierarchy. 

You can undo changes to a component by clicking the Undo 

Component Changes icon. Clicking this icon reverses changes you 

have made to the selected component only. 

3 Drag additional components to the workspace and directly position 

them within the product structure. Alternatively, double-click an item 

or product structure code. 

The currently selected component is colored orange. 

New or modified components in the product structure are colored 

yellow. These components have been added to the product structure 

as displayed in the workspace but have not yet been saved to the 

database. 

The system displays an error message if: 

• You attempt to create a cyclical structure. For example, the 

system will not allow you to add an item so that it is a parent of 

itself. 

• You add duplicate components to the same parent and then save 

the structure. 

• You try to have two same components with overlapping valid 

periods and then save the structure. 

4 To save a product structure to the database, select the top-level 

component, right-click and select Save (or click the Save icon).

If the system finds any problems while it saves the product structure, 

the components that need attention are displayed in red. 

5 Once a product structure has been saved, you can delete a component 

in the structure as follows: select the component, left-click and select 

Delete from the pull-down menu. 

Note If a component has not yet been saved to the database (the 

component is colored yellow), instead of Delete the selection is Undo 

Add. 

Rather than delete a component from the product structure, a common 

practice is to change the end date of a component so that the 

component is effectively obsolete. 

Using HTML Maintenance Programs 

The default input screens for most MFG/PRO programs running in the 

QAD .NET UI are standard HTML pages. While the sequence of fields 

and frames is modeled after the character interface, all of the input fields 

on HTML screens support standard editing options such as highlighting, 

cutting, copying, and pasting. You can click into fields in the active frame 

in any order to update them. 

In the HTML screen, all logical fields display as check boxes. In some 

cases, drop-down lists and radio buttons are also used. Within a screen, 

you navigate by clicking buttons, using the keyboard, or choosing 

options. 

A UI designer can simplify certain HTML screens. Designers can disable 

fields for input, hide fields, set a predefined default value for a field, mark 

a field as required, 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. This tool is 

described in Chapter 3, “Simplifying HTML Screens,” on page 87. 



Fig. 2.18 

HTML 

Maintenance 

Program 

See “Creating 

Custom Links” 

on page 78. 

Sample HTML Screen 

The following figure illustrates the screen that displays when you click 

the Sales Order Maintenance (7.1.1) menu link. 

Click to see links or create a new one. 

Click to see additional commands. 

Lookup 

Optional navigation pane 

Click to go 

forward (Go). 

Click to go 

back (End). 

Click Next or Back to proceed to the next frame (Go) or go back (End). 

Other commands may also be active for the current program. Which 

commands you can use varies from program to program and frame to 

frame. To see these commands, click the Actions link. 

Click Program Links at the bottom of the program screen to create links to 

other programs using User Tool Maintenance (36.20.4). The links you add 

display on the Program Links drop-down. They also display when you 

right-click a program screen (see Figure 2.21).

Entering Data in HTML Screens 

You can use a variety of ways to input data in HTML screens. 

• Many fields display a small magnifying glass icon. This indicates that 

a lookup is associated with the field. Click the icon or use the Alt+L 

keyboard shortcut to display the lookup. The lookup lists the valid 

values; select one from the list. 

• Date fields have an associated calendar. Double-click in the field or 

use the Alt+L keyboard shortcut to display a calendar for selecting an 

appropriate date. 

• When only a few values apply to a field, a drop-down list displays. 

Select the appropriate value from the list. 

• Logical fields represent Yes and No choices. These display as check 

boxes on HTML screens. A clear check box indicates a No value; a 

box with a check indicates a Yes value. 

Using HTML Calendars 

When you click in a date field in an HTML screen, a calendar tool like the 

following displays. You can also use the Alt+L keyboard shortcut to 

display the calendar. 

Go back to previous year. 

Go back to previous month. 

Proceed to next month. 

Use the calendar to choose and insert a date into the active field. You can 

use the keyboard or your mouse to navigate this calendar. 

• Using the keyboard, use the Tab key to move the cursor through the 

calendar. Tab begins with the arrows at the top of the calendar. With 

an arrow button selected, press spacebar to display previous and next 

months and years as shown in the figure. Press spacebar when a date 

in the current month is selected to enter that date in the date field. 


Proceed to next year. 

Fig. 2.19 

HTML Calendar


Fig. 2.20 

Actions Menu 

• Using the mouse, click the arrows for the next and previous months or 

years; then click the day in the displayed month to insert it into the 

active field. 

Using the Actions and Go To Menus in HTML Screens 

To see a menu of the active commands that apply to your current program 

context, select the Actions menu. 

Actions menu 

Action menu commands include: 

• Next Record and Previous Record are commonly available 

commands. Use them to display the next and previous records for the 

current field. 

Note You can also use the up and down arrows on your keyboard to 

display next and previous records in key fields or when the field has 

been defined to support next/previous processing. 

• Email is another command that is available in any context. Using this 

option is described in “Sending URL Links in E-Mail” on page 65.

You can view any added program links by selecting the Go To menu, 

located next to the Actions menu. To add links, select Go To|Add Link, 

which opens the User Tool Maintenance program. 

When you right-click in the screen, the menu combines Actions and Go 

To links for ease of use. 

Commands that display in the Progress status bar in a character session 

can be found in the Actions menu on HTML screens. This includes 

Delete, Page Up, Page Down, and Pivot. These commands are only 

available when the program frame supports them. For example, Page Up 

and Page Down typically display in selection lists where the up/down 

keys cannot be used. 

Note The Delete, Insert, Page Up, and Page Down keys on your 

keyboard operate as shortcuts to the Actions menu. However, shortcuts do 

not exist for special operations such as Pivot. 

Pivot is used in a number of selection lists that support sorting by specific 

columns. Pivot is used in a number of selection lists that support sorting 

by different columns, such as the call lookup in Call Maintenance 

(11.1.1.1). It is also used to display the next set of data in programs such 

as Line Utilization Maintenance (33.15.9) and Simulation Line 

Utilization Maintenance (33.17.19). 


Fig. 2.21 

Actions Menu, 

Right-Click


Fig. 2.22 

Pivot Command 

Fig. 2.23 

Pivot Command 

Changes Sort 

Column 

In the following figure, Queue is the currently active sort column, as 

indicated by the italic, red font. 

Pivot 

command 

Use Pivot to move to the next column and sort records by its values. In 

this example, choosing Pivot changes the sort column from Area to Eng 

Code.

Sending URL Links in E-Mail 

You can use the Email command on the Actions menu in any HTML 

program to generate a URL link to the current program. Using these 

URLs greatly simplifies group work flow by letting one user notify 

another when to begin their step in a process. 

Example Customer Representative Jane creates a new customer address 

record. Jane then right-clicks anywhere on the Customer Maintenance 

screen and chooses Email. This creates a new e-mail message using the 

company e-mail system and adds a direct-launch URL to Customer 

Maintenance in the body of the message. Jane adds information about the 

customer ID she just created and sends this message to her supervisor, 

Mark, who needs to review the record and add appropriate credit limits. 

When Mark gets the e-mail, he clicks the URL link and enters log-in 

information. Customer Maintenance then displays with the correct 

customer record already in edit mode. 

The following figure shows Customer Maintenance with the new record 

for 01000000. Right-click to display the Actions menu and choose Email 

to generate an e-mail message. 


Fig. 2.24 

Choosing Email 

from the Actions 

Menu


Fig. 2.25 

System-Generated 

Message 

Fig. 2.26 

Internet Options 

Settings 

In the system-generated e-mail message, the subject is set to the menu 

description of the currently executing program. 

Before sending the e-mail, you can add information to the URL to 

identify a specific record or any other additional information as needed. 

The system uses the e-mail program defined in the browser Tools|Internet 

Options|Programs setting. 

Note You can also set the e-mail program from the QAD .NET UI using 

Tools|Internet Options. 

Indicates 

default e-mail 

program to use

The system generates a URL of the following format: 

http://host:port/Web_AppName/api.jsp?id=MFGPROProgramName 

For example: 

http://netui.qad.com:8100/eb2_d3/api.jsp?id=adcsmt.p 

You can manually add a field value to be passed to the MFG/PRO 

program when it is launched using the following format: 

&fieldname=FieldName&fieldvalue=FieldValue&submit= 

n&domain=DomainCode 

Where: 

FieldName is the name of the field with the key value. 

FieldValue is the value that you want to pass to the field. 

n is the number of times you want the Go command executed. 

DomainCode is the code identifying a domain in an MFG/PRO eB2.1 

environment for retrieving a record. 

This is the same syntax that is used for generating links to other 

MFG/PRO programs in browses; see page 139. 

Example To pass the value 01000000 as the customer ID to Customer 

Maintenance in the USA domain of an MFG/PRO eB2.1 environment, 

you would enter: 

http://netui.qad.com:8100/eb2_d3/api.jsp?id= 

adcsmt.p&fieldname=cm_addr&fieldvalue=01000000 

&submit=1&domain=USA 

Understanding HTML Program Overlay Frames 

Most MFG/PRO maintenance programs have multiple frames that display 

sequentially as you click Next. You must complete the required fields in 

the first frame before you can proceed to the next. 

Some frames display as pop-up screens that overlay the screens below 

them. 



Fig. 2.27 

Overlay Frame 

You can move these overlay frames by clicking the bar at the top and 

dragging with your mouse. After you complete the required fields, click 

Next to continue. 

Working with HTML Program Selection Lists 

Many MFG/PRO functions display multiple records in a list format and 

let you select one or more of them. 

Single-Row Selection Lists 

Click and drag with the 

mouse to move this frame. 

Click Next to 

continue. 

Some HTML programs such as Item Master Maintenance (1.4.1) require 

you to select an active row for editing. 

Note The heading of the primary column displays with special 

formatting: italics and red color. In this example, Element is the primary 

control column.

Click to 

edit. 

To edit this type of list, click the row that you want to update, or use the 

right-click menu on the row to choose an option such as insert, to create a 

new row. The row highlighted in gray is currently in focus. When a 

selection list initially displays, this is always the first row. 

You can also use the following keyboard shortcuts: 

• Tab moves selection forward through the rows. 

• Shift+Tab moves the selection backward. 

• Spacebar is the shortcut for click. 

Multiple-Row Selection Lists 

Another kind of selection list lets you select multiple items for inclusion 

in additional processing. When you click the row, selection is indicated by 

an asterisk. The following figure illustrates a selection list in Installed 

Item Move (11.3.13) that displays an asterisk for selection. 


Fig. 2.28 

Item Master 

Maintenance 

(1.4.1), Cost 

Element Selection


Fig. 2.29 

Installed Item 

Move (11.3.13) 

Asterisk 

indicates 

selection. 

Click row 

to select. 

In this kind of list, clicking the row (or pressing spacebar) toggles the 

display of an asterisk, indicating selection. When a list supports multiple 

selections, you can select as many rows as you want this way and then 

click Next to continue. 

Navigating in Selection Lists 

When a selection list displays, focus is always initially on the first row. To 

change focus, use the mouse or Tab key. When items to select span 

multiple pages, use the Actions link right-click to display the Actions 

menu that includes Page Up and Page Down commands for displaying the 

next or previous page. You can also use the Page Up and Page Down keys 

to move through a scrolling list rather than choosing the commands from 

the Actions menu. 

Some selection list screens let you insert new rows and add associated 

data. In these lists, you can use the Insert command on the Actions menu 

or the Insert key.

Navigating HTML Screens with the Keyboard 

Most commands have keyboard options. The following table lists 

common keystrokes you can use within an HTML screen. 

Button/Link Keystroke Action 

Next Enter Submits current data and displays the next frame. 

Equivalent to Go in character and Windows 

interfaces. 

Back Ctrl+Enter Exits current frame. Equivalent to End in character 

and Windows interfaces. 

Delete Alt+D 

Ctrl+Shift+D 

Executes the Delete Record command when it is valid. 

Delete key In a text field, deletes a single character. 

Tab Move forward from field to field within a frame or 

from row to row within a selection list. 

Shift+Tab Move backward from field to field or from row to row 

within a selection list. 

Ctrl+Tab Move forward through open programs in the current 

workspace. 

Ctrl+Shift+Tab Move backward through open programs in the current 

workspace. 

Ctrl+F6 Move forward through open workspaces. 

Ctrl+Shift+F6 Move backward through open workspaces. 

Spacebar In a logical field, press spacebar to toggle the check 

box. 

In a multiple-row selection list, press spacebar to 

select (same as a left mouse click). 

Can also be used as End when focus is on the Back 

link. 

Up arrow In a field where next/previous processing is enabled, 

displays the previous record. 

Down arrow In a field where next/previous processing is enabled, 

displays the next record. 

Page Up key Displays the previous group of records in a scrolling 

list. 

Page Down key Displays the next group of records in a scrolling list. 


Table 2.2 

Keyboard 

Navigation in 

HTML 

Maintenance 

Programs


Button/Link Keystroke Action 

Insert Opens a new row in a scrolling list. 

Alt+I 

Ctrl+Shift+I 

Executes the Insert command when it is valid. 

Alt+L Displays either the lookup or calendar associated with 

the current field. 

Alt+B Displays the drill-down selection box for the current 

field. In the selection box, select a drill-down option 

by using the up or down arrow keys and then pressing 

the Enter key. You can also click on a drill-down 

option using the mouse. 

F1 Displays help for current field and program. 

Understanding Messages in HTML Screens 

Most MFG/PRO application messages fall into the following categories: 

• Errors. These display in separate browser alert boxes. Click OK to 

continue. 

• Warning and informational messages. These display in the message 

area of the program screen that is executing. 

• Warning and confirmation prompts. These require a Yes or No 

response and display in a browser alert box. Click the Yes or No 

button to continue. 

Occasionally, the system may also display messages about internal 

problems. These messages display when there are problems displaying 

the HTML screens, or when one or more components of the system are 

not responding. For example, a message displays when the system cannot 

make a connection to the database to execute the user request. 

These messages are described in detail in Installation Guide: QAD User 

Interfaces. Addressing the problem indicated in the message may require 

the intervention of a system administrator.

Using HTML Reports and Inquiries 

Reports and inquiries in QAD .NET UI display in HTML screens just like 

maintenance programs. 

Some programs both update the database and produce report output. 

These programs display in the same way as other HTML reports. Sales 

Order Print (7.1.3) is an example of a program that generates output and 

updates the Print field in the sales order record. 

You use and navigate HTML report programs like maintenance programs 

with a few exceptions. 

HTML Report Output 

In HTML programs that generate report output, you choose an output 

device. In general, you can use any device previously defined in Printer 

Setup Maintenance (36.13.2). However, if you want to display the report 

output on your terminal, you must select a device that has Scroll Output 

set to Yes in Printer Setup Maintenance. 

Typically, you can use the Page option, which is a system default that has 

Scroll Output set to Yes. Or you can define another printer with this 

setting. You can also use the Email option in HTML reports and inquiries. 


Fig. 2.30 

HTML Report


Fig. 2.31 

Output to Page 

Fig. 2.32 

Canceling a Report 

Important Output to terminal is not supported in HTML screens. 

Cancel HTML Reports 

In other interfaces, you can use the Ctrl+C key combination to stop a 

report that is currently processing. 

Click to stop an executing report. 

In QAD .NET UI, this key combination has no effect. Instead, a Cancel 

button displays. Click the Cancel button to stop the report. You can also 

use the close button in the program title bar to stop the report execution. 

Using Character Terminal Screens 

You can run any program in the QAD .NET UI using a character display. 

By default, the display mode is determined by settings in Program 

Information Maintenance (36.3.21.1). Each user can change this setting 

on a program-by-program basis using the Open With option on the

Properties dialog. These choices are retained from session to session for 

all workspaces. See “Menu Properties” on page 22 for an illustration of 

this drop-down. 

Any program that is not defined in Program Information Maintenance 

automatically displays in the character UI. 

The functionality of a program displayed in a character screen is exactly 

the same as the program with an HTML screen; only the appearance and 

UI features are different. 

Note While you can have many instances of an HTML screen open, you 

cannot run two instances of the same program in the character UI. 

You can use standard function keys to navigate in character programs. A 

status line at the bottom of the screen displays active function keys. 

Character screens automatically resize to fill the available application 

space. You can use the mouse to select text on the screen to paste into 

another application. Otherwise, you cannot use the mouse to navigate 

character programs. 

You can also use the Print and Print Preview commands to send images of 

character screens to an output device. 


Fig. 2.33 

Character Screen


Table 2.3 

Character 

Keyboard 

Commands 

Using Other Keyboard Commands 

You can use the keys listed in the following table to navigate and 

complete other actions. 

Note You cannot use the F6 or Ctrl+P keys in the Desktop to access the 

user menu. Instead, add these programs to your Favorites. 

Keyboard Control 

Commands Entry Key Entry Description 

Enter Enter Move to next field within a frame 

Tab Tab Move to next field within a frame. 

Back Ctrl+U Move back one field within a frame. 

Go F1 Ctrl+X Move to next frame. 

Help F2 Display lookups, field help, and program help. 

Insert F3 Ctrl+T Toggle insertion mode. 

End F4 Ctrl+E Move to previous frame. 

Delete F5 Ctrl+D Delete a record. 

Clear Shift+? 

Clear the value in date fields. Use F8 to clear 

F8 

any field. 

Previous F9 or up Ctrl+K Retrieve previous record in a key data field 

Record arrow 

and scroll up in lookup. 

Next F10 Ctrl+J Retrieve next record in a key data field and 

Record 

scroll down in lookup. 

Copy/Paste F11 Ctrl+B Copy a value or paste a previously copied 

value. 

Multiple F12 Ctrl+A Copy values from one or more fields and paste 

Copy 

them into the same fields of another record. 

Field Ctrl+F Display technical information about the 

Information 

current field and the executing program. 

Requesting Application Help 

Use the F1 key in a field in an HTML program to display application help 

for the active program and field. Program help describes a menu-level 

function, how it is used, and how it relates to the rest of the system. Field 

help describes the purpose and use of an individual field in a program.

Note Generally only maintenance programs have program help—not 

reports and browses. 

The following figure illustrates the page displayed when you request help 

in Sales Order Maintenance. 

Click a field name 

to display its help 

information. 

Application help displays in a tri-pane window in a new tab. 

• Use the left pane to display help for a field associated with the 

program. 

• Use the top right pane to navigate to a list of programs. You can click 

a program in this list to display its help. 

• Use the bottom right pane to view the program help for the current 

program. 

Displaying Field and Tool Tips 

Field tips display automatically when you position your cursor over a 

field. The field tip displays the associated Progress field name. 

Tool tip descriptions display when your cursor is positioned over a tool 

button. The tool tip indicates the action associated with the button. 

Tool tips also display when your cursor is positioned over a menu item in 

the menu when you are in search mode. The tips display the position of 

the menu in the menu hierarchy. This is useful when a menu item occurs 

more than once in the menu structure. 


Fig. 2.34 

HTML Application 

Help


See Figure 1.15 

on page 27. 

Fig. 2.35 

Menu Tool Tip 

Note You can also use the Find in Menu right-click option to open the 

menu where the currently found menu item is located. 

Creating Custom Links 

QAD .NET UI lets you customize the interface by adding links on a 

program screen that let you access other programs. 

Note System administrators can customize and extend the interface in 

many other ways. These are discussed in Chapter 3, “Simplifying HTML 

Screens,” on page 87 and Chapter 5, “Configuring Administrative 

Settings,” on page 133. 

To add links on a program screen to another program, complete the 

following steps: 

1 Open the program you want to update. 

2 Click Program Links at the bottom of the program screen and choose 

Add more links. The User Tool Maintenance (36.20.4) screen 

displays in a separate browser window.

3 Specify your user ID if you want the program links to display only 

when you execute the parent program. Alternatively, leave the field 

blank to create a generic record of settings. This generic record is 

automatically associated with every user in the system that does not 

have a user-specific record. 

4 Enter the name of the program where you want the link to display. 

Leave Program blank to add the link to all programs that do not 

already have a user-specific record. Click Next to continue. 

5 Enter the name of the program you want to execute when you click a 

link in the Exec field. In the Label field, specify a text string to appear 

in the link area. If you leave this field blank, the standard menu 

description from Menu System Maintenance is used. 

Leave the Image field blank. Images do not apply in the QAD .NET 

UI. 


Fig. 2.36 

User Tool 

Maintenance 

(36.20.4)


Fig. 2.37 

Browse 

Maintenance 

(36.20.13) 

Using Special UI Features 

This section covers a number of topics related to areas where the 

programs in the QAD .NET UI have different features than the character 

UI or special behavior. 

Using Browse Maintenance 

In MFG/PRO, you use Browse Maintenance (36.20.13) to create browses, 

which display selected data in the form of a table. Browse Maintenance 

has some special features that are not available in the character UI and 

that are not like other HTML programs. This section describes these 

features. 

For complete details on this function, see User Guide Volume 9: Manager 

Functions. 

The following figure illustrates Browse Maintenance as an HTML 

function in the QAD .NET UI. In the first frame, you specify the browse 

name.

Click Next or click the second tab, Browse Data, to continue. Enter data 

in the Browse Data tab the same way you enter data in the character 

interface. Specify an associated label term for the browse title and 

indicate the type of browse—power browse, look-up browse, or both. 

Then enter the name of a view or primary table with browse data, and any 

filter criteria for limiting the data that displays. 

Click Test to preview each browse. 

The Preview function, accessed with a button in the character user 

interface, is accessed by clicking the Test link in the Browse Data screen. 

This displays the currently edited browse in a detached window. For 

existing browses, you can preview the browse before changing it. 

Use the Field Select tab to select fields to be included in the browse and 

specify the display order. 


Fig. 2.38 

Browse 

Maintenance, 

Browse Data


Fig. 2.39 

Browse 

Maintenance, Field 

Select 

Move fields between lists using the horizontal arrows. 

Fields from the view or primary table entered in the Browse Data tab 

display in the Available column. You can include up to 20 fields in a 

browse. 

Move fields from one list to another by clicking the field to select it and 

clicking the arrow that indicates the appropriate direction. Multiple fields 

can be selected by holding down the Shift key and clicking. 

In the Selected column, use the up and down arrows to arrange the order 

of the fields. This determines the order of the fields in the browse, from 

left to right. 

To specify sort columns—for look-up browses only—select one or more 

fields in the Selected column and click the right arrow to move them to 

the Sort Order column. You can use the up and down arrows to reorder the 

fields in the Sort Order list. The look-up browse sorts the records on the 

first column you enter in the Sort Order field. 

Click Next to display the Details tab. 

Change 

the sort 

order 

using the 

vertical 

arrows.

Choose the field in the browse with values you want to use from the dropdown 

list associated with the Value-Returned Column field. The default is 

the first column of the browse. 

To view the details related to a specific field, select it from the drop-down 

list in the Detail field. 

If needed, you can change the default field label and format. To control 

the display length of a label, enter a Max Length value. Click Back if you 

want to view or modify data for other fields. Otherwise, click Next to 

display the browse history. 


Fig. 2.40 

Browse 

Maintenance, 

Details


Fig. 2.41 

Browse 

Maintenance, 

History 

The program automatically creates a revision history line containing a 

revision number, the user name (or logon ID), and current date. You can 

modify this as needed. The revision history is also saved in the source 

code. 

Note The Procedure field offers other choices; only History is currently 

implemented. 

Click Test to preview the browse after making changes and before saving 

the changes permanently. Click Save to save the browse. To discard your 

changes without generating the browse program, click Back. 

Using Fixed Assets Programs 

Some programs in the Fixed Assets module include additional navigation 

buttons that are used to modify information or access additional screens 

with a program. For example, Fixed Asset Maintenance (32.3) includes 

multiple navigation buttons in the QAD .NET UI.

Add is the currently active button, as indicated by the darker frame 

around it. You can use the Tab key to move forward between the buttons 

and Shift+Tab to move backward. Press the spacebar to execute the 

function associated with the active button. 

Note Pressing Enter is the same as clicking Next. This typically has no 

effect when the buttons are active. 

The End button and the Back link execute the same function; similarly, 

the two Delete buttons execute the same function. 

Transaction Comments 

Programs such as Sales Order Maintenance, Purchase Order 

Maintenance, and Work Order Maintenance include the option to enter 

comments. 

Comments have a limit of 15 lines. You can cut, copy, and paste ASCII 

text. In general, any rich text formatting is removed from copied text 

when the text is pasted. 


Fig. 2.42 

Fixed Asset 

Maintenance (32.3)


Note When you are in the comments field, pressing Enter places a 

carriage return in the entered text. If you are not in a comments field, 

pressing Enter submits the current data and advances you to the next 

frame (or screen), the equivalent of clicking the Next button on the 

screen.

Chapter 3 

Simplifying HTML 

Screens 

Read the following topics to learn how to use administrative tools to 

simplify the appearance of selected MFG/PRO functions. 


Planning Template Design 90 

Administering Simplified Screens 92 

Creating a UI Template 96


Table 3.1Screens 

that Can Be 

Simplified 

Introduction 

When MFG/PRO programs run under the QAD .NET UI, screens provide 

the enhanced usability features of HTML— but, otherwise, look like the 

same screens that display when programs run in the character user 

interface. However, QAD provides a design tool for tailoring and 

simplifying HTML input screens. Currently, this tool can only be used 

with the set of programs listed in the following table. 

Menu Number Description Program Name 

1.4.1 Item Master Maintenance ppptmt.p 

2.1.1 Customer Maintenance adcsmt.p 

2.3.1 Supplier Maintenance advnmt.p 

3.7 Issues - Unplanned icunis.p 

3.9 Receipts - Unplanned icunrc.p 

3.10 Receipts - Sales Order Return icsorc.p 

3.11 Receipts - Return to Stock icrsrc.p 

3.12 Receipts - Backward Exploded icunrc01.p 

3.14 Cycle Count Results Entry icccaj.p 

3.4.1 Transfer - Single Item iclotr02.p 

3.4.3 Transfer With Lot/Serial Change iclotr03.p 

5.2.3 Requisition Maintenance rqrqmt.p 

5.3.1 Blanket Order Maintenance poblmt.p 

5.7 Purchase Order Maintenance popomt.p 

5.13.1 Purchase Order Receipts poporc.p 

7.1.1 Sales Order Maintenance sosomt.p 

7.3.13 Scheduled Backorder 

Maintenance 

rcsomt.p 

7.9.1 Picklist/Pre-Shipper – Automatic sososl.p 

7.9.13 Sales Order Packing List sosopk.p 

7.12.1 Sales Quote Maintenance sqqomt.p 

7.13.1 Pending Invoice Maintenance soivmt.p 

10.5.13 Project Activity Recording 1 

pjcarmt.p 

11.1.1.1 Call Maintenance fscamt.p 

11.1.1.13 Call Activity Recording 1 

fscarmt.p 

11.7.1.1 RMA Maintenance fsrmamt.p

Menu Number Description Program Name 

12.17.19 Distrib Order Picklist Print dsdopk01.p 

14.13.1 Routing Maintenance rwromt.p 

16.6 Work Order Release/Print woworl.p 

16.7 Multiple WO Release/Print woworl01.p 

16.10 Work Order Component Issue wowois.p 

16.11 Work Order Receipt woworc.p 

16.12 Work Order Receipt Backflush 1 

wowoisrc.p 

16.19 Work Order Operation Backflush 1 wobkfl.p 

17.1 Labor Feedback by Work Order sfoptr01.p 

17.2 Labor Feedback by Employee sfoptr02.p 

17.3 Labor Feedback by Work Center sfoptr03.p 

17.4 Non-Productive Labor Feedback sfoptr04.p 

17.5 Operation Complete Transaction sfoptr05.p 

17.6 Operation Move Transaction sfoptr06.p 

17.7 Operation Scrap Transaction sfscrap.p 

17.22.16.4 Kanban Card Print kbcdrp03.p 

17.22.16.5 Kanban Multi-Card Print kbcdrp01.p 

18.22.13 Backflush Transaction rebkfl.p 

18.22.14 Run Labor Transaction relbr.p 

18.22.15 Setup Labor Transaction reset.p 

18.22.16 Reject Transaction reject.p 

18.22.17 Rework Transaction rework.p 

18.22.18 Scrap Transaction rescrap.p 

18.22.19 Move Transaction remove.p 

18.22.20 Down Time Transaction redt.p 

18.22.21 Wip Adjust Transaction rewadj.p 

18.22.22 Non-productive Labor Feedback renplf.p 

28.1 Voucher Maintenance apvomt.p 

28.8.1 Recurring Voucher Maintenance aprvmt.p 

1. Although you can simplify the user interfaces for these programs, you 

cannot set the defaults. 

Simplifying HTML Screens 89


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, 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 

MFG/PRO 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. 

Planning Template Design 

Simplifying screens enables you to help the individuals who use 

MFG/PRO 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 MFG/PRO design, 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: 

Generalized codes validation. Many MFG/PRO programs support the 

used 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. 

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. 

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. 

Error Handling 

To help you during testing, an additional message displays when a 

program error is generated because a template does not allow entering a 

field that is validated by MFG/PRO. 

For example, a frame can have a field that is validated by MFG/PRO. If 

that field is hidden so that the user cannot supply a value, the user will not 

be able to proceed through the program. 

In this case, the system displays additional information with the error 

indicating that a simplified screen setting caused the error, like the 

following example: 

The following error was caused by a simplified screen 

setting. Please contact your System Administrator. 

ERROR: Country code does not exist. Please re-enter 

If automatic navigation is specified for a frame but default values are not 

specified for fields that cannot be blank, the automatic submit will fail. 

The frame remains hidden and the user cannot proceed within the 

program. This ensures that users are not allowed to see restricted 

information. 



See “UI Template 

Conflicts” on 

page 94. 

Assigning Templates to Groups 

A set of changes to a particular program’s user interface is stored as a 

template. Templates are then assigned to user groups. Groups are defined 

in User Group Maintenance (36.3.4) and then assigned to users in User 

Maintenance (36.3.1). The system displays all groups defined in User 

Group Maintenance. 

In addition, you can assign a generic template to all users. The system 

activates a template assigned to all users only when a specific template is 

not assigned to users, based on their group membership. 

Specific group assignments always take precedence over generic 

templates. However, it is still possible for a user to belong to more than 

one group with different assigned templates. The system handles this by 

using the template of the first group assigned to the user. 

The system also creates an XML file for every conflict. The UI Template 

Conflicts administrative function lets you view these conflicts and 

manually determine which template should be used, as needed. 

When you design your templates, you should plan how you want to assign 

users and determine if your existing groups accommodate the way you 

want to develop your templates. Since security groups often reflect 

functional responsibility within an organization, they typically already 

represent different views of an organization that can be supported by 

different templates. 

However, you may find that you need to add new groups to be able to use 

templates to the best advantage in your particular implementation. 

Administering Simplified Screens 

To open the Simplified Screens utility, select Administration|Simplified 

Screens. 

You can manage two sets of values: 

• Simplified screens setup 

• UI template conflicts

See Installation Guide: QAD User Interfaces for full details about 

administration. The installation guide also includes details about 

directories and servers. 

Since creating simplified screens is an administrative function, access to 

the UI Template Setup tool is restricted. Only members of a specific 

MFG/PRO user group can create and modify templates. You should 

create this group and assign it to users in User Maintenance before 

implementing simplified screens. Once you have done this, specify this 

group as the UI Design Group in the Simplified Screens Setup screen, 

described next. 

Note Three user groups have special responsibilities for managing the 

QAD user interface: 

• The group set during installation that can access the UI 

Administration page for managing system processes 

• The group that has access to the Process Editor, which must be named 

pronav 

• The group authorized to create UI templates 

The information associated with each template is stored in XML files 

located in: 

NETUIInstallDir/com/mfgpro/configxml/qaddb 

Simplified Screens Setup 

Use the following screen to administer simplified screen setup. 

Simplifying HTML Screens 93 

Fig. 3.1 

Simplified Screens 

Setup


You must specify values for two fields. 

Enable Simplified Screens. Select this field to enable members of the 

group specified for UI Design Group to create screen templates and 

assign them to users. 

Enabled: Members of the UI design group can create templates, and 

templates assigned to user groups are active when those users access 

the associated program. 

Disabled: Templates cannot be created and any that exist are not 

active even if assigned to users. 

UI Design Group. Enter the name of a user group in MFG/PRO that is 

authorized to create and modify screen templates. Only members of 

this group can create simplified screen templates. 

Predefine groups in User Group Maintenance (36.3.4) and then 

associate them with users in User Maintenance (36.3.1). 

Important You cannot associate templates with members of this group. 

UI Template Conflicts 

Use the UI Template Conflicts screen to resolve conflicting template 

assignments. These conflicts can occur because users in MFG/PRO 

belong to more than one group. 

Example John Smith belongs to the Sales1 user group and Manager1 

group. The UI designer creates a UI template for Sales Order 

Maintenance and assigns it to group Sales1. The designer also creates a 

second Sales Order Maintenance template for managers and assigns it to 

group Manager1. When John logs in and uses Sales Order Maintenance, 

the system has no way of knowing which version of the UI to present. 

In these situations, the system uses the template associated with the first 

group assigned to the user. However, this may not be what you want or 

expect. The system also creates an XML file with the conflict 

information. You can view and manage these conflicts using the UI 

Template Conflicts function, accessible from the Simplified Screens table 

on the Simplified Screens Admin screen.

The UI Templates Conflict screen lists all users that belong to more than 

one group with an assigned template. The administrator can use the dropdown 

list in the Conflict column to select the group assignment that the 

system should prioritize. 

Impact of MFG/PRO Changes 

UI templates are based on the order and organization of a specific user 

interface. Certain changes to MFG/PRO screens can invalidate existing 

UI templates resulting in unexpected behavior during execution. These 

changes include: 

1 Key fields are added or removed. 

2 The initial focus field or the first field of a frame is changed. These 

fields are points of reference for other field information in the 

template. 

3 The internal Progress frame name is changed. 

4 The location of a frame on the screen is changed; for example, 

moving a frame from the top of the screen to the bottom. This 

changes the x and y coordinates of the frame, which are used as 

location identifiers. 

These types of changes are not common. However, you should be aware 

of this possibility when: 

• You customize any supported programs. 

• You install MFG/PRO service packs or upgrade MFG/PRO releases. 

Be sure to check the release notes provided with the release or service 

pack to see if these kinds of program changes occurred. 

The following kinds of UI changes do not adversely affect UI templates: 

1 Adding or removing fields from frames, other than the initial focus 

field or first field mentioned previously. 

2 Adding or removing frames. 

3 Changing the sequence that frames appear as long as the frames 

remain in the same screen location. 



Fig. 3.2 

Selecting Design 

Mode 

See “UI Design 

Group” on 

page 94. 

Creating a UI Template 

When you simplify screens, you create templates and assign them to user 

groups. Each template defines how fields display, whether they are 

required and enabled, if default values are supplied, and any automatic 

navigation from frame to frame. 

To create a new template, select one of the supported programs in the 

menu system, such as Customer Maintenance. Right-click to display 

options and choose Design. 

When you right-click on Customer Maintenance, you can select the 

Design option from the list. 

Click to begin creating or 

modifying a template. 

Note This option is enabled only when you are logged in as a member of 

the UI Design Group. 

To move through the sequence of frames in a program, you must either 

create a new record or modify an existing one. However, when you are in 

simplify mode, none of the changes that you make to database records are 

saved. You use the record simply as a way to move through the screen. 

In cases where new records are assigned sequential numbers, it may be 

better not to create new records. Although the records are not saved, 

number sequences are incremented. For example, if you create a new 

sales order in simplify mode, the new order is not saved. However, the 

next sales order number in Sales Order Control (7.1.24) is incremented, 

leaving a gap in sales order numbers.

On the other hand, testing of template changes is simplified when you 

create a new record, rather than editing an existing one. When a new 

record is created, many fields that require data may be initially blank. For 

an existing record, these would already have values. If you hide a required 

field and test with an existing record that has a field value, no error is 

generated. Later when a user attempts to create a new record, template 

errors may occur because a field that needs input cannot be updated. 

Important To support rolling back changes when you exit simplify 

mode, some database records may remain locked during the entire time 

you are in simplify mode. 

To reduce any adverse effects of record locking on other users of the 

system, designers should create and modify UI templates when other 

users are not actively using the system. 

Creating a Template 

When you choose the Design option, the UI Template Setup screen 

displays. Using this screen, you can modify an existing template or create 

a new one. 


Fig. 3.3 

UI Template Setup 

Screen


To create a new template, follow these steps: 

1 Click New under the Templates list. A new template with the default 

name New Template is created and automatically selected for editing. 

2 Modify the template name and description to indicate its purpose. 

You can use any characters in your name and description. Name can 

be up to 40 characters and description up to 60. 

3 Indicate if you want this template to be a generic template assigned to 

all users. If you want this template to be used whenever a more 

specific one is not found, select the Assign to all users check box. 

When this option is selected, you cannot assign any specific groups. 

4 If this is not a generic template, select one or more user groups to 

assign to this template. The Select Groups list displays all defined 

groups in the system except for the one that has been designated as 

the UI design group. 

• Click Select All if you want to assign all user groups to the 

template. 

• Click Deselect All to clear selection from all groups. 

• If you have many groups in your system, click Show Selected to 

see only the groups that are currently assigned to a template. 

5 Click Save to save the template summary information. You must save 

the template before you can begin modifying the program fields. 

Click Simplify to begin the process of defining the template content, 

described in the next section. 

To modify an existing template, select it from the list. You can change its 

name, description, or assigned groups. Then click Simplify to enter the 

associated program in simplify mode. You can also delete a template by 

selecting it and clicking Delete. 

Simplifying Program Screens 

To begin simplifying program screens and frame navigation for a specific 

template, select the template and click Simplify in the UI Template Setup 

screen. The program opens with a green check mark over the Simplify 

button.

Running in simplify mode 

You can click the Simplify button at any time to save your changes and 

leave simplify mode. Your changes are also saved each time you click 

Next or Back to access a new frame. 

You access the commands to modify screen behavior in several ways: 

• Right-click in a field for a menu of actions that apply to the field. 

• Right-click on the screen for a menu of actions that apply to the 

frame. 

• Choose the option you want from the Action menu at the bottom of 

the screen. 

• Use the Auto Next and Auto Back check boxes for frame level 

options. 

The following figure illustrates the menu that displays when you rightclick 

in a field. 


Fig. 3.4 

Executing 

Customer 

Maintenance in 

Design Mode


Fig. 3.5 

Accessing UI 

Options 

UI field 

options 

UI screen 

navigation 

options 

The top commands—Hide Field, Disable Field, Required, and Default— 

apply to the field that is currently in focus and are only active when you 

right-click a field. The bottom commands—Auto Next and Auto Back— 

affect the navigation through the frame and are active when you rightclick 

outside a field in a frame.

You can simplify all types of fields in a frame except for fields that are 

represented with drop-down lists, as the Line Format field in Sales Order 

Maintenance (7.1.1) 

None of the field-level commands can be used with this type of field. 

When you right-click the Line Format field, the commands are disabled. 

Modifying Field Behavior 

Use the following options to modify field behavior: 

Hide Field. This field does not display to the user assigned this 

template. In simplify mode, it is shown with gray hash marks. 

Disable Field. Users cannot update this field. In simplify mode, it is 

shown in gray. 

Required. Users cannot click Next through the current frame without 

supplying a value for this field. In simplify mode, the field is marked 

with a red asterisk (*). The field is also marked with a red asterisk 

when the user executes the program. 


Fig. 3.6 

Drop-Down List in 

Sales Order 

Maintenance 

(7.1.1)


Default. The value you specify in this field displays as a default value 

when the user is creating a new record in the associated program. 

Users can change the default value, unless the field is also disabled or 

hidden. In simplify mode, the default value displays in red type. 

Defaults you specify for a template override any other defaulting 

logic associated with a field. 

Note Defaults are only applied to new records; when a record is 

being edited, no field values are overridden. 

You can assign more than one option to a field; for example, you can 

provide a default value for a field as well as disabling or hiding it. 

If you plan to mark fields as required, you should consider marking all 

fields that are validated by the MFG/PRO application logic that way—not 

just additional ones that are required for your particular implementation. 

This will prevent users from being confused about why some fields 

without asterisks are also required. 

Modifying Screen Navigation 

Another option you can use to simplify data entry is to skip entire frames. 

You do this using the Auto Next and Auto Back options. 

Important Do this only with careful planning since in order to skip an 

entire frame without generating an error, the proper defaults must exist for 

all required fields. 

Auto Next and Auto Back have the same effect; use them to skip the 

display of a frame. Which one you use depends on the normal screen 

navigation. To proceed from one frame to the next, you normally use the 

Next command. However, when you are in a frame that lets you enter 

multiple lines—such as sales order detail or customer banks—you use the 

Back command to indicate you are through entering lines and ready to 

display the next frame. 

So, for example, if you do not want a particular user group to modify bank 

accounts associated with customers or even see them, set the Auto Back 

option on the Bank Accounts frame in Customer Maintenance. When 

users execute the program, that frame does not display.

Note Typically, Auto Next and Auto Back prevent the display of a 

frame. However, in some cases, the screen may be visible before the 

navigation reaches that point. For example, if you set Auto Next on the 

bottom frame of the first screen in Customer Maintenance, the frame will 

still be visible when the screen is launched. When the user navigation 

reaches that frame, it will then be skipped. 

The following figure shows the multiple salesperson frame in Customer 

Maintenance with Auto Next enabled. This frame does not display to 

users assigned this template. 

In this figure, Auto Back has been enabled in the Bank Accounts frame. 

Auto Back in this frame has the same effect as Auto Next in the multiple 

salesperson frame. 

Auto 

Back 

enabled 


Auto Next 

enabled 

Fig. 3.7 

Using the Auto 

Next Option 

Fig. 3.8 

Using the Auto 

Back Option


Chapter 4 

Using the 

Process Editor 

This chapter discusses how to use the Process Editor to design and 

maintain custom process maps for use with the QAD .NET User 

Interface (UI). 


Getting Started with the Process Editor 109 

Using Process Options 113 

Associating URLs with Processes 116 

Using Property Editors 118 

Accessing Processes 127 

Administering the Process Editor 129


Introduction 

MFG/PRO is a flexible product designed to adapt to specific requirements 

of individual users. As a result, MFG/PRO applications can be used in 

many different ways. 

The Process Editor in the QAD .NET UI lets users build models of their 

work processes. These models are essentially clickable image maps that 

have associated URLs. The URLs can point to various resources such as 

images, video, audio, and documents, as well as to MFG/PRO programs 

to execute. Any application that can be viewed in a browser can be 

associated with one of the locations on a process map. 

Note To access the Process Editor, users must belong to the pronav user 

group defined in MFG/PRO security functions. In general, the 

QAD .NET UI only displays Administration programs such as the 

Process Editor for users who have security privileges or who are members 

of a defined administration group. 

Scalable Vector Graphics 

The Process Editor relies on the scalable vector graphics (SVG) format, a 

new XML technology for defining vector-based two-dimensional 

graphics for the Web. SVG was developed by the World Wide Web 

Consortium (W3C), which promotes standards for the Web and 

interoperability among Internet products. 

SVG has many advantages over other image formats commonly used on 

the Web today such as Joint Photographic Experts Group (JPEG) and 

graphics interchange format (GIF): 

• Plain text format. SVG files can be read and modified by a range of 

tools and are usually much smaller and more compressible than 

comparable JPEG or GIF images. 

• Scalable. Unlike bitmapped GIF and JPEG formats, SVG is a vector 

format, which means you can print high-quality SVG images at any 

resolution, without the distortion common to printed bitmapped 

images. 

• Zoomable. You can zoom in on any portion of an SVG image and not 

see any degradation.

• Searchable and selectable text. Unlike bitmapped images, text in an 

SVG image is selectable and searchable. For example, you can search 

for specific text strings, such as city names in a map. 

• Scripting and animation. SVG supports sophisticated dynamic and 

interactive graphics. 

• Open standard. SVG is an open recommendation developed by a 

cross-industry consortium. Unlike some other graphics formats, SVG 

is not proprietary. 

• True XML. SVG offers all the advantages of XML, including 

interoperability, internationalization (Unicode support), and wide tool 

support. In addition, you can: 

• Manipulate SVG files through standard APIs, such as the 

Document Object Model (DOM). 

• Transform SVG files through XML Stylesheet Language 

Transformation (XSLT). 

For additional details, visit the Adobe SVG Zone: 

http://www.adobe.com/svg/ 

Sample Process 

A number of sample processes are provided with the QAD .NET UI that 

illustrate process flows. The Processes applications menu includes sample 

processes you can use. 

Using the Process Editor 107 

See “Accessing 

Processes” on 

page 127.


Fig. 4.1 

Sample Production 

Process 

Figure 4.1 illustrates a sample production process. 

Processes are built with two basic components: 

• Nodes are represented by various shapes and typically indicate a step 

within the process. 

• Connectors are lines with arrows that indicate the direction of 

execution for the steps (nodes) within the process. 

Managing Process Files 

The Process Editor looks for processes by default in a directory on the 

Web server. This directory name and location can be modified during 

installation, if needed. 

Note SVG files created with the Process Editor can be modified using 

other applications and text editors. However, this is not recommended. 

When you deploy process files for use, you can move them to another 

directory relative to the installation directory. This is recommended if you 

have many processes.

Getting Started with the Process Editor 

To open the Process Editor, select Administration|Process Editor. 

Figure 4.2 illustrates the Process Editor. 

The Process Editor has three parts: 

• On the top are options for creating a new process, opening a process, 

saving a process, previewing a process in the browser, and displaying 

help in the form of an online version of this chapter. 

• On the right, a grid displays the process being created or maintained. 

• On the left, various property editors let you modify aspects of a 

process. Use a different property editor for process information, 

process properties, nodes, connectors, styles, and the process grid. 


Fig. 4.2 


See “Using 

Property Editors” 

on page 118.


Some editors become active only when the appropriate object is 

selected. For example, the Node Properties editor is available only 

when a node is selected. 

Before you begin creating processes, you can update default properties, or 

use those supplied with the system. You can: 

See page 120. 1 Define the appropriate size for the drawing grid. 

See page 121. 2 Set up styles you want to use. 

See page 116. 3 Set up any variables needed for URLs. 

To begin creating a process: 

1 Click in the grid to add a node with the default rectangular shape. 

2 Use Node Properties to modify the node and assign other values. 

3 To add a connector, select the first node by clicking. Hold down Shift 

and click the second node. A connector is added pointing from the 

first to the second node. 

4 Use the Connector Properties to modify the connector and assign 

other values. 

To delete a node or connector: 

1 Click the node or connector to select it. 

2 Press the Delete key on your keyboard or right-click the node and 

choose Delete from the context menu. 

Using Process Editor Context Menus 

You can use two context menus when creating and previewing processes: 

• If you right-click while pointing to a node or connector, a menu of 

Process Editor commands displays. 

• If you right-click anywhere in Preview mode, a menu of SVG 

commands displays.

Using Process Editor Commands 

Figure 4.3 illustrates the context menu that displays when you point to a 

node or connector and right-click the mouse. 

• Choose Cut to remove the currently selected node or connector and 

keep its properties in memory to be pasted. 

• Choose Copy to copy the attributes of the currently selected node or 

connector into memory. 

• Choose Delete to remove the currently selected node or connector. 

• To use Paste, do the following: 

• Right-click a node or connector and use Cut or Copy to put its 

attributes in memory. 

• Select an existing node or connector. If you want to create a new 

node or connector with the copied attributes, first create the node 

by clicking in the grid or create the new connector by clicking the 

first node and Shift-clicking the second. 

• Now, right-click the new node or connector to display the context 

menu. 

• Choose Paste. 


Fig. 4.3 


Context Menu


Fig. 4.4 

SVG Context Menu 

Using SVG Commands 

You can use standard SVG commands to manipulate images in Preview 

mode when viewing the SVG file in the browser. 

• Panning. Hold down Alt and click-and-drag with the mouse to pan an 

SVG image. When the scroll lock is enabled, you can use the arrow 

keys to pan the image. 

• Zooming. Hold down Ctrl and click to zoom in at the mouse pointer 

location. Hold down Ctrl and click-and-drag to select a region to 

zoom into. Hold down Ctrl and Shift and click to zoom out. 

You can also use the zoom commands in the context menu. Right-click in 

the SVG image area to open the contextual pop-up menu. 

Figure 4.4 illustrates the context menu that displays when you right-click 

in preview mode. 

This displays the commands and options for interacting with the image. A 

Help command is included on the pop-up menu. Use it to display more 

extensive help about SVG commands.

Using Process Options 

Links at the top of the Process Editor let you execute the following 

options: 

• Create a new process. 

• Save a process. 

• Display a list of existing processes to open or delete. 

• Preview a process in your browser. 

• Display help in the form of an online version of this chapter. 

Creating a New Process 

To create a new process: 

1 Click New at the top of the Process Editor. The grid is cleared so you 

can begin defining a new process. 

2 Assign the process a name and optional description and owner; then 

click Save. Process names can contain letters, numbers, underscores, 

and hyphens; spaces are not allowed. 

3 Begin adding nodes and connectors as needed. 

Saving a Process 

Click Save at the top of the Process Editor to save your updates. If this is 

a new process, you must specify a name in Process Properties before you 

can save your changes. 


See “Process 


page 119.


Fig. 4.5 

Open Screen 

Opening a Process 

You can modify an existing process by opening it in the Process Editor. 

1 Click Open at the top of the Process Editor. The screen illustrated in 

Figure 4.5 displays: 

Click Name to sort 

processes by name. 

Arrow indicates direction of sort. 

2 To reorder processes, click a column heading to sort by that column. 

Click the same column heading for a reverse sort. The arrow next to 

the primary sort column name indicates the direction of the sort 

(ascending or descending). 

3 Click the name of the process you want to edit. The process displays 

in the grid and the Open screen is closed. 

4 If you leave the index open for a period of time, click Refresh to 

regenerate the index based on your latest changes.

Deleting a Process 

To delete a process: 

1 Click Open at the top of the Process Editor. The screen illustrated in 

Figure 4.6 displays: 

Click check box to select for deletion. 

2 Click the check box next to the name of the process you want to 

delete. Click multiple check boxes to delete multiple processes. 

You can sort columns to facilitate selection. 

3 Click Delete All Checked. 

4 You are prompted to confirm the deletion. Click OK to continue. 

5 The process file or files are removed from the operating system. 

Previewing a Process 

Click button to delete. 

Previewing a process lets you see the process the way users would see it 

in a browser. You can also test links to ensure they work correctly. If you 

are using variables defined with Process Properties, the variables are fully 

expanded during preview. 


Fig. 4.6 

Deleting Processes


See “Using SVG 

Commands” on 

page 112. 

To preview a process in the browser: 

1 Create a new process or open a process to preview. 

2 Click Preview at the top of the Process Editor. 

3 The process opens in a new browser window. All of the URLs that are 

part of the process are active. You can click them to test the related 

actions. In addition, images not viewable in the editor display in 

preview mode. 

Note Refreshing the preview page may generate an error. Return to the 

Process Editor and click Preview again to view the process. 

You can use standard SVG commands in preview mode. 

Associating URLs with Processes 

One of the powerful features of the Process Editor is its ability to 

associate URLs with nodes and connectors. These URLs can point to 

many different types of files. You can configure them to open in a new 

window, or replace the content in an existing window. 

You can use URLs to: 

• Execute audio files 

• Display movies 

• Open documents in portable document format (PDF) 

• Display images 

• Open Microsoft Word documents 

• Open catalogs, training material, and help files 

In addition to these external resources, processes typically link to other 

processes and MFG/PRO programs. For example, you can create nested 

processes that together build a more complex model. For example, the 

sales order processes illustrated in Figure 4.1, “Sample Production 

Process,” on page 108 could be nested under a larger order management 

process that incorporates sales orders, return material authorizations, and 

material orders.

When you specify a URL, you can enter the full path relative to your 

computing network. However, if you do this, you may not be able to use 

the processes if your network setup changes. You will also have problems 

executing them from other systems if you want to deploy them to multiple 

sites. 

To execute an MFG/PRO program from a process requires knowing the 

application program interface (API) for calling the program. 

To simplify the use of URLs and ensure that they are portable, you can 

use a set of variables when defining URLs. Values for these variables are 

defined in a file named process-config.xml. This file is located in: 

TomcatInstallDir/webapps/qaduiConfig/WEB-INF/conf/ 

process-config.xml 

These values can be updated if needed using the ProccessAdmin.html 

administration tool. All of the processes that use the variables are then 

updated automatically. 

Note In addition to variable values, process-config.xml contains 

default values for other process properties. These can also be modified if 

necessary. 

Four variables are supplied with the Process Editor. These variables have 

a global scope since they apply to all processes. They cannot be modified 

in the Process Editor. 

You can also create your own variables. The scope of user variables is 

local. They apply only to the current process. 

The following four variables are supplied with the Process Editor. These 

can be updated using Process Editor administrative function. 

• QAD_DT_IMG. Use this variable when you create URLs referencing 

graphics. The variable points to the images directory below the 

Desktop installation directory defined in QAD_DT_DOC_ROOT. 

• QAD_DT_DOC_ROOT. Use this variable in URLs to reference the root 

directory where Desktop is installed on the Web server. This directory 

is unique to each installation and has a form similar to the following: 

http://crsu04.qad.com:8080/desktop 

You can append other directories to this variable to locate specific 

resource files. 


See Installation 

Guide: QAD 

User Interfaces. 

See 

“Administering 

the Process 

Editor” on 

page 129. 


Properties” on 

page 126. 

See “Configuring 

Process 


page 131.


• QAD_DT. Use this variable in URLs to reference an MFG/PRO 

program to be run in the Desktop. This variable sets up the API 

between the process and Desktop, represented by the following 

command: 

QAD_DT_DOC_ROOT/run.html?id= 

Follow the variable with a valid MFG/PRO program name such as 

sosomt.p or menu number such as 7.1.1 to be executed when a user 

clicks the associated link. 

• QAD_PV. Use this variable in a URL when you want to reference 

another process. Its value has the form: 

ProcessViewer.jsp?ProcessName= 

Follow the variable with the name of a process created with the 

Process Editor. 

Using Property Editors 

Each of the property editors lets you define attributes for a different 

aspect of a process. 

• Use Process Information to assign a name and optional description 

and owner to a process. 

• Use Grid Properties to modify aspects of the grid used for creating 

and editing the process. 

• Use Style Properties to modify aspects of styles. Styles can be 

associated with nodes and connectors. They group characteristics 

related to the display of fonts, colors, and lines. 

• Use Node Properties to modify aspects of a node. 

• Use Connector Properties to modify aspects of a connector. 

• Use Process Properties to define local variables for use with URL 

links. Variables ensure that processes are portable and can be moved 

from one computing environment to another. 

The Process Information, Process Properties, Grid, and Style Properties 

editors are always available. The Node Properties editor displays only 

when a node is selected. The Connector Properties editor displays only 

when a connector is selected.

When all the property editors are open, the screen can be very full. Click 

the button in the upper right corner of the title bar of an individual editor 

to minimize it (see Figure 4.7). Click the button with the X to close the 

property editor. You can reopen it by clicking the editor name link at the 

bottom of the screen if necessary. 

Note Only Process Information, Process Properties, Grid, and Style 

Properties can be closed this way. The display of Node and Connector 

Properties is controlled by your selection in the grid. 

During one browser session, the current arrangement of the editors is 

saved in memory. If you close your browser and start a new session, the 

Process Editor displays with a default layout. 

Process Information 

Figure 4.7 illustrates Process Information. 

Click here to minimize. 

The Process Information editor lets you identify a process and its owner. 

To update process information: 

1 Assign the process a name. The process name is the physical file 

name on the operating system. You can use alphanumeric characters, 

hyphens, and underscores in the name; you cannot use spaces. You 

must assign a name before you can preview or save a process. 

2 Assign the process a description. You can use any characters in the 

description. Description is optional. 

3 Assign the process an owner. This is the person responsible for 

updating and maintaining the process. Owner is optional. 

Note Owner information is maintained within the process file. It 

does not indicate operating system file permissions, which are 

managed on the Web server. 


Fig. 4.7 

Process 

Information


Fig. 4.8 

Grid Properties 

Fig. 4.9 

Adding and 

Removing Grid 

Rows and Columns 

When you look for a process to open, you can sort by name, owner, 

description, or date last modified. 

Grid Properties 

Figure 4.8 illustrates Grid Properties. 

Use Grid Properties to: 

• Specify the number of rows and columns in the grid. A warning 

displays if your change would cause nodes or connectors to be 

deleted. 

• Modify the height and width of the grid in pixels. 

• Specify a zoom percentage. 

• Toggle the display of grid lines. 

• Toggle the display of header rows. These are the rows with numbers 

and letters that can be used to identify grid blocks. 

You can specify from 1 to 12 rows and columns in the grid. The default is 

6. If you specify a larger number, you may need to reduce the size of the 

cells in the grid or reduce the zoom percentage so that you can see the 

entire process definition as you work with it. 

If you are displaying header rows, you can also add and remove columns 

and rows directly within the grid. When your cursor hovers over the 

header row, a plus (+) and minus (–) sign appear. Click the plus to add a 

row or column; click the minus to remove it. 

Click to delete a row. 

Click to add a row.

Style Properties 

Use Style Properties to modify attributes of system-defined styles. 

Associate styles with nodes in Node Properties and with connectors in 

Connector Properties. Style attributes are immediately visible when 

applied to a node or connector in the grid. 

Three basic styles are predefined: 

• Connector is the default style associated with a connector. 

• Node is the default style associated with a node. 

• Mouse Over Node changes the style of a node when the mouse is 

pointing to it. 

Figure 4.10 illustrates Style Properties. 

1 Select the ID of the style you want to modify. 

2 Choose the font family associated with labels using this style. 

3 Choose the font style (normal or italic). 

4 Choose the font size (from 7 to 36 points). 

5 Choose the font weight (lighter, normal, bold, or bolder). 

6 Choose the stroke color to apply to fonts and lines. 

7 Choose the fill color for the node. 


Select options from dropdown 

lists. 

Preview colors. 

8 Choose a value for opacity. 1 represents a solid label. Decreasing 

values represent increasing transparency. 

Fig. 4.10 

Style Properties


Fig. 4.11 

Filter Effects 

See “Associating 

URLs with 


page 116. 

9 Choose a value for stroke width, measured in pixels. A higher value 

represents a wider line. 

10 Optionally select a value for filter, or leave the default None. The 

filter value lets you add special effects that determine how the node 

appears. This lets you add interest and variety to your process maps. 

Figure 4.11 illustrates a node with each of the various filters applied. 

Experiment with the various filters by applying them to a style and 

seeing their effect on a sample process. 

Adding or Modifying Styles 

Styles and their attributes are defined in the process-config.xml file, 

which is designed so that you can add additional styles or modify the 

default attributes of system-defined styles. Any changes you make to this 

file are reflected in the Style Properties editor. 

However, if you modify styles, be aware that the style attributes are 

embedded in the XML used to define a process. If you change a style that 

has already been used, existing processes are not affected. 

To change the style in an existing process, you must open it and change 

the style attributes in the Style Properties editor.

Node Properties 

Figure 4.12 illustrates Node Properties. 

Use Node Properties to modify attributes of nodes. 


Click to display a list 

of MFG/PRO 

programs. 

1 Specify an optional label for the node. The label uses the font 

attributes associated with the style. While you can specify a long 

label, you typically want to constrain the label to the size of its 

associated node. 

2 Associate an optional URL with the node. When a user clicks on the 

node, the resource is displayed in the browser. 

a To optionally associate an MFG/PRO program to execute, click 

the look-up icon. The lookup displays a list of MFG/PRO 

programs, sorted by menu number. You can click any column 

label to sort by that column. The arrow next to the column name 

indicates the direction of the sort (ascending or descending). 

Enter a value for filtering. Click Next to view more records. 

Fig. 4.12 

Node Properties 

Fig. 4.13 

Program Lookup



URLs with 


page 116. 


URLs with 


page 116. 

b Use the three filter values to narrow the programs displayed in the 

lookup. 

• Enter a string such as fs in the filter field. 

• Then specify whether you want to filter by program, menu 

number, or label. 

• You can further narrow the filter by indicating whether 

displayed items should start with, end with, or contain the 

specified string. 

• Click Filter to display the programs that meet your filter 

criteria. 

c To view the next 100 records, click Next. To view records listed 

previously, click Prev. 

d After filtering the list, click Refresh to display the unfiltered list. 

e Click a row to select a value, close the window, and return the 

value to the URL field. 

You can use variables with URLs so that your processes are not 

confined to one computing environment. You can follow the QAD_DT 

variable with a program name or menu number to execute. 

3 Specify the target window to use when the URL is executed. Values 

are: 

• New Window. The URL is opened in a new window. The process 

window remains open. 

• Current Window. The URL replaces the contents of the current 

window. You must use this setting whenever the destination URL 

is an MFG/PRO program. 

4 Optionally specify the full path or URL for an image to be associated 

with this node. This image is used instead of any shape specified in 

the Shape field. 

Note This image displays in the Process Editor only when you 

specify a literal path. If you use the QAD_DT_IMG variable, you 

must click Preview to expand the variable and view the graphic. 

The system sizes the image to fit into the cell height and width. 

Ensure that the image is correctly proportioned for the cell size or it 

may be distorted.

5 Specify the node shape: rectangle, ellipse, diamond, report, manual 

operation, manual input. The default is rectangle. 

Note If your grid height and width are the same, the rectangle is 

viewed as a square and the ellipse as a circle. 

Figure 4.14 illustrates the node shapes supplied with the Process 

Editor. 

6 Specify a style for the node. The style determines font attributes, 

color, line width, and filter. Style attributes are immediately visible in 

the grid area. 

Connector Properties 

Figure 4.15 illustrates Connector Properties. 

Use the Connector Properties to modify attributes of connectors. 

1 Specify an optional label for the connector. The label uses the font 

attributes associated with the style. While you can specify a long 

label, you typically want to constrain the label to the size of its 

connector. 

2 Associate a URL with the connector. When a user clicks on the 

connector, the URL is launched in a new or current window, based on 

the value of Target. 


Fig. 4.14 

Node Shapes 

Fig. 4.15 

Connector 

Properties



URLs with 


page 116. 

Fig. 4.16 

Process Properties 


URLs with 


page 116 for 

details on global 

variables. 

Fig. 4.17 

Variable Name 

Prompt 

You can use variables with URLs so that your processes are not 

confined to one computing environment. 

3 Specify the target window to use when the URL is executed. Values 

are: 

• New Window. The URL opens in a new window. The process 

window remains open. 

• Current Window. The URL replaces the contents of the current 

window. 

4 Specify a shape for the connector. The shape can be an arrow or a 

line. 

5 Specify a style for the connector. The style determines color, line 

width, and font attributes of the associated label. 

Process Properties 

Figure 4.16 illustrates Process Properties. 

Use Process Properties to create your own variables for use with 

individual processes. These variables have local scope. You can see the 

value of global variables, but you cannot modify them with this editor. 

To create a local variable, follow these steps: 

1 Click New. You are prompted to specify the name of the new 

variable.

2 Enter a name and click OK. The new variable is added to the dropdown 

list in the Process Properties. 

3 Choose the new variable from the list. Scope automatically defaults to 

local and cannot be changed. 

4 Enter a value for the variable. 

5 Click the URL Parameter check box if you want the new variable to 

be added automatically to every URL in this process. 

You can use the Delete button to delete a local variable. You cannot delete 

QAD-reserved variables (global scope). 

Accessing Processes 

After you have created processes, you typically want to make them 

available to users from the interface. To facilitate this, a top-level menu 

item for processes has been added to the main menu. This menu is option 

100 under A. 

Adding items under the Processes link requires two steps: 

• Update a flat (ASCII) file located in a QAD UI configuration 

directory with information about the process. 

• Define the label that should appear on the menu using Label Master 

Maintenance (36.4.17.1). 

Updating the Processes File 

Follow these steps to update the flat file: 

1 Locate processes.d in: 

MFGPROInstallDir/qaduiConfig/com/qad/nav/data 

2 Open this file with a text editor. 

3 Create a line with the following format for the process you want to 

add: 

 

Using the Process Editor 127


See Installation 

Guide: QAD 

User Interfaces. 

is typically A.100 to add the process under the 

Processes link. 

determines the display order for processes. 

is the name you gave the process in Process 

Information. 

is a term defined in Label Master Maintenance. The long 

label associated with the term displays on the interface. This lets you 

create labels appropriate for different languages. 

4 After completing your updates, save the file. 

5 Rebuild the menus using the build scripts. 

Sample Flat File Entries 

To add a process named Purchasing as the first link under the main 

Process menu item, create this line in processes.d: 

"A.100" "1" "Purchasing" "PURCHASING" 

To create a submenu under the Processes link for purchasing processes 

and add the first choice on this menu, create these lines in processes.d: 

"A.100" "1" "A.100.1" "PURCHASING" 

"A.100.1" "1" "Purchase Requisitions" "PURCHASING_REQ" 

Create Terms and Labels 

Follow these steps to create terms and associated labels for the process 

you added to the menu: 

1 Access MFG/PRO and choose Label Master Maintenance 

(36.4.17.1). 

2 Enter the display language of your Desktop screens. In a multiplelanguage 

installation, you must create multiple labels. 

3 Enter the term you specified in processes.d. 

4 Enter the value you want to display on the Desktop menu in Long 

Label. 

5 Press Go to save your changes.

Note When a term is not found in lbl_mstr, the term is displayed on the 

menu rather than the label. 

Administering the Process Editor 

You can configure the Process Editor’s context parameters and process 

properties using Process Admin. To access Process Admin, select 

Administration|ProcessAdmin. 

See Installation Guide: QAD User Interfaces for full details about 

administration. The installation guide also includes details about 

directories and servers. 

Configuring Context Parameters 

Figure 4.18 illustrates the page for configuring context parameters, which 

specify information needed by the Process Editor. 

The page displays with defaults for all context parameters. Some of these 

are derived from values specified during the build process. Typically, 

most of these parameters do not need to be changed. 

Help URL. Enter the full URL to the location where the help files are 

located. These files are an HTML version of this guide. This URL is 

executed when a user clicks the Help link in the Process Editor. To 

link directly to the information in this chapter, specify 

03_ProcessNavigation.html as the final element in the URL. 


Fig. 4.18 

Context Parameters


See Figure 4.13 

on page 123. 

Menu Lookup Result Size. Enter a value that determines the number 

of records returned when a user displays the Program Lookup 

associated with the URL field in the Node and Connector Properties 

editors. The default is 100. 

Menu Lookup Timeout. Enter the number of minutes the system 

should retain menu information in memory. When a user uses the 

Program Lookup, the system connects to the active database using the 

URL specified in Menu Lookup URL and reads the menu information 

from the database. This information is held in memory for the number 

of minutes specified in this parameter. 

Menu Lookup URL. Enter the full URL the system should use to 

connect to an MFG/PRO database when it reads menu records to 

display in the Program Lookup. The URL should look like the 


http://crsu04.qad.com:4949/cgi-bin/ 

qad_wspd_cgi_31c_dt91.ksh/WService=testdt91web/com/qad/ 

nav/xmenu.p?Action=MenuLookup 

It is built using the following elements: 

• Relative path to the executables directory on the Web server 

• WebSpeed executable name 

• WebSpeed broker name 

• API for reading the database menus 

SVG Directory. Specify the directory path where the SVG files 

created with the Process Editor are stored. The path is relative to the 

webapp directory on the Tomcat application server. 

URL Lookup. Specify the file to use for generating the listing of 

MFG/PRO programs associated with the URL field in Connector and 

Node Properties. By default, this is MenuLookup.jsp. 

XML Directory. Specify the path to the directory where the XML files 

created with the Process Editor are stored. A file created with the 

Process Editor is initially saved in XML format and then converted to 

SVG using a stylesheet built with the Extensible Stylesheet Language 

(XSL). The path is relative to the webapp directory on the Tomcat 

application server.

XSL Path. Specify the path to the XSL file used to convert process 

files from XML to SVG format. This file was installed during 

Desktop installation. The path is relative to the webapp directory on 

the Tomcat application server. 

Configuring Process Properties 

Figure 4.19 illustrates the page for configuring process properties. These 

properties are variables that let you set up URL links in the Process Editor 

without using hard-coded values. This ensures that your processes can be 

used in multiple environments, if necessary. 

These variables display in the Process Properties editor, but cannot be 

changed there. The default values can only be changed using the 

administration tool. The only variable you may need to change is 

QAD_DT_DOC_ROOT. The value of other properties is determined by QAD. 

These properties are discussed in “Associating URLs with Processes” on 

page 116. 

QAD_DT. This variable sets up the API between a process and 

Desktop. 

QAD_DT_DOC_ROOT. This directory is unique to each installation. It 

specifies the root directory where Desktop is installed on the Web 

server and has a form similar to the following: 

http://crsu04.qad.com:8080/desktop 

QAD_DT_IMG. This variable points to the images directory below the 

Desktop installation directory defined in QAD_DT_DOC_ROOT. 




page 126. 

Fig. 4.19 

Configuring 

Process Properties




page 126. 

QAD_PV. This variable sets up the API in a URL when you want to 

reference another process. 

After making any changes, click Apply to save the new values. Click New 

to insert a new row for defining a variable. When you create variables 

with the Process Properties editor, you can create local variables only. 

You can define new global variables with the administration tool that are 

available to all users of the Process Editor. 

You can also delete variables if you want. 

Important If you delete any of the QAD-supplied variables, the sample 

processes will no longer work properly.

Chapter 5 

Configuring 

Administrative 

Settings 

The following topics describe administrative settings you can configure 

after initial implementation. These settings let administrators tailor the 

functions in the QAD .NET UI for specific users and groups. 

Configuration Overview 134 

Defining User Settings 135 

Defining Browse URL Links 137 

Monitoring User Sessions 144 

Defining Program Information 145 

Report Format Control 147


Table 5.1 

Desktop Menu 

(36.20.10) 

Configuration Overview 

The QAD .NET UI provides a framework for executing QAD 

applications. One of the applications that runs within the QAD .NET UI is 

QAD Desktop. Some of the settings that can be used with QAD Desktop 

also apply to programs running in the QAD .NET UI. 

These topics describes the various settings that affect program execution 

in the QAD .NET UI. Most of these are located on the Desktop Menu 

(36.20.10). It also describes optional configuration that you can 

implement. 

Some of the manager functions that are used to configure character and 

Windows interfaces can also be used to affect the appearance and 

behavior of the program in the QAD .NET UI. These programs are also 

discussed briefly here. More details can be found in User Guide 

Volume 9: Manager Functions. 

The following table lists the functions available on the Desktop Menu and 

indicates if the function affects programs running under the QAD .NET 

UI. 

Menu 

Number Program Menu Label Notes 

36.20.10.1 mgusromt.p User Option Maintenance Lets you tailor the UI for 

specific users and groups; only 

two settings apply to 


36.20.10.2 mgbr062.p User Option Browse Lets you browse user option 

settings 

36.20.10.3 mgusrtmt.p User Option Telnet 

Maintenance 

Discussed in Installation 

Guide: QAD User Interfaces 

36.20.10.4 mgusrrp.p User Option Report Lets you generate a report of 

user option settings 

36.20.10.8 mgurlmt.p Menu URL Maintenance Does not affect QAD .NET 

UI. 

36.20.10.9 mgbr220.p Menu URL Browse Does not affect QAD .NET 

UI.

Menu 

Number Program Menu Label Notes 

36.20.10.11 mgburlmt.p Browse URL Maintenance Lets you define URLs to 

external resources or 

MFG/PRO programs that 

display in Desktop browses 

36.20.10.12 mgbr221.p Browse URL Browse Lets you browse the URLs in 

the QAD .NET browses 

36.20.10.15 mgsessmt.p Session Master 

Maintenance 

Defining User Settings 

Most of the settings in User Option Maintenance (36.20.10.1) are either 

obsolete or control features of QAD Desktop when it is being used 

outside the QAD .NET UI. Only two settings affect program execution 

when you are using the QAD .NET UI: Expiration Date and Session 

Timeout. 

Configuring Administrative Settings 135 

Lets you monitor current user 

sessions 

You can define unique settings for individual users or enter an asterisk (*) 

in the User ID field to create a generic record of settings. This generic 

record is automatically associated with every user in the system that does 

not have a user-specific record. 

Note Expiration date must be defined for specific users; you cannot 

create a generic value. 

The system is installed with a default record that applies to all users. You 

can change it to accommodate your own requirements. 

You should create separate records for individual users only when 

appropriate settings vary from user to user. 

Note Individual user IDs must be defined in User Maintenance (36.3.1) 

before you can reference them in User Option Maintenance.


Fig. 5.1 

User Option 

Maintenance 

(36.20.10.1) 

Table 5.2 

User Option 

Settings 

The following table summarizes the use of User Option Maintenance 

settings. 

Field Description 

Restrict Menu Obsolete. 

You can restrict user access to executing 

programs as needed using Menu Security 

Maintenance (36.3.10). 

Menu Substitution Obsolete. 

Only the standard menu items are included on 

the QAD .NET UI menus. 

Program Execution Applies to QAD Desktop only. In the 

QAD .NET UI, users can only execute a 

program after it has been added to the menu. 

Server Print Applies to Java browses in QAD Desktop; does 

not apply to QAD .NET UI. 

Save Brw Settings Applies to Java browses in QAD Desktop; does 

not apply to QAD .NET UI. In the QAD .NET 

UI, browse settings are always saved with other 

session values. 

QAD 

Desktop 


.NET 

UI 

No No 

No No 

Yes No 

Yes No 

Yes No 

Expiration Date Indicates when the associated user can no 

longer access the system. 

Yes Yes 

Max Web 

Connections 

Obsolete. No No

Field Description 

Max Browse 

Records 

Applies to Desktop only. In QAD .NET UI, 

records are specified by the user in Tools| 

Options. 

Session Timeout Determines the amount of time in minutes after 

which the system automatically logs a user out 

of an inactive session. A change to the session 

timeout does not take effect until a user’s next 

session: if a user is logged in when this field is 

changed, the new session timeout does not take 

effect until after the user logs out and then logs 

in again. 

Defining Browse URL Links 

Use Browse URL Maintenance (36.20.10.11) to create URL links that 

users can activate from QAD .NET browses. This is described in 

“Accessing Links in Browses” on page 42. 

When a browse cell contains a URL link, double-clicking it launches a 

new browser window and displays the intranet or Internet resource 

associated with the URL. You can use these URLs in two ways: 

• Create links to external Web sites that users can activate from 

QAD .NET browses, such as a supplier Web site associated with a 

supplier ID. 

• Create links to other MFG/PRO programs and pass specific data 

values to the programs. This lets you use browses as a means of 

navigating directly to maintenance programs. 



Desktop 

Yes No 

Yes Yes 

Browse Timeout Obsolete. No No 


.NET 

UI 

You can access links to other programs only from drill-down browses, not 

lookups. Drill-down browses are typically available directly from the 

MFG/PRO menus, but can also be associated with program fields in Drill 

Down/Lookup Maintenance (36.20.1).


Table 5.3 

Sample Field 

Entries for Browse 

URL Links 

Defining URLs to External Web Pages 

Use Browse URL Maintenance to create links to external URLs with 

information that is related to items in the browse, as in the following 

example. 

Example You want to establish a URL link in the Purchase Order 

Browse from supplier ID GS10100 to the corresponding supplier’s 

company Web site, located at http://www.generalsupplies.com. To do this, 

enter the values in listed here in Browse URL Maintenance. 

Field Name Value 

Browse pobr006.p 

User ID * 

Field Name so_vend 

Value gs10100 

URL http://www.generalsupplies.com 

Description General Supplies Web Site 

Primary Yes 

URLs can contain special strings that are automatically replaced by field 

values in the browse. Selecting a link containing this type of string 

automatically replaces that string with the corresponding field value in the 

row. 

Follow these steps to define this type of special string in a URL: 

1 Enter #b# to indicate the beginning of the string. 

2 After the #b#, enter an MFG/PRO field name associated with the 

specified browse. 

3 Enter #e# to indicate the end of the string. 

Example The Web site for one of your primary suppliers contains a 

catalog of items. Entering an item’s identifier at this Web site accesses the 

catalog entry for that item, containing information such as item cost, 

quantity available, and ship weight. To create links from the MFG/PRO 

supplier item numbers to their corresponding catalog entries at the 

supplier’s Web site, create the following URL: 

http://www.generalsupplies.com/catalog/#b#vp_vend_part#e#


Then, associate it with the Supplier Item column in the Supplier Item 

Browse. After you establish this link, selecting a supplier item number in 

the Supplier Item Browse automatically inserts the selected field value. 

For example, selecting supplier item 10-1005 creates this URL: 

http://www.generalsupplies.com/10-1005 

The system then launches a Web browser to display the relevant catalog 

information for that item located at that URL address. 

Defining Links to Other MFG/PRO Programs 

Use Browse URL Maintenance to create links to other MFG/PRO 

programs, as in the following example. 

You can set up links in an item browse to directly access Item Master 

Maintenance (1.4.1), passing the current item number to the maintenance 

program, and executing the Next command any number of times. When a 

user clicks the link, Item Master Maintenance displays in a detached 

window. 

Multiple columns of data in a browse can contain links so that you can 

access maintenance programs for any data related to a record. However, 

data for only one field can be passed to each program. 

To support this kind of URL link, use the run_html setting to indicate that 

you want to build a URL for MFG/PRO programs. The string must 

include the beginning and ending indicators required for other strings in 

URLs: 

1 Enter #b# to indicate the beginning of the string. 

2 Enter #e# to indicate the end of the string. 

Then specify values that determine: 

• The name of the MFG/PRO program to be executed when a user 

clicks the link 

• The field in the designated MFG/PRO program to which you want to 

supply a value 

• The value to be passed to the specified field 

• The number of times the Next command should be executed in order 

to reach the field


Table 5.4 

Sample Field 

Entries for Browse 

Program Links 

To make it easy to build the URL, leave the URL and URL Script fields 

blank and click Next to display a pop-up that prompts you for the values 

required to build the URL. In this case, the system builds the URL 

including the run_html setting using the values you supply. 

Field Name Value 

Browse sobr009.p 

User ID * 

Field Name sod_part 

Value * 

URL Leave Blank 

Description Link to Item Master Maint. 

Program Name ppptmt 

Field pt_part 

Value sod_part 

Index 2 

The URL that the system builds based on these input values looks like the 


#b#run_html#e#?id=ppptmt.p&f=pt_part&v=#b#sod_part#e#&x=2 

When the user clicks item 01053 in the sobr009.p browse, Item Master 

Maintenance displays with 01053 entered in the Item Number field and 

the active cursor focus is in the Name field below it.

Using Browse URL Maintenance 

The following figure illustrates Browse URL Maintenance. 

Use the following field descriptions to configure Browse URL 

Maintenance settings for your environment: 


Browse. Enter the name of the browse program to contain the 

specified URL link. 

Entering an asterisk (*) in this field allows the specified URL to be 

associated with any browse in the system. 

Example To associate a specific URL with the sales order number 

column in all QAD .NET browses, enter an asterisk in this field and 

specify the sales order column’s corresponding field name (so_nbr) in 

Field. 

User ID. Enter a user ID to associate with the specified URL link. To 

associate all users in the system with that link, enter an asterisk (*) in 

this field. 

Field Name. Designate the browse column in which you want to 

establish a URL link by entering the database field name associated 

with that column. The lookup associated with this field displays fields 

from the previously entered browse. 

Fig. 5.2 

Browse URL 

Maintenance 

(36.20.10.11)


This field cannot be left blank. 

Value. Specifying a value in this field associates the designated URL 

with every browse cell that contains that value and belongs to the 

browse column indicated in Field Name. Enter an asterisk (*) to 

associate the URL with every cell in the column. 

URL. Specify a URL referring to an Internet or intranet location 

(maximum 132 characters). Leave blank to create a link to another 

MFG/PRO program. 

Description. Optionally enter a description to display when this URL 

is selected. 

Primary. Enter Yes to indicate that the specified URL is the primary 

URL for a cell. 

When you right-click a browse cell containing multiple URLs, a list 

displays for selection. The primary link displays at the top of the list 

in bold font and is the default link for the cell. 

Note The value of Primary has effect only if no drill-downs are also 

associated with the cell. Drill-downs always take precedence over 

URLs and are listed first when you right-click. 

This value applies to defined (non-scripted) URLs only. 

URL Script. To associate the specified user, browse, column, field 

value, or combination of these with a custom URL script, enter the 

full path to the directory containing the custom script. You cannot 

specify both a URL and a URL script. Scripts should be based on the 

supplied template urltempl.p, located in the source code directory, 

/src/urltempl.p. 

Determine. Enter Yes to have the system run the specified custom 

URL script upon selection of the associated cell or column to 

determine whether that cell or column has an associated URL. 

When this field is No, the script is not run and the designated column 

or cell is defaulted to having a URL.

HTTP Parameters Pop-Up 

This pop-up displays when both URL and URL Script are blank and lets 

you specify a set of values used to access another MFG/PRO program. 


Program Name. Enter the name of the MFG/PRO program to launch 

when a user clicks this link. You can include or omit the .p extension. 

For example, specify adcsmt or adcsmt.p. 

Field. Enter the field in the program that you want to pass a value to 

from the browse; for example, enter cm_addr to pass a value to the 

Customer Address field in Customer Maintenance. Only one field can 

be specified. 

Value. Enter the field in the browse that contains the value that you 

want to pass to the named field. Use the beginning and ending 

delimiters for this value. For example, to pass the value of the 

sod_part field in the Sales Order Browse (7.1.2) to the pt_part field in 

Item Master Maintenance, enter #b#sod_part#e#. 

Index. Enter the number of times you want the system to execute a Go 

command when it invokes the program specified for Program Name. 

To access the first frame in a maintenance program, set this value to 1. 

If you set this to more than 1, all validations are executed before 

Fig. 5.3 

Browse URL 

Maintenance, 

HTTP Parameters


Fig. 5.4 

Session Master 

Maintenance 

(36.20.10.15) 

processing the Go command, so if appropriate values do not exist for 

all required fields, an error will be generated when the user clicks the 

link. 

Monitoring User Sessions 

Use Session Master Maintenance (36.20.10.15) to view information about 

users who are currently logged in to MFG/PRO through the QAD .NET 

UI. This information displays in the form of session records, each 

identified by a unique session ID that is generated by the system. (You 

can identify your current session ID by selecting Tools|Options and 

viewing the Session ID in the MFG/PRO System Preferences section.) A 

session record is automatically created when a user successfully logs in to 

MFG/PRO from the QAD .NET UI and is deleted when the user logs out. 

Only some of the settings displayed on this screen apply to the 

QAD .NET UI sessions. You can ignore the following: Active Web, 

Number of Records, Security Profile, Active Telnet, Menu Substitution, 

and Context ID.

The session context detail displays information about the current 

workspace (domain). One user session can be associated with multiple 

contexts if programs have been activated in more than one workspace. 

You can also monitor the status of sessions for HTML maintenance 

programs, reports, and inquiries using Connection Manager, which is 

described in detail in Installation Guide: QAD User Interfaces. 

Defining Program Information 


The program information table contains a record for each menu-level 

program in MFG/PRO, defining characteristics that affect the way it runs. 

Each program in the QAD .NET UI must have a record both in Menu 

System Maintenance and in Program Information Maintenance 

(36.3.21.1). 

In addition to menu-level programs, lookups must be defined in order for 

the look-up icon to display next to a field in an HTML screen. 

Program information records are loaded with other default data during 

system installation and can be viewed in Program Information 

Maintenance or Program Information Browse (36.3.21.2). You must 

manually create records for any custom programs that you want users to 

be able to access from the QAD .NET UI. 

The following table lists the default settings for different program types. 

Program Type 

Web Logic 

Implemented Type 

Browses, lookups Yes Blank 

Special HTML programs such as 

Browse Maintenance and Kanban 

workbenches 

Yes Blank 

HTML reports and inquiries No Desktop 

HTML maintenance programs No Desktop 

The Multi Domain field indicates a program that updates data that applies 

to all domains in an MFG/PRO database. When this is set to Yes, the 

string All Domains displays in the Menu Properties window for the 

associated menu program. Otherwise, the domain name displays. 

Table 5.5 

Default Display of 

Programs in 

QAD .NET UI


See page 147 for 

details. 

Fig. 5.5 

Program 

Information 

Maintenance 

(36.3.21.1) 

Appropriate default settings for the Multi Domain field are set during 

installation. For example, generalized codes apply to each domain 

separately so Multi Domain is set to No by default for mgcodemt.p. 

Country codes apply to the database as a whole so Multi Domain is set to 

Yes by default for adctrymt.p. 

Important You can update the setting for your custom programs or 

change it if you want the current working domain to continue to display 

even when a user is updating a table that applies across domains. This 

change affects what displays on the UI only. The program continues to 

update data for all domains. 

Adding Records 

To execute a program from the QAD .NET UI menus, add a record to 

Program Information Maintenance for each custom program. 

If you want to create records for a number of programs at once, use 

Program Information Update (36.3.21.23.18) to scan them and 

automatically create records. 

For .NET 

browses 

To create program information records: 

1 Enter a custom program name. 

2 Indicate if this program updates data for all domains in the database. 

3 Press Go to continue. 

4 Set Web Logic Implemented to Yes if this is a browse written 

according to QAD standards. Set Web Logic Implemented to No if 

this is a maintenance program, report, or inquiry that you want to 

display in HTML.

5 Leave the Type field blank for a browse. Specify Desktop for an 

HTML maintenance program, report, or inquiry. 

Program Information Update 


Use Program Information Update to automatically add records for custom 

programs to Program Information Maintenance. Use this utility as an 

alternative to adding records manually. It is especially useful for initially 

populating records with referenced tables. 

Report Format Control 

With the QAD .NET UI you can control the appearance of reports, 

including: 

• “Displaying Company Logo” on page 148 

• “Removing Report Footer” on page 148 

• “Setting Default Browser Text Size” on page 149 

• “Setting Different Colors for Alternate Rows” on page 149 

• “Setting Report Format” on page 149 

• “Excluding Some Reports from New Format” on page 150 

Fig. 5.6 

Program 

Information Update 

(36.3.21.23.18)


Displaying Company Logo 

With the new format, the upper-left area can include your company’s 

logo. To include a logo: 

1 Locate the Tomcat installed images directory (for example, 

TomCatInstallDir/webapps/qaduiConfig/images). Place 

any graphics files containing company logos in this directory. For 

example, place a file named myLogo.jpg that contains the logo you 

want to use. By default, the directory includes companyLogo.jpg, 

which contains the QAD logo. 

2 To add your company’s logo to the report, edit the setting.dat file 

in the TomCatInstallDir/webapps/qaduiConfig/WEB- 

INF/pro/com/mfgpro directory, setting reportCompanyLogoImage 

to the graphics file (images/myLogo.jpg). 

By default, reportCompanyLogoImage is set to 

image/companyLogo.jpg. (Note that the file name is casesensitive.) 

If you do not want to display a logo on reports, set 

reportCompanyLogoImage to blank (do not enter any graphics file). 

3 Clear the QAD .NET UI’s cache of temporary Internet files before 

running further reports. 

Removing Report Footer 

The new report footer now includes the program name and number at the 

bottom of the report. If required, you can remove the footer information 

as follows: 

1 Edit the TomCatInstallDir/webapps/qaduiConfig/css/ 

AppReportStandard.css file, changing the div.reportFooter 

statement to the following: 

div.reportFooter {display:none;} 

2 Finally, all users must clear the QAD .NET UI’s cache of temporary 

Internet files before running further reports.

Setting Default Browser Text Size 


To have reports use your default browser text size setting, edit the 

setting.dat file in the 

TomCatInstallDir/webapps/qaduiConfig/WEB- 

INF/pro/com/mfgpro directory, setting allowBrowserFontSize to yes. 

The default setting is no. Note that to set the default browser text size 

setting in Internet Explorer, select View|Text Size). 

Setting Different Colors for Alternate Rows 

If a report includes different colors for alternate rows, to have the 

different colors display, select Tools|Internet Properties and click the 

Advanced tab. In the Settings view, scroll down to Printing and select 

Print background color and images. 

Setting Report Format 

You can specify whether to use the new report format or the previous 

report format on a system-wide basis as follows: 

1 To use the new report format, edit the setting.dat file in the 

TomCatInstallDir/webapps/qaduiConfig/WEB- 

INF/pro/com/mfgpro directory, setting beautifyReports to yes. 

2 To use the old report format, set beautifyReports to no. By default, 

beautifyReports is set to yes. 

3 Restart the Connection Manager for the changes to take effect. 




Excluding Some Reports from New Format 

If you want to use the new report format but want to have selected reports 

use the old format, you can exclude those reports from the new format as 

follows: 

1 List the reports in the reports.lst file, located in the QAD user 

interface installation /pro/com/mfgpro directory (for example: 

/eB21/qadui/pro/com/mfgpro). 

2 Restart the Connection Manager for the changes to take effect. 



Accelerator Keys. Keystroke equivalents to 

mouse actions. For example, you can delete a 

record in the QAD .NET UI by choosing 

Delete from the Actions menu or by pressing 

Ctrl+Shift+D. 

Actions Menu. A pop-up menu that displays 

when you use a right-mouse click. The choices 

on the menu vary depending on where you 

click; only actions valid in the current context 

display. 

Apache Software Foundation. A 

membership-based, not-for-profit corporation 

that exists to provide organizational, legal, and 

financial support for the Apache open-source 

software projects. 

Applet. See Java Applet. 

Array. A field or variable with multiple 

elements, each element having the same data 

type. 

Bookmark. A saved link to a Web page that 

has been added to a list. Bookmarks are found 

on the Favorites menu in Internet Explorer. 

Browse. An inquiry program that displays 

records in a tabular format. Browse types 

include look-up and drill-down browses. Drilldown 

browses can be specified on the menu or 

associated with a field. Look-up browses are 

always associated with individual fields for use 

in selecting entry values. See also Drill-Down 

Browse and Look-Up Browse. 

Glossary 

Browser. An application used to view and 

navigate the World Wide Web and other 

Internet resources. Common browsers include 

Microsoft Internet Explorer and Netscape 

Navigator. 

Bytecode. Compiled Java code containing 

instructions to the Java virtual machine. The 

virtual machine, in turn, interprets these 

instructions so they can be performed by the 

system. See also Java Virtual Machine (JVM). 

Cascading Style Sheet (CSS). A Web page 

derived from multiple sources with a defined 

order of precedence to manage conflicts among 

style element definitions. The cascading style 

sheet, level 1 (CSS1) recommendation from 

the W3C is implemented in the latest versions 

of the Netscape and Microsoft Web browsers. 

CGI. See Common Gateway Interface (CGI). 

Character Interface. Sometimes abbreviated 

as CUI or CHUI, an interface to MFG/PRO 

that displays only keyboard characters on the 

screen rather than icons and buttons. Compare 

with Graphical User Interface (GUI). 

Comma-Separated Values (CSV). Sometimes 

referred to as flat files, CSV files organize 

values as a series of ASCII text lines where 

each column value is separated by a comma 

from the next column’s value and each row 

starts a new line. Data in CSV files can be 

conveyed as input to other table-oriented 

applications such as Microsoft Excel.


Common Gateway Interface (CGI). A 

standard way for a Web server to pass a Web 

user’s request to an application program and to 

receive data in response, which it then 

forwards to the user. CGI is part of the Web’s 

hypertext transfer protocol (HTTP). See also 

HTTP (Hypertext Transfer Protocol). 

Cookie. Information a Web site puts on your 

hard disk so that it can retrieve information 

about you at a later time. Typically, a cookie 

records your preferences when using a 

particular site. 

CSS. See Cascading Style Sheet (CSS). 

CSV. See Comma-Separated Values (CSV). 

Data Encryption. See Encryption. 

DHTML (Dynamic Hypertext Markup 

Language). A combination of new HTML tags 

and options that support more animated and 

interactive Web pages. Much of dynamic 

HTML is specified in HTML 4.0 with 

Javascript and cascading style sheets. See also 

HTML (Hypertext Markup Language). 

Document Object Model (DOM). A 

programming interface specification being 

developed by the W3C that lets a programmer 

create and modify HTML pages and XML 

documents as program objects, rather than data 

structures. 

Drill-Down Browse. A type of browse that is 

available from a menu or associated with other 

browse fields. You can filter, graph, and print 

from drill-down browses. Compare with Look- 

Up Browse. 

Encryption. Conversion of data into a form 

that cannot be easily intercepted by 

unauthorized people. 

Extensible Markup Language (XML). A 

markup language that describes data. XML is 

used to create HTML screens. 

Extensible Stylesheet Language (XSL). A 

language for formatting an XML document; for 

example, showing how the data described in 

the XML document should be presented in a 

Web page. XSLT shows how the XML 

document should be reorganized into another 

data structure (which could then be presented 

by following an XSL style sheet). 

Extensible Stylesheet Language 

Transformation (XSLT). A standard way to 

describe how to transform the structure of an 

XML document into an XML document with a 

different structure. The coding for the XSLT is 

also referred to as a style sheet and can be 

combined with an XSL style sheet or be used 

independently. 

Extranet. A private network designed to 

securely share portions of business information 

or operations with suppliers, partners, 

customers, or other businesses. An extranet can 

be viewed as part of a company’s intranet that 

is extended to users outside the company. See 

also Internet Server Application Programming 

Interface (ISAPI). 

Field Tips. Context-specific references to 

fields consisting of the Progress field name. 

Graphical User Interface (GUI). A user 

interface that presents computer actions and 

options as pictures, buttons, and icons. The 

most common example of a graphical user 

interface is Microsoft Windows. Compare with 

Character Interface. 

Graphics Interchange Format (GIF). A 

graphics file format that is the industry 

standard for Web and Internet use. 

Grid. A screen design element that organizes 

related data fields in a format similar to a 

spreadsheet or table. 

Group. See Security Group. 

GUI. See Graphical User Interface (GUI).

HTML (Hypertext Markup Language). A tagbased 

ASCII language used to create pages on 

the World Wide Web. HTML uses codes 

surrounding a block of text to indicate how it 

should display. In HTML, you can also specify 

that a block of text, or a word, is linked to 

another file on the Internet. 

HTTP (Hypertext Transfer Protocol). The set 

of rules for exchanging text, graphic images, 

sound, video, and other multimedia files on the 

World Wide Web. See also Common Gateway 

Interface (CGI). 

Interface. See User Interface (UI). 

International Organization for 

Standardization. See ISO. 

Internet. A system of linked computer 

networks—international in scope—that 

facilitates data communication services such as 

remote log-in, file transfer, electronic mail, and 

newsgroups. The Internet is a way of 

connecting existing computer networks. 

Internet Information Server (IIS). Web server 

software from Microsoft Corporation that 

supports a common gateway interface. 

Internet Server Application Programming 

Interface (ISAPI). A program-level means of 

communicating with the Microsoft Internet 

Explorer Web server. 

Intranet. A private network inside a company 

or organization that uses the same kinds of 

software found on the public Internet. 

ISO. ISO (International Organization for 

Standardization), founded in 1946, is a 

worldwide federation of national standards 

bodies from some 100 countries. ISO is not an 

abbreviation. It is a word, derived from the 

Greek isos, meaning equal. The name ISO is 

used around the world to denote the 

organization. 

Glossary 153 

ISS. See Internet Information Server (IIS). 

JAR File. See Java Archive File (JAR). 

Java 2 Platform, Enterprise Edition (J2EE). 

A recent release of Java designed to support the 

requirements of large-scale computing 

systems. Features include Java servlets and 

Java Server Pages (JSPs), which facilitate 

dynamic Web-enabled data access and 

manipulation. 

Java. An object-oriented programming 

language created by Sun Microsystems. Java is 

a device-independent language. Programs 

compiled in Java can be run on any computer. 

Java programs can be run as free-standing 

applications or as applets placed on a Web 

page. 

Java Applet. A small application program that 

can be sent along with a Web page to a user. 

Applets written in Java are served from a Web 

site but executed on the client computer. 

Java Archive File (JAR). A file that contains 

the class, image, and sound components of a 

Java applet gathered into a single file and 

compressed for faster downloading to a Web 

browser. 

Java Bean. A reusable program building block 

developed with a Beans Development Kit 

(BDK) from Sun Microsystem. 

Java Class. In object-oriented programming, a 

class is a template definition of the methods 

and variables in a particular kind of object. 

Java Development Kit (JDK). A software 

development environment from Sun 

Microsystems for writing applets and 

applications in the Java programming 

language.


Java Runtime Environment (JRE). A subset 

of the Java Development Kit for end users and 

developers who want to redistribute the Java 

runtime environment. The Java runtime 

environment consists of the Java virtual 

machine (JVM), the Java core classes, and 

supporting files. 

Java Server Page (JSP). A technology for 

controlling the content or appearance of Web 

pages through the use of servlets, small 

programs that are specified in the Web page 

and run on the Web server to modify the page 

before it is sent to the user who requested it. 

Java Virtual Machine (JVM). The part of the 

Java runtime environment responsible for 

interpreting bytecode. A JVM is included in 

the JRE, which replaces the default virtual 

machine associated with a Web browser. This 

lets developers deploy Java applets that depend 

on the latest features of the Java platform and 

be assured that their applets will run reliably 

and consistently in a browser. See also 

Bytecode. 

JDK. See Java Development Kit (JDK). 

JRE. See Java Runtime Environment (JRE). 

JSP. See Java Server Page (JSP). 

JVM. See Java Virtual Machine (JVM). 

Leaf Nodes. The lowest-level elements in a 

hierarchical navigation tree. Leaf nodes cannot 

be expanded or collapsed. 

Look-Up Browse. A type of browse that is 

only associated with individual program fields 

for use in selecting entry values. Look-up 

browses contain less detail than drill-down 

browses. Compare with Drill-Down Browse. 

Maintenance Programs. Programs used to 

add, modify, and delete records and codes in 

the MFG/PRO database. 

Menu Substitution. Replacing one program 

with another on the MFG/PRO menu; for 

example, replacing a standard program with a 

customized version. 

MFGX.net. The QAD portal, which is a 

collaborative environment where members of 

the manufacturing community can share 

information and work together to achieve 

overall competitiveness. 

MIME (Multipurpose Internet Mail 

Extension). A protocol for exchanging 

different kinds of information on the Internet. 

The MIME header is inserted at the beginning 

of a Web transmission so that client programs 

can select the appropriate associated 

application. 

Netscape Server Application Programming 

Interface (NSAPI). A program-level means of 

communicating with the Netscape Web server. 

Network. A series of points or nodes 

interconnected by communication paths. The 

Internet is a common example of a network. 

See also Internet, Extranet, Internet Server 

Application Programming Interface (ISAPI), 

and Wide Area Network (WAN). 

Node. In the Process Editor, nodes represent 

steps in a process and can contain URL links to 

other resources. 

Perl. A script programming language 

(Practical Extraction and Reporting Language) 

that is similar in syntax to the C language and 

that includes a number of popular UNIX 

facilities. Perl is regarded as a good choice for 

developing Common Gateway Interface (CGI) 

programs because it has good text 

manipulation facilities.

Platform. An underlying computer system on 

which application programs run. Historically, 

most application programs had to be written to 

run on a particular platform. Products written 

in Java, however, are cross-platform, meaning 

they can be run anywhere the Java runtime 

environment is installed. 

Point. A unit of about 1/72 inch used to 

measure type size. 

PROPATH. An environment variable 

containing the list of directories Progress 

searches when looking for a program to 

execute. 

Relational Database Management System 

(RDBMS). The Progress software that manages 

and provides access to the MFG/PRO 

databases. 

RSA (Rivest-Shamir-Adleman). An Internet 

encryption and authentication system that uses 

an algorithm developed in 1977 by Ron Rivest, 

Adi Shamir, and Leonard Adleman. The RSA 

algorithm is included with Netscape Navigator 

and Microsoft Explorer. 

Scalable Vector Graphics (SVG) . An XML 

technology for defining vector-based twodimensional 

graphics for the Web. 

Script. A program or sequence of instructions 

that is interpreted or carried out by another 

program. 

Secure Sockets Layer (SSL). A program 

layer for managing the security of message 

transmissions in a network. The program layer 

exists between an application (such as a Web 

browser or HTTP) and the Internet’s TCP/IP 

layers. Sockets refers to the sockets method of 

passing data back and forth between a client 

and a server program in a network or between 

program layers in the same computer. 

Glossary 155 

Security Group. A category of users who 

typically access the same programs in 

MFG/PRO. 

Servlet. Programs similar to Java applets, that 

run on the server rather than the client and are 

used to run interactive Web applications. 

Socket. A convention for connecting with and 

exchanging data between two program 

processes within the same computer or across a 

network. A socket represents the end point in a 

network connection. Sockets are created and 

used with a set of programming requests or 

function calls sometimes referred to as the 

sockets application program interface (API). 

The most common sockets API is the Berkeley 

UNIX C language interface. 

SSL. See Secure Sockets Layer (SSL). 

SVG. See Scalable Vector Graphics (SVG). 

TCP/IP. See Transmission Control 

Protocol/Internet Protocol (TCP/IP). 

Telnet. A user command and underlying 

TCP/IP protocol that lets you access 

applications and data on remote, or host, 

computers. See also Transmission Control 

Protocol/Internet Protocol (TCP/IP). 

Terminal Emulation. Use of a personal 

computer to interact with a computer with a 

different operating system. The terminal 

emulation program runs as a separate task with 

its own window. The application interface 

presented in this window is character-based or 

text-only. 

Thin-Client. In a thin-client model, the client 

machine takes on only the user interface role. 

No business logic processing is accomplished 

on the client.


Tomcat. The servlet container used in the 

official reference implementation for the Java 

Servlet and Java Server Pages (JSP) 

technologies. Tomcat is developed in an open 

and participatory environment and released 

under the Apache Software Foundation license. 

Tool Tips. Context-specific descriptions that 

display whenever your cursor is positioned 

over a UI button. 

Transmission Control Protocol/Internet 

Protocol (TCP/IP). The basic communication 

language or protocol of the Internet. It can also 

be used as a communications protocol for 

intranets and extranets. 

UI. See User Interface (UI). 

Uniform Resource Locator (URL). A text 

string that indicates the location of an intranet 

or Internet resource. 

Universal Unique Identifier (UUID). A 

hexadecimal number including a time stamp 

and a host identifier. Applications use uuids to 

identify many kinds of entities. 

User Interface (UI). The portion of an 

application that is visible to the user and the 

mechanism by which the end user interacts 

with the application, enters information into 

the application, and sees the results of the 

interaction. 

UUID. See Universal Unique Identifier 

(UUID). 

W3C. See World Wide Web Consortium (W3C). 

WAN. See Wide Area Network (WAN). 

WAR. See Web Archive File (WAR). 

Web Archive File (WAR). A compressed file 

containing a Web application and its related 

files. Assists in easily deploying an entire 

application. 

Web Browser. See Browser. 

Web-Enabled. Distinguishes .NET browses 

from other types of programs that run in the 

.NET framework. 

Web Site. A related collection of Web files that 

includes an introductory file called a home 

page. From the home page, you can get to all 

the other pages at that site. 

WebSpeed. A product from Progress Software 

consisting of two parts: a set of Web-centric 

development tools and a transaction Web 

server. The server manages high-volume 

database transactions across multiple servers. 

Wide Area Network (WAN). Generally a 

corporate private network that connects 

computers between remote company sites. 

Widget. In Java screen-design terms, identifies 

a unique screen element. Widgets display 

information or provide specific ways for users 

to interact with application programs. 

Wildcards. Characters or symbols used in 

search or command functions in place of one or 

more letters or numbers. 

World Wide Web Consortium (W3C). An 

international industry consortium that seeks to 

promote standards for the evolution of the Web 

and interoperability among Internet products 

by producing specifications and reference 

software. 

XML. See Extensible Markup Language 

(XML). 

XSL. See Extensible Stylesheet Language 

(XSL). 

XSLT. See Extensible Stylesheet Language 

Transformation (XSLT).

Numerics 

32.3 84 

36.3.21.23.18 147 

36.20.10 134 

36.20.10.1 135 

36.20.10.11 42, 137 

36.20.10.15 144 

36.20.13 80 

A 

Actions menu 

Email command 65 

HTML screens 62 

pivot 63 

administration options 12 

All Domains display 145 

Auto End command 102 

Auto Next command 102 

autosize 

browse 37 

B 

Browse Maintenance 80 

Browse URL Maintenance 42, 137 

browses 34–43 

column options 37 

Excel output 41 

features 35 

grouping data 38 

links in 42 

navigation 36 

preferences 15 

rows per page 16 

search 44 

C 

calendar 

HTML 61 

connectors, Process Editor 125 

context menu 

Process Editor 111 

SVG 112 

context parameters, Process Editor 129 

copy command 


cut command 


D 

delete command 


Desktop 

accessing processes 127 

Desktop Menu 134 

Drill Down/Lookup Maintenance 42 

E 

Edit menu 11 

e-mail 

sending URL links 65 

Email command 65 

Excel output 41 

F 

field help 76 

field tip 77 

File menu 10 

filter style property 122 

Fixed Asset Maintenance 84 

functional menus 10 

Edit 11 

File 10 

Help 18 

Tools 12 

Window 18 

Workspace 18 

Index


G 

global variables, Process Editor 117 

grids, Process Editor 120 

grouping browse data 38 

groups 

assigning UI templates 92 

UI design 94 

H 

help 

application 76 

field and tool tips 77 

for SVG commands 112 

menu 18 

HTML maintenance screen 59 

Actions menu 62 

calendar 61 

keyboard navigation 71 

messages 72 

selection lists 68 

K 

keyboard commands 

HTML maintenance screens 71 

.NET UI 19 

telnet 76 

L 

Label Master Maintenance 127 

links 

accessing in browses 42 

Browse URL Maintenance 137 

external Web page 138 

other MFG/PRO programs 139 

program to program 78 

local variable, Process Editor 126 

log level 13 

M 

maintenance programs 

HTML 59 

menus 20 

Action 62 

icons 23 

include role menu 16 

My 23 

options 21 

properties 22 

searching 25 

messages 72 

MFG/PRO options 15 

My Menus 23 

N 

nodes 


O 

opacity, Process Editor 121 

P 

Page output option 73 

panning SVG images 112 

paste command 


pivot command 63 

previewing a process 116 

Printer Setup Maintenance 73 

printing 

to page 73 

Process Editor 105–132 

accessing processes from Desktop 127 

adding rows and columns 120 

Connector Properties 125 

context menus 110 

context parameter 129 

creating processes 113 

deleting processes 115 

Grid Properties 120 

introduction 109 

managing files 108 

Node Properties 123 

opening processes 114 

previewing a process 116 

Process Information 119 

Process Properties 126 

saving processes 113 

Style Properties 121 

URLs 116 

process-config.xml 117, 122 

processes.d 127 

program help 76 

Program Information Browse 145 

Program Information Maintenance 145 

Program Information Update 147 

properties, menu 22 

property editors 118 

Connector 125 

Grid 120 

Node 123 

Process 126 

Process Information 119 

Style 121

Q 


features 7 

functional menus 10 

HTML maintenance screens 59 

HTML reports and inquiries 73 

main screen 8 

QAD .NET UI overview 5 

QAD_DT 118, 131 

QAD_DT_DOC_ROOT 117, 131 

QAD_DT_IMG 117, 131 

QAD_PV 118, 132 

R 

reports 

canceling HTML 73 

HTML 73 

printing 73 

role menus 

including 16 

rows per page 16 

S 

scalable vector graphics (SVG) 106 

commands for 112 

scroll output 73 

searching 

browse operators 46 

browses 44 

menus 25 

security, log on 8 

selection lists 

HTML screens 68 

Session Master Maintenance 144 

simplified screens 87–103 

administration 92 

creating templates 96 

supported programs 88 

Simplified Screens Setup function 93 

styles, Process Editor 121 

SVG. See scalable vector graphics (SVG) 

T 

tab groups 

creating 29 

moving programs 31 

target window, Process Editor 124 

templates, simplified screens 90 

assigning to users 92 

conflicts 94 

creating 96 

field options 101 

navigation options 102 

tip 

field 77 

tool 77 

tool tip 77 

Tools menu 12 

U 

UI Design Group 94 

UI Template Conflicts function 94 

uniform resource locators (URLs) 

browse links 137 

updates, checking for 14 

URLs 

connector 125 

images 124 

nodes 123 

processes 116 

sending in e-mail 65 

User Group Maintenance 92 

user groups 

UI templates 92 

User Option Maintenance 135 

User Tool Maintenance 78 

users 

assigning UI templates 92 

V 

variables, Process Editor 126 

W 

Window menu 18 

Workspace menu 18 

workspaces 

choosing 18 

manage 17 

Z 

zooming SVG images 112 

Index 159

User Guide: QAD .NET User Interface - QAD.com

Create successful ePaper yourself

Delete template?

Save as template?