In order to bring you the best possible user experience, this site uses Javascript. If you are seeing this message, it is likely that the Javascript option in your browser is disabled. For optimal viewing of this site, please ensure that Javascript is enabled for your browser.
Login  |   On Demand  |   Home  |   qad.com




Application Changes
If upgrading from a previous version of the QAD .NET UI, be sure to review the release notes for the versions between your current version and this version.
InBox Messages to Inactive Users
Previously, you could send InBox messages to inactive or nonexistent users without getting an error message. This issue has been resolved so that you now get an error message (“The following addresses were not recognized”) when you send or save the message.
Browse Maintenance Print
You can now print the visual relationships between tables shown in Browse Maintenance by choosing File > Print.
Refresh Button on Browse Toolbar
The browse toolbar now includes a refresh button next to the paging buttons so you can easily refresh the display of browse data. The refresh button is included on both drill-down and lookup browses.
Generalized Code Scrolling Improvement
Fields with generalized codes allow you to scroll through a pull-down display of field values using the up and down arrow keys. Previously, you could mistakenly change field values while using the arrow keys. Now, when the up or down arrow key is used, it first opens the pull-down instead of immediately changing the field value.
Browse Option for Switching of CSV Delimiter
In many non-US English environments, the delimiter for CSV export/import is a semicolon rather than a comma. You can now specify the delimiter in the client session configuration file (client-session.xml) browse settings (<Browse>...<csvdelimiter>,</csvdelimiter>...</Browse>), where the default is a comma.
Browse Timeout Configuration
Previous releases have introduced browse performance controls that can be configured in the client-session.xml file’s <Browse>...<Notification> settings. Additionally, the QAD .NET UI includes a mechanism to set the timeout on a browse “get all records” request to a single value with a <TreatGetAllAsOneRequest> setting in the client-session.xml configuration file. The “get all records” request is actually a series of requests to the server. Setting the parameter to false will treat each request separately for timeout. Setting the parameter to true will use one timer for the set of requests. Suppose the timeout value is 5 minutes and 3 calls are made, each taking 4 minutes. A false setting would not time out, as no single request exceeds 5 minutes. A true setting will time out on the second request, as the 5 minutes is used up.
Configurable Screens Added Frame Correction
Previously, an added frame was appearing only on the first line of a multi-line frame. This issue has been resolved.
Messages Display To Column
The Messages display includes a To column along with the columns for From, Date, and Subject.
Browse Control Default Changes
Previously, the browse control defaults were to provide no warnings and then cancel all long-running browses after five minutes. Now, the defaults are to provide warnings after two minutes and then cancel all long-running browses after three minutes. These browse control settings are specified in client-session.xml. The new setting is: <timeout browseId="" warnAt="2" cancelAfter="3"/>.
Metric Pie Chart Placement
Previously, the bottom metric pie chart was placed too far to the right if there was a horizontal scroll bar to the right when the group box was expanded. This issue has been resolved.
Operational Metrics Screen Focus Correction
Previously, a focus issue was causing the screen to scroll to the top or side when any chart was hovered over by the cursor when scroll bars were present. Now the focus goes to the chart that was hovered over, and the screen jumps to that chart instead of the top of the page.
Operational Metrics Print Format Correction
Previously, when you printed a metric with charts expanded that were high enough to span multiple pages, the charts could sometimes get cut across two pages instead of being kept on the same page as one chart image. This issue has been resolved.
Operational Metrics Print Memory Correction
Previously, in Operational Metrics, using Print or Print Preview from a metric that has never had its history charts expanded could result in an out-of-memory error and in some cases cause a red X to be displayed on the screen. This issue has been resolved.
Operational Metrics Target Range Correction
Previously, the metric editor target-range dropdown control did not change the number field when the dropdown was set to 1. This issue has been resolved.
Operational Metrics Autosizing Correction
Previously, a metric group display was not resized after the creation of a new metric in a group. This issue has been resolved.
URN Support for Browse Collections
The system’s URN format can now specify browse collections, using the format urn:collections: collection_ID.
Browse Cancel Button
The toolbar for browses includes a Cancel button so that users can stop long-running browses.
AIA Timeout Setting
The browse performance controls apply in AIA environments, but for other types of requests in AIA environments, you can configure the AIA timeout setting in the client-session.xml files’s <AppServer>...<Timeout> setting (in seconds). The default setting of 0 directs the system to use the Progress default, which is 100 seconds.
Operational Metrics History
With the QAD Operational Metrics History, you can view changes in operational metrics over time. The system stores the history of operational metric activity and then generates charts of the data for you.
You can then explore the chart data further, change the time range, scroll right and left or zoom in and out of particular areas of interest, and export the chart data to Excel for further analysis.
When you open an operational metric page, the system uses the most recent history data to display the initial view of the metric page if the data is less than 24 hours old. This allows the page to be displayed more quickly than if the underlying metric browses were queried to retrieve the data.
The system saves history data whenever the browse queries for the metrics are run. In addition to the history data, a pie chart that summarizes the metric results is also saved so that the Operational Metrics View process map can show the most recently generated results.
The system queries the metric browses (and saves history data) in the following situations:
When you click an operational metric’s Refresh button.
When you open an operational metric and the history data is more than 24 hours old. (Note that 24 hours is the default; the interval is configurable and applies to all metrics in the system.)
When the QAD_OpMetricsAutoRun report is run. Typically, this report is run when metrics are scheduled for periodic running, but if a report administrator runs this report from the report designer, it also runs the metric and its processes.
The history data is never deleted from the system.
A new “as of” label next to the metric name indicates the date and time of the metric data being displayed. If the browse queries are currently running, “loading...” is displayed next to the metric name; when they finish running, the “as of” time shows the current time.
Metric history data will contain at most one history record per day for a given metric. If the metric’s browses run more than once in a given day, the history reflects the most recent run.
Configuring Operational Metrics History
Configuring operational metrics history includes the following:
Operational Metrics History Update Interface
Operational Metrics History and the QAD Reporting Framework
Operational Metrics History Update Interval
By default, if operational metric history data is more than 24 hours old, the system updates the data (by running the metric browses) when you launch a metric collection. Otherwise, the most recent history data is used to display the metric more quickly.
You can change the time interval by adding (and modifying) the following to the client-session.xml configuration file:
<Metrics>
...
<StaleDataAllowedHours>24</StaleDataAllowedHours>
...
</Metrics>
The time interval applies to all metrics in the system.
Operational Metrics History and the QAD Reporting Framework
Operational Metrics History uses the QAD Reporting Framework report server’s scheduled batch mode to auto-run a special report that runs the desired metric and generates and stores metric history data. The new QAD-supplied report, QAD_OpMetricsAutoRun, is used for auto-running the metrics in scheduled batch mode.
Your system must be configured to run scheduled reports in scheduled batch mode (see the Scheduled Batch Mode section in the Reporting Framework User Guide’s Administering Reports chapter).
Additionally, the Set Up a Scheduled Batch section in the Reporting Framework User Guide’s Administering Reports chapter describes how to create a parameter file to contain command line parameters with fixed values, using a params.pf file as an example. In that file, you must add the following line in order for the metric report to run properly:
-enable:qad.plugin.opmetrics
Using Operational Metrics History
With the QAD Operational Metrics History, you can view changes in operational metrics over time. The system stores the history of operational metric activity and then generates graphs of the data for you.
For example, in the Sales Orders metric collection, open the Sales Orders Past Due metric. Notice the thumbnail images to the right of the displays for Past Due Orders and Past Due Cost. Click on the thumbnail image for Past Due Orders:
When you click on the chart thumbnail, a metric history chart displays:
Navigating the History Chart
Under the thumbnail image of the chart, click the icons that allow you to:
Change the time range of the display (1 week, 1 month, 3 months, 6 months, 1 year, 2 years, 3 years).
Toggle the Zoom control to:
Zoom in
Zoom out
Zoom horizontally
Zoom vertically
Export the history data to Excel for further analysis.
Detach the chart to a separate window to enlarge the view.
You can also click-drag to navigate the metric history chart.
If you mouse over a data point, it shows you its value. The color of the dot on a given day corresponds to the metric result for that day. Boundaries for the result ranges (where red indicates an error, yellow indicates a warning, and green indicates good) are also displayed on the chart as colored dotted lines.
Clicking the chart thumbnail again hides the metric history chart.
Scheduling Batch Processes for Operational Metrics History
Although metric history gets generated whenever a user manually refreshes a metric (or opens a metric that does not have recent history data), you can schedule metrics to be run at regular intervals to guarantee the regular creation of history data. For example, you might want to schedule a certain metric to be auto-run daily and a different metric to be auto-run weekly.
Operational Metrics History uses the QAD Reporting Framework report server’s scheduled batch mode to auto-run a special report that runs the desired metric and generates and stores metric history data. This must be configured as described in Operational Metrics History and the QAD Reporting Framework.
Scheduling and Running Batch Processes
You can schedule and edit these batch processes directly from a metric display.
From the toolbar, choose Schedule to schedule batch processes:
The Schedule pull-down options include:
New — schedule a new batch process. Enter a valid batch ID.
Note: Batch IDs must first be defined by an administrator using Batch ID Maintenance. It can be useful to name the batches according to the time interval at which the report server is configured to run that batch. For example, you might define a batch called “daily” that is configured to run every day and another batch called “weekly” that is configured to run once a week. When a batch ID is specified by the user, the metric auto-running only occurs if a report server is configured to process that batch ID.
View Schedule — view currently scheduled batch processes in a browse. You can view further details and modify the batch process by right-clicking on the ID and choosing Scheduled Report History, Parameters, and Scheduled Report Maintenance. Use Scheduled Report Maintenance to modify batch details. (See the Reporting Framework User Guide’s Maintaining Scheduled Reports section for further information.)
View History — view previously run batch processes in a browse that includes their status, such as New, Waiting, Running, Complete, or Error. (See the Reporting Framework User Guide’s Viewing Report History section for further information.)
Saving Operational Metrics as Favorites
To save a metric as a favorite, you can either:
Drag the menu item for the metric from the Applications pane to the Favorites pane.
When the metric is open, click the Add to Favorites button in the toolbar.
Important: These two ways do not create the new favorite in the same way:
When you drag the metric from the Applications pane to the Favorites pane, the new item in the Favorites pane points to exactly the same metric with the same history data. Clicking on the favorite opens the same metric as clicking on the metric in the Applications pane.
When you click Add to Favorites, however, a new metric is created and the new item in the Favorites pane points to the new metric. The reason it creates a new metric is that you are free to make custom changes to it before saving it as a favorite. As with all favorites, the new favorite metric is only visible to the user that saved it. Although the new favorite can have the same name (by default) as the one on the Applications pane, clicking on the favorite opens the new metric. Although the new metric is based on the same browses, the history data saved for the new metric is different. Additionally, the new metric saved as a favorite by using Add to Favorites does not have the scheduling functionality.
Note: If you want the metric saved as a favorite to be the same metric (with the same history data) as the one on the Applications pane, be sure to drag the menu item from the Applications pane to the Favorites pane.
Attaching Metrics History Manually
Metrics history is attached to specific metrics collections, which reside as XML files on the QAD home server. If these XML files are replaced by new or modified files (during an upgrade, for example), the system reconnects the existing history to the new XML files. However, in some cases, due to certain changes in the new (or old) XML files (changes in metric names, for example), the history might not get reconnected. To address this, a history connection screen can be enabled, allowing an administrator to manually connect the history to metrics. To enable this feature:
1
Edit the client-session.xml file, and find the <Metrics> element.
2
Inside the <Metrics> element, add the following:
<ManualAttachHistory>true</ManualAttachHistory>
3
Launch the QAD .NET UI client.
Now, when an administrator (someone with access to create metric collections) runs a metric and right-clicks on the metric name, there will be a History menu item with the following options:
Merge — this brings up a window in which the current history chart will be displayed along with a chart in which can be displayed one or more sets of history that are available to merge with the current history.
Replace — this brings up the same window as above, only the selected history set completely replaces the current history, instead of merging with it.
Unlink — this disconnects the metric from any history, allowing history to start fresh.
The changes done in all three cases only take effect if the collection is saved using the Replace option.
Connection Manager: Secure Shell (SSH) Default
The Connection Manager now specifies secure shell (SSH) rather than telnet by default. To view and change the settings, in Administration | Connection Manager, under Functions, click Update configuration settings:
Host
The machine name or IP address of the SSH or telnet server.
Port
The port number for SSH or telnet. The default is 22 (SSH). For telnet, the port number is 23. (Previously, the default was 23 for telnet).
Protocol
Specifies the connection protocol as ssh (the default) or telnet. (Previously, the default was telnet.)
Startup Script
The server log-in prompts and the responses to these prompts, separated with the pipe symbol (|). The standard order is:
loginPrompt|userid|passwordPrompt|$PASSWD|osPrompt|cd UIConfigDir|osPrompt|startScript
For example:
login:|mfg|Password:|$PASSWD|$| cd /user/mfg/work|$|exec /user/mfg/work/scripts/connmgr.wrap
Note: The same startup script can be used for both SSH and telnet. If using SSH, the login credentials in the script are ignored if they are specified in the Server Startup User and Server Startup Password settings. For SSH, if you have defined Server Startup User and Server Startup Password, you can remove the login credentials from the script but the first four token delimiters must still be included in the script. For example, for telnet, the script might be:
login:|mfg|Password:| $PASSWD |$|cd /user/mfg/work|$|exec /user/mfg/work/scripts/connmgr.wrap
For SSH, however, with the login credentials defined in Server Startup User and Server Startup Password, the script can be:
||||$|cd /user/mfg/work|$|exec /user/mfg/work/scripts/connmgr.wrap
Server Startup User
Specifies the user ID of the server startup user, if not specified in the startup script. (This new setting is only used for SSH.)
Server Startup Password
The password for the session startup script, if not specified in the startup script. It is encrypted on entry.