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

  • Release Notes for Release 3.3
    QAD Business Intelligence Version: 3.3
    Date: September 2010
    QAD BI 3.3 continues the evolution of QAD business intelligence to bring more modules for analysis and an improved portal with which to explore that data. The data warehouse has been extended to include Purchasing and Inventory schema sets. Extensions in the portal make creating dashboards and reports even easier. The addition of collaboration to the portal changes the user’s interactions from reading data into discussion, analysis, and decision making.
    New Feature Summary
    Collaboration: allows users to have a discussion on a dashboard or its contents, or any other subject, directly in the Portal application.
    Impact analysis: track where any query or visual item is used in the environment, and go directly to the item editor to make changes. This is exposed in a new tab on the item in the library view called “Referenced By.”
    Edit in place: quickly and easily move inside the designers to a component item, jumping to the editor directly. All visual components have a new “information” icon in the upper right corner that shows details about the item.
    Report modifications: Reports are easier to create and run, with more control over parameter positions, report titles and formatting.
    Query Editor enhancements: data can be exported directly to Excel, a count of rows from each query is returned, and a new Test Run button allows for quick testing of a query.
    Inventory: inventory transactions and monthly summary schema sets have been added to the Operations module
    Purchasing: bookings, order history and receipts schema sets added to the finance module
    A new, QAD branded data warehouse designer
    QAD Issue
    Customer Case
    Clicking on a folder in the repository browser would sometimes cause the application to take a long time to display folders. This has been corrected.
    QBI-217, 220, 223
    The portal’s freeform item editor has been redesigned to allow easier and more functional creation of freeform items.
    Internet Explorer would fail to export reports in PDF or Excel format if the BI portals’s tomcat server was not in the list of trusted sites. This has been corrected. Please note that File Download and Automatic Prompting for file download should be enabled in Internet Explorer. Typically these options are automatically enabled if the Portal server is included in the user's Trusted Sites or Local Intranet security zone.
    The parameter selection box now allows the user to type in a value. As the user types into the control, the list of parameters that start with the data being input are displayed in a selection list. The user can either type in the full value, or use one of the values from the displayed selection list.
    Report output in Excel format now correctly places output into Excel rows and columns so that the data can be easily sorted, filtered and otherwise manipulated.
    The Portal’s query designer can export the results of a query run to Excel format, allowing the user to run ad-hoc queries and examine the results directly in Excel.
    All designer views now show the full path of the item being edited in the upper right of the item view. This information is presented when the user presses the blue “information” icon in the upper right.
    QBI-426, 166
    If a report is selected from the Portal with all parameters filled in, or no parameters required at all, the report runs immediately. There is no need for the user to press the run button. Reports that return no information display a status message that no data was returned. Report parameter selections have been moved from a pane at the top of the screen to the left side to allow the user to see all available report parameters without resizing the report parameter selection pane.
    Selected parameter values can be included in the title of the report. To do so, give the name of the parameter in the title surrounded by P{}. For example, a parameter named ‘Territory’ could be displayed in the report title with a string like this: Open inventory amount: P{Territory}
    Items in the designer libraries can now be moved from folder to folder, rather than just copied and the deleted from the source folder.
    When creating a chart style visual item the user can now select one of a set of dimension values in the query to use as the X axis for the chart. This allows the user to easily select dimension values such a month number in year (1 to 12) and month name, sort on the former and display the latter.
    Selections of a column in a grid and report now default to the format of that column as populated in the metadata.
    The internal permanent storage table ‘perm_item_master’ was visible to the user in the BI Portal. This has been adjusted so this table does not appear in the Portal’s query designer.
    Documentation has been expanded for all fact and dimension tables. This documentation is available as a link off the Portal’s “Welcome” dashboard and is included in the metadata release package.
    The CFO dashboard in the Portal uses fact_gl tables. These tables are populated with metrics of interest to those examining the general ledger and require modification at installation time. Documentation for these modifications is now given in the installation guide. See the section on installing the CFO dashboard.
    OM Shipments (fact_om_shipment) now has valid data for the effective date column. This information was not correctly populated in earlier data warehouses.
    Added the sales person assigned to a customer into the customer dimension view. Expanded the AR fact tables to show the 4 sales people assigned to a receivable.
    QBI-369, 363
    Added required date to order management shipment and performance fact tables. The required date can be used to determine if the order was shipped on or before the date that the receiver required the shipment.
    QBI-430, 421
    A number of problems with columns used by the metadata that do not exist in some SE source systems have been corrected. Notably, the tr_hist.tr_qty_cn_adj column is now properly handled in SE and EE databases.
    The portal’s grid and report column formats now default to the metadata’s format. The format values for all end user visible columns have been modified to properly show data formats that the BI portal can use.
    Known Issues
    The BI Portal application cannot run in the same instance of Tomcat as QXTend. (QBI-174)
    Visual items: drill-in using hierarchy the "loading" spinner displays forever. (QBI-181)
    Model changes in RED are not picked up unless a custom model is opened in the Portal, saved and closed. (QBI-127)
    fact_ar_invoice_history has the ‘entered date’ value stored as a degenerate dimension value rather than as a dimensional join. This will change to a full dimension join in future releases of the BI data warehouse. Doing so might cause some queries to need to change in the future. (QBI-26)
    The server-config.xml file includes user and password information for connecting to the QAD BI Portal database. Please secure this file properly with file system permissions. (QBI-176)