Release Notes for Release 1.6
QXO Server Version: 1.6
Date: April 2009
QAD Enterprise Applications Compatibility: eB SP4 through current release
QAD QXtend Documentation: Technical Reference: QAD QXtend (78-0691C) and Installation Guide: QAD QXtend (78-0692B)
Important: If you are using QAD 2009 EE or SE, use Qxtend version 1.6.
The application changes made to the current version are grouped by functional area within the product.
1 In the current version, you can use both database triggers and named (business) events to trigger a business object to be extracted. The introduction of named events enhances your control over the processing business objects; for example, you can now trigger processing at crucial stages within a workflow.
In non-direct data publish source applications, events can be either database triggers (raised against a specific database table) or business events (raised against business objects). In direct data publish source application types, business events are the only event type. A warning symbol displays next to the event type if the database trigger is not installed in the QAD Enterprise Applications database. You configure database triggers and business events by using the Event Types option on the Configuration tab tree hierarchy.
Note: Named events have also been introduced for business objects, profiles, and subscribers. For details, see the appropriate section below.
2 You can now view and configure event types—for example, database triggers and business events—for data objects on business objects; only active events are displayed. For direct data publish business objects, all valid event types display for the current business object in the primary top-level data object.
3 Inner join queries can now be added to any data object in a business object for additional filtering. An inner join is essentially a filter that consists of fields and/or tables that may or may not be part of the current data object. The fields and tables in the query do not have to be part of the business object. Using inner joins enhances your ability to extract the types of data you want from business objects in your system. Multiple inner join queries can be combined by using a comma to separate the queries.
4 For business objects that have more than one top-level table, it is now possible to specify which data object is the primary object; the system identifies the raw message based on the value of the data identifier field of that data object. The primary data object is indicated by selecting the Primary check box on the Business Object screen.
5 Direct data publish business objects can now be created for all types of source applications, regardless of whether the source application is direct data publish. If you create a direct data publish business object for a non-direct data publish source application, the system displays a dialog box prompting for the type of business object being created.
6 You can now display a Subscribers report to determine the subscribers that will receive messages based on a business object and the events that will trigger messages. The report displays the following:
• Activated event types
• Profiles related to the current business object that have this event type enabled
• Subscribers that receive these profiles based on the event type
If a profile is not assigned to a message publisher, a warning symbol displays next to the profile name. Similarly, if a subscriber is not assigned to a message sender, a warning symbol displays next to the subscriber name. A tooltip for the warning symbols provides the exact reason. To display the report, click the Subscribers button on the Business Objects screen.
7 Chr(23) has been replaced in the system with a different delimiter and is no longer used. This is because chr(23) is a valid character in some European codepages and causes issues when using QXO.
8 Business events can now be imported into—and exported out of—QXtend Outbound when defining business objects by using the Import and Export buttons at the bottom of the Business Events table on the Event Types screen.
9 You can now specify which events must occur in order for a profile to be published by enabling the Listen check box for selected events. By default the Listen check box is enabled for all event types for the profile.
The event types that are available are the activated event types for all data objects in the business object related to the profile. Hence these event types are related to the profile as a whole, not to a specific data object. The profile event types do not appear when editing a data object for the profile.
10 Fields can now be defined as add-only. When performing data synchronization, certain fields may be maintained in the local domain and not replicated from the master domain, except when the record is created. Setting a field to “Add Only” on the profile causes that field to be published only when the operation is Add.
11 Profiles can now filter on values that are derived from fixed values and calculated programs. In previous versions of QXO, these values were only calculated when the profile was generated. These values are added to the raw message.
12 Fixed value fields now can contain Progress expressions and perform built-in Progress calculations. Fields from the current buffer can be referenced in this calculation by including the XML node name surrounded by dollar (“$”) characters. The expression must start with an equals (“=”) character; for example, =today + 2 and =substring($ptDesc1$,1,12).
13 You can now publish only the rows that have changed by using the Publish Unchanged Rows check box. Publish Unchanged Rows only works when the Detect Operations check box is enabled, and operates similarly to delta QDocs, except at the table—rather than the field—level.
14 You can now specify an operation program to use for a profile by using the Operation Program field. This option is used with the Detect Operation check box. The operation program specified must be a Progress (.p) program specified in the PROPATH. This check box is only used to perform an operation calculation, or if you want to enter the operation value into a different field than the operation node.
15 You can now include an operation node in the QDoc request by selecting the Detect Operation check box. If you specify an operation program, the system determines what the operation is and enters the result into the operation node in the profile. This field affects how the system handles messages during archiving.
16 Individual profiles can now be configured for subscribers. You can select which events must occur before a message will be published for a subscriber. The message will be sent only when certain event types were the original trigger for the raw message.
17 In previous versions of QXO, a delivery schedule applied to all messages sent to a subscriber. In the current version you can define a delivery schedule for an individual subscriber profile by selecting the Use Subscriber Default option on the Sending Option drop-down menu.
18 Subscribers now can be configured so that the subscriber will only deliver a profile message if the operation of the top-level table in the profile matches the subscriber configuration.
19 Although profiles in previous versions of QXO have had fixed values and calculated programs, the current version allows you to use tokens to set these values on the profile based on the subscriber that is receiving them. For example, suppose each subscriber requires a different fixed value for Site, while the other profile data can be the same. A token is represented syntactically by a character string surrounded by “at” (@) characters, and is placed in the fixed value field of a profile field.
Direct Data Publish
20 In the current version, a direct data publish document must have a business event associated with it, otherwise it will not be published. The system verifies that the event is a valid event type for the source application; if the event type is invalid, the system raises an exception.
21 Direct data publish business objects can now be created for all types of source applications, regardless of whether the source application is direct data publish. If you create a direct data publish business object for a non-direct data publish source application, the system prompts for the type of business object being created.
22 Based on the result of processing subscriber messages, the system now can be configured to send
e-mail to the user that generated the event (for non-direct data publish source applications) or to the user defined within the message structure (for direct data publish applications). To do this, select the Email Data Owner check box in the subscriber Configuration Parameters screen, and then select the processing result that will trigger the e-mail to be sent (ERR, MES, or WRN). A status of ERR always results in a message being sent.
23 E-mails are now sent by a dedicated service, freeing up resources used in the message sender service in previous versions. You can view information about the existing e-mail service—for example, e-mails sent, alerts pending, and so on—by using the Dashboard. The e-mail service can be stopped and started as required.
24 The QAD QXtend installer has been significantly enhanced. Using the installer you can now:
• Perform a new installation or upgrade an existing installation. The previous version of the installer only allowed new installations.
• Migrate a QAD QXtend configuration when performing a new install or an upgrade.
• Perform an in-place conversion on the qxodb and qxevents databases using the installer’s upgrade mode.
• Specify additional connection parameters that can be used, for example, when compiling implementation-specific databases.
• Install an additional AppServer that is dedicated to the service interface.
• Define schema area locations for the qxodb database to improve system performance.
• Install QAD QXtend against any of the QAD-supported code pages.
1 The sess-control script can now be used to query the status of individual services. It also can be run in batch mode.
2 You can now filter the output of a view correctly on the Viewers tab. Previously, the filter could not be reset.
3 During data synchronization, the system now correctly handles the start date field in Product Structure Master (ps_mstr). In previous versions this field was replicated incorrectly.
4 The current version of Technical Reference: QAD QXtend incorporates errata that were issued for the 1.5.1 release documentation. The errata sheet is accessible from http://support.qad.com/.
1 To avoid potential issues, QXO triggers for the sct_det and spt_det tables are not deployed for QAD 2009 EE.
2 When installing QAD QXtend using the console mode and a local repository, if the file you specify is not found, no warning is returned; instead, a message displays stating that there is nothing to install on the host.