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
  • Previous Page

    QAD Alerts Release Notes
    March 2013
    These release notes include information about the latest QAD Alerts fixes and changes to QAD Alerts. These changes may affect the way you implement and use the product.
    Important: Review this document and the QAD Alerts errata before proceeding with any phase of a QAD Alerts implementation.
    These release notes are cumulative, with the most recent changes described first. Review the notes for all releases after your currently installed release. Installation and configuration changes may have occurred in those intermediate releases, and unless otherwise noted, apply to the release where they were announced, as well as subsequent releases.
    QAD highly recommends that you implement the latest QAD Alerts release available. Check the QAD Web site to make sure that you have the latest QAD Alerts release notes, installation guide, and installation media:
    Use the following list to find release notes for a specific product:
    Release Notes for Current Release
    Version: 1.3.1
    Date: March 2013
    User Guide: QAD Alerts (70-3094-1.3.1); Installation Guide: QAD Alerts (78-0936-1.3.1)
    Note: QAD Alerts supports the latest .NET Framework version (.NET 4), the latest OpenEdge version (OpenEdge 11), and the latest Tomcat version (Tomcat 7).
    New and Changed Features
    Installer Enhancement
    The installer has been enhanced and now it is more robust and user friendly:
    In scenarios where database security is set up for the QAD Enterprise Applications database, the installer still works fine, with no need of workarounds.
    In Alerts installation, in addition to service name, now port number can be used for the QAD Enterprise Applications database.
    The installer checks the QAD Reference Architecture (QRA) version, which should be 1.1.130 or later. This helps to prevent authentication issues at run-time later on.
    Some parameters are regrouped to make the installer more user friendly and more visually effective.
    Previously when the Alerts installer sent the user name and password to QAD Enterprise Applications to check for user authentication, the password was not encoded. Now the password is encoded.
    Now QAD Alerts uses Atomikos 3.8, which fixes an Atomikos 3.6.5 problem of growing log size.
    Previously when a user logged in to the QAD .NET UI, the user password was not encoded. Now the password is encoded.
    Previously in Alerts Queue Monitor, for alert messages with ID greater than 1000, detailed content of the message could not be shown. Now all message contents can be displayed.
    Release Notes for Release 1.3
    Version: 1.3
    Date: September 2012
    Documentation Updates
    The following documents have been updated for this release:
    User Guide: QAD Alerts (70-3094-1.3); Installation Guide: QAD Alerts (78-0936-1.3)
    New and Changed Features
    Product Name Change
    The product name has been changed from QAD Workflow Alerts to QAD Alerts.
    Tab Name Change
    In Alert Maintenance, a tab name has been changed from Assign Users/Roles to Restrict Users/Roles, since the tab is used to restrict access to the alert rather than assigning the alert to selected users/roles.
    Installer Enhancement
    The installer has been enhanced and now it is more robust and user friendly. Now during installation, the installer checks the following configurations:
    Active Maintenance license in QAD Enterprise Applications
    SQL service/port of the qaddb database
    QXtend Inbound availability
    User name and password for QAD Enterprise Applications
    E-mail settings
    These configuration validations greatly help to prevent installation issues.
    Language Support
    QAD Alerts now fully supports the following languages:
    Castilian Spanish
    Latin Spanish
    Brazilian Portuguese
    Simplified Chinese
    Traditional Chinese
    Alerts can now send e-mail through an SMTP server that requires authentication.
    Previously, when Alerts was used with some early SE versions, an error about missing fields appeared when users tried to run any subscription maintenance function. Now Alerts can work properly with these SE versions.
    Previously, QXtend e-mail service was sometimes affected by Alerts and did not always work properly. This is fixed and now both QXtend and Alerts can send e-mail properly.
    Known Issues
    When the installer sends the user name and password to QAD Enterprise Applications to check for user authentication, the password in the request QDoc is not encoded and thus appears in the qdocRequests.log file of QXtend Inbound. If you do not want the password to be there, just manually remove it from the log file.
    If a user sets Alert Delay for an alert while the Maintain State option in the corresponding Alerts profile is not selected, alerts cannot be sent out. Therefore, if you use Alert Delay, make sure that the Maintain State option is selected in the corresponding Alerts profile. If you are not sure about the Maintain State option, check with the person who defined the Alerts profile.

    Previous Page