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  |   Cloud ERP  |   Home  |

  •     QAD Glossary

  • QAD 2011 – Standard Edition
    This release includes all ECOs closed between June 11, 2010 and May 23, 2011. A few significant changes introduced with ECOs that modify product features are highlighted in this section.
    .NET UI Updates
    QAD 2011 Standard Edition is supported by the new version 2.9.4 of the QAD .NET UI.
    For information on this change as well as other .NET installation and application changes, see Release Notes: QAD .NET User Interface.
    Enhancements to QAD Reporting Framework
    The infrastructure that supports reporting from operational and financial functions has been improved in several areas.
    Additional Report Output Formats
    Previously, output formats for reports included only Document, Excel, and PDF. You can now also choose from the following additional output formats when a report is run:
    PDF Read-only — The report is rendered as a read-only PDF file. It has a random password that prevents tampering with the document.
    TIFF — The report is rendered as a Tagged Image File Format (TIFF) file.
    RTF — The report is rendered as a Rich Text Format (RTF) file.
    Plain Text — The report is rendered as a plain text (.txt) file.
    The Document and PDF formats offer the highest display quality. Some images and colors may appear differently in some render types (for example, TIFF and RTF), and may not appear at all in others (for example, Plain Text).
    C# Script Objects Added to Report Designer
    .NET Script Objects make it possible to expand the functionality available in the report designer to go beyond VBScript logic. It is now possible to write custom C# (or any .NET language) classes and expose their public methods such that they can be invoked from within VBScript code blocks that execute during report rendering. This is a powerful capability that overcomes the many limitations of the VBScript language and the further limitations imposed by the report framework VBScript interpreter. Now any operation that can be written in a .NET language can be invoked dynamically by reports. This opens the door to performing file I/O, network calls, and custom data structures, for example.
    Layout Selection
    When running a report, you can now select which layout to use from the new Layout pull-down list if the report resource has multiple layout definitions.
    Report Language Selection
    Previously, the language that translations was done in for scheduled reports was the language of the server user ID specified in the command line arguments—not the language of the user who submitted the report. In this release, reports are in the language of the user who scheduled the report, regardless of the server user’s language.
    Report Output E-mail Attachments
    For scheduled reports, you can now have a copy of the report automatically attached to the e-mail notification.
    External Metadata for Data Source Programs
    When developing a data source program as described in Appendix A of the Reporting Framework User Guide, you can now use an alternative to hard-coding the metadata. In this release, Appendix B of the user guide describes how to externalize the metadata in an XML file that gets loaded at runtime. This approach can greatly improve the ease and productivity of writing data source programs.
    Scheduled Reports Printer Setup
    Starting with the QAD .NET UI 2.9.2 (Enterprise Applications 2010.1 Enterprise Edition) release, printer setup for scheduled reports has changed. The Printer Setup Maintenance program is no longer used for the Reporting Framework. Instead, use the following steps to set up a printer for scheduled reports. If you are upgrading from an older version, any scheduled reports that refer to the previous printer types will still execute properly. However, the following steps must still be done to allow printers to be defined for new scheduled reports:
    Set up a physical printer on the report server. From the Windows Start menu, select Control Panel|Printers and Faxes|Add a Printer to add a printer.
    In the client session configuration file (client-session.xml), located in the TomcatInstallDir /webapps/qadhome/configurations/ SysEnvName / directory, set up printers available for scheduled reports as follows:
    <Description>Description of printer (optional)</Description>
    Scheduled Report API
    In addition to scheduling reports from the user interface, you can now use an API to schedule reports programmatically from Progress 4GL code. Contact QAD Support to get a sample bundle ( that gives instructions and the necessary supporting files to access this API.
    Label Terms in Filter Names
    When creating a report filter, the filter name can be a label term such as ${SALES_ORDERS} so that the filter name will be translated.
    Specifying Logical Value of Label Term
    When designing reports, you can now specify to have the value rather than the label display for logical values and value lists:
    ${TERM}V — specifies the value rather than the label
    Setting Default Report Filter in Report Viewer
    You can now specify a default filter in the Report Viewer. When you click Open, the default filter is listed in bold. To change the default filter, click More and set a new default from the list by clicking on the default check box.
    Number-to-Word Function Supports Polish Language
    Previously, the script object function QAD_NumberUtil.ToWords(number) did not support the Polish language. This limitation has been fixed.
    Running Reports with Enter Key
    When running a report, you can now simply press the Enter key to run the report rather than clicking the Run button, thus allowing mouse-free operation.
    Search Field Lookup Enhancements
    When implementing a Progress data source program, fields appearing in the report search panel can optionally have a lookup specified. This is done by specifying the LookupName attribute in the field metadata (see Appendix A of the Reporting Framework User Guide). Previously, only the following possibilities were supported:
    Non-Component Based Browses — Any browse created by Browse Maintenance can be used as a search field lookup, where the LookupName attribute in the field metadata is the program name of the lookup program (if any) that will be invoked from the lookup icon.
    Specifying Component-Based Financial Lookups — When writing data source programs, you can specify component-based Financial lookups in the metadata as opposed to standard browse lookups.
    Now, starting with this release, the following additional capabilities are also supported:
    Passing Parameters to Lookups — The lookup can also have parameters passed to it to dynamically change the behavior of the lookup. For example, a lookup of items may be defined to have a product line input parameter that would filter the item list according to the product line value passed in. The values that can be passed to lookups can either be hard-coded or obtained from values that the user has entered into any other search condition.
    Specifying Conditional Lookups — It is now possible have a search field lookup invoke a different browse depending on the user-selected value in a different search condition.
    Multiple Return Values in Lookup Browses
    Additional navigation has been added to Drill-Down/Lookup Maintenance (36.20.1) that lets you define browse field/frame field pairs so that a lookup browse can return more than one value to the screen when a browse record is selected.
    Use the up and down arrows to display available browse fields for the specified procedure. Then, in Frame Field, enter the name of the field you want to populate in the program when you select a record from the browse.
    You can use this feature to avoid selecting a value in one field, then being required to use additional lookups on subsequent fields to find the exact record you want. When you set up one or more field pairs for a browse field, the system automatically returns values for all specified fields when you select a row/record from the browse.
    Declaration ID on Intrastat Inquiries
    You can use the new Declaration ID field to determine the declaration ID associated with an Intrastat transaction. Previously, reporting functions did not include this information. The field has been added to the following inquiries:
    Intrastat Inquiry (2.22.14)
    Intrastat Inquiry by Invoice (2.22.15)
    Intrastat Inquiry by Supplier Invoice (2.22.16)
    Intrastat Inquiry by Order (2.22.17)
    Declaration ID also displays in Intrastat Maintenance (2.22.13).
    Reallocate Field in Container/Shipper Control
    A new Reallocate field in Container/Shipper Control (7.9.24) lets you specify whether detail allocations are deleted for unshipped lines in Sales Order Shipments (7.9.15).
    Yes: The system reallocates inventory and deletes detail allocations for unshipped lines.
    No: The system does not reallocate inventory and leaves detail allocations for unshipped lines.
    Note: This new field is also available in Customer Schedules Control (7.3.24).
    New Vertex Tax Setting in Work Code Maintenance
    When you use Service and Support Management with the Vertex tax application, you can now apply taxes on labor and parts at the rate associated with the address record of the service provider without using the QAD SE Depot functionality. Previously, this method was used only when Depot functionality was enabled for the associated work code.
    In Work Center Maintenance (11.2.1), set the new Tax at Repair Center field to Yes to use this new feature. When that field is No, the system applies the tax rate associated with the address record of the end user.
    Important: You should review your current work codes settings and adjust them as needed. To enable Depot functionality for a work code, set Repair Center to Yes. To calculate taxes based on the service provider’s address record, also set Tax at Repair Center to Yes.
    Cleanup of Stranded Requisition Records
    A new Release Locked Requisitions utility (5.2.22, utrqrel.p) lets you clean up qad_wkfl records that are created when you run Build PO from Requisitions (5.2.18) and an unexpected system termination strands the records.