Process Maps in QAD .NET UI > Using Process Admin
  
Using Process Admin
You can configure the process map context parameters and process properties using Process Admin. To access Process Admin, select Administration|Process Admin.
Click Refresh to update the view of context parameters and process properties.
Setting Context Parameters
The Process Admin’s Context Parameters page displays variables needed by the Process Editor.
Note: Double-check any changes you make to the settings. A mistake that is easy to make but difficult to notice is a blank space at the end of a value. The value appears to be correct but is really incorrect because of the blank space at the end.
1 Choose Process Admin|Context Parameters and edit the Context Parameters page. For more information, see Context Parameters Screen.
2 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.
3 Click Save when you are done making any changes.
Refresh
When you modify a Process Map context parameter, click Save to save the change, and then Refresh to update the process map function configuration. The screen now displays a refresh status, and indicates when the refresh is complete.
Note: Deleting the browser history also has the effect of refreshing the configuration. You can use Tools, Delete History to delete the Internet Explorer history cache.
Context Parameters Screen
Use the Process Admin’s Context Parameters page to set administration parameters. Typically, these parameters are set for you during the QDT-based installation process for QAD Enterprise Applications — Enterprise Edition, but are described here for your reference.
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 Node Properties and Connector Properties. 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. The default is 30.
Menu Lookup URL
Enter the full URL the system should use to connect to a database when it reads menu records to display in the Program Lookup. The URL is the WebSpeed Workshop path, except instead of /workshop at the end of the URL you have the string for the WebSpeed API menu lookup: /com/qad/nav/xmenu.p?Action=MenuLookup.
For example, if the WebSpeed Workshop path is:
http://host:port/environment/cgi-bin/wspd_cgi.sh/WService=QADMFG_WS/workshop
The Menu Lookup URL would be:
http://host:port/environment/cgi-bin/wspd_cgi.sh/WService=QADMFG_WS/com/qad/nav/xmenu.p?Action=MenuLookup
If the home server and port is http://example.qad.com:17170 and the environment is production-1, the Menu Lookup URL would be as follows:
http://example.qad.com:17170/production-1/cgi-bin/wspd_cgi.sh/WService=QADMFG_WS/com/qad/nav/xmenu.p?Action=MenuLookup
Note that you can verify the Menu Lookup URL by entering it in a web browser; if the URL is valid, an XML listing of menu items is displayed.
Properties Directory
Specifies the directory path where the language properties files are located (such as WEB-INF/pronav/properties).
SVG Directory
Specifies the directory path where the SVG files created with the Process Editor are stored. The path is relative to the TomcatInstallDir/webapps directory.
URL Lookup
Specifies the file to use for generating the listing of programs associated with the URL field in Connector and Node Properties. By default, this is MenuLookup.jsp.
XML Directory
Specifies 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 TomcatInstallDir/webapps directory. For Enterprise Edition, process maps are stored in the TomcatInstallDir/webapps/WEB-INF/pronav/xml/eB3 directory, so the default setting is /WEB-INF/pronav/xml/eB3.
SVG XSL Path
Specifies the path to the XSL file used to convert process files from XML to SVG format, typically WEB-INF/pronav/xsl/process.xsl. The path is relative to the TomcatInstallDir/webapps directory. This file was installed during installation.
Silverlight XSL Path
Specifies the path to the XSL file used to convert process files from XML to Silverlight format, typically WEB-INF/pronav/xsl/process_sl.xsl. The path is relative to the TomcatInstallDir/webapps directory. This file was installed during installation.
Use Silverlight Viewer
Use this option to set the default process map viewer. Default is Yes.
Setting Process Properties
The Process Admin’s Process Properties page displays 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.
The Process Admin’s Process Properties page displays 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.
Note: Double-check any changes you make to the settings. A mistake that is easy to make but difficult to notice is a blank space at the end of a value. The value appears to be correct but is incorrect because of the blank space at the end.
1 Choose Process Admin | Process Properties.
2 Edit the Process Properties page. For more information, see the Process Properties Screen
3 The process properties variables also display in the Process Properties Menu, but cannot be changed there. The default values can only be changed using Process Admin|Process Properties. The only variable you may need to change is QAD_DT_DOC_ROOT. The values of other properties are determined by QAD.
4 After making any changes, click Apply to save the new values.
5 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 using Process Admin | Process Properties, and delete existing variables.
Warning If you delete any of the QAD-supplied variables, the sample processes no longer work properly.
Process Properties Screen
These variables display in the Process Properties Menu, but cannot be changed there. The default values can only be changed using Process Admin | Process Properties. The only variable you may need to change is QAD_DT_DOC_ROOT.
Attachments
Specifies a full URL or a directory path for locating attachments for easy on-boarding (EOB) process maps. If just a directory path is specified, the link to the attachment will be relative to the URL to the process map (pronav) environment. Note that the pronav URL is shown in the Help | View Configuration menu (search for the “processmapbaseurl” setting).
QAD_CONTENT
Specifies a URL for locating content in a directory under QAD_DT_DOCROOT, such as:
{QAD_DT_DOCROOT}/content/
QAD_CONTENT_IMG
Specifies the directory name for locating content (typically images) such as:
/content/
QAD_DT
Invokes a menu item based on the program name. Set to {QAD_SH}. (Previously set up the API between a process and the 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.
You can append other directories to this variable to locate specific resource files.
QAD_DT_IMG
This variable points to the images directory below the Desktop installation directory defined in QAD_DT_DOC_ROOT.
QAD_HOMESERVER
This variable is a URL that points to the root directory for the QAD .NET UI application home server. The home server URL is shown in the Help | View Configuration menu (search for the “homeserver” setting). Note that the QAD_HOMESERVER setting typically requires a backslash at the end of the URL (example: http://localhost:8080/qadhome/) because this variable is used to define URLs in other variables such as QAD_METRICS_IMAGES.
QAD_IMG
This variable points to the images directory in the process map installation directory defined in QAD_PMAP_ROOT.
Note: If you want to store your images in some other location, you can create a new variable such as QAD_IMAGES and specify its value as the full path (for example, http://path/images/) to where you are storing the images. The path value must be explicitly specified or you can use the {QAD_PMAP_ROOT} or {QAD_HOMESERVER} variables as part of the path.
QAD_IMG_DOCUMENT
This variable points to the image file used as the icon in a node when in the Process Editor you select the Choose Document option from the Link pull-down in Node Properties. The image file is located in the directory set by the {QAD_IMG} variable.
QAD_IMG_MENUITEM
This variable points to the image file used as the icon in a node when in the Process Editor you select the Menu Lookup option from the Link pull-down in Node Properties. The image file is located in the directory set by the {QAD_IMG} variable.
QAD_IMG_PROCESS
This variable points to the image file used as the icon in a node when in the Process Editor you select the Process List Lookup option from the Link pull-down in Node Properties. The image file is located in the directory set by the QAD_IMG variable.
QAD_METRICS_IMAGES
This variable uses a JSP page to retrieve operational metrics images from the home server.
For example,
{QAD_HOMESERVER}GetMetricImage.jsp?config=env-1&key=
For the config= setting, enter the environment name (for example, env-1). The key element of the variable is used to import operational metric images into process maps. See Creating Browse Operational Metrics.
QAD_PMAP_ROOT.
Specifies the URL to where the process map environment (pronav) is installed. (The default setting is http://localhost:8080/pronav/). The URL is shown in the Help | View Configuration menu (search for the “processmapbaseurl” setting). Note that the QAD_HOMESERVER setting typically requires a backslash at the end of the URL (example: http://localhost:8080/qadhome/) because it can be used to define other variables, such as QAD_IMG.
QAD_PV
This variable opens the Process Viewer (default is ProcessViewer.jsp?ProcessName=).
QAD_PE.
Use this variable to open the Process Editor
(default is ProcessEditor.jsp?Action=load&ProcessName=).
QAD_SEARCH
This variable specifies the URL for searching the QAD Document Library (default is http://search.qad.com/search?site=qad_proddoc&client=portal_doclib&output=xml_no_dtd&proxystylesheet=portal_doclib&getfields=*&proxyreload=1&filter=p&access=p&q=).
QAD_SEARCH_LBL
This variable specifies the text of the link on process maps for searching the QAD Document Library (default is Documentation Search).
QAD_SEARCH_LOCALE
This variable specifies the language code for searching the QAD Document Library (default is en).
QAD_SH
This variable is the QAD Shell URL for invoking a menu item based on the program name (qadsh://menu/invoke?menuitem-alias=). For example, for Sales Order Maintenance, you would use sosomt.p as the program name.
QAD_SH_MENU_KEY
This variable is the QAD Shell URL for invoking a menu item based on the program key (qadsh://menu/invoke?menuitem-key=). For example, for Sales Order Maintenance, you would use 7.1.1 as the program key.
QAD_SH_REPORT
This variable is the QAD Shell URL for invoking a report based on the report code (qadsh://report/invoke?report-code=).
Multiple Language Support for Process Maps
In a process map, each node has a label that specifies the text that is displayed on the node. Although you can enter text directly in the Label field, a better approach is to reference a label key.
The process maps include many label keys whose text has been translated into multiple languages. You can review all the available label keys using Process Label Maintenance (see Process Label Maintenance).
If you are customizing a map and cannot find a label that you would like to use, you can create a new label key using Process Label Maintenance. You can then reuse that label key in other maps you create rather than re-entering the text, which can help assure consistency.
Process Label Maintenance
Administrative users can use the Process Label Maintenance program to create and maintain each label key and its associated text for all the available languages.

Process Label Maintenance
From the Language pull-down, select a language; the text for each label is displayed in the selected language. You can search on any label key from the Search field. From the Records per page field, specify the number of records displayed on a page, and use the First Page, Prev Page, Next Page, and Last Page icons to view each page.
Editing Label Text
You can edit the label text simply by placing the cursor in the text area and modifying the existing text. Fields with modified text display a yellow exclamation mark (!) next to them to show they have been modified. If you want to save the modifications, click the Save button in the lower right corner of the screen.
Adding New Label Keys and Text
To add a new label key and text, click the New button in the lower right corner of the screen. In the Process Label Maintenance pop-up window, enter the label key in the Key field and the label text in the Text field. The label key format should be in uppercase with no spaces (for example, ADD_ASSETS). Finally, click Save to add the new label key and text. Note that if the label key you enter is the same as an existing label key, the existing key will be replaced by the new one.
Deleting Label Keys
To delete a label key, select the check box next to the label key and then click the Delete button in the lower right corner of the screen. Do not delete a label key unless you are sure you will no longer need it.
Note: A button to access the Process Label Maintenance program is also available from the Process Viewer. The button is located in the upper left corner, next to the button for accessing the Process Editor from the Process Viewer.