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




Business Events
Previous versions of QXtend Outbound only used database triggers as events; in version 1.6 a business process can also be the event that triggers a business object to be extracted. The term for event-based notification triggers is business events.
Business events enhance your control over when a business object is extracted, including the ability to trigger processing at crucial stages within a workflow.
The term workflow typically denotes a built-in automated approval process that can be applied to any record (or document) created in the system. Essentially a workflow depicts a sequence of operations within a business process. Workflow can be used for various purposes including:
Approve supplier invoices
Release invoices for payment
Notify stakeholders of changes to accounts, GL data, and customer or supplier data
Escalate overdue customer invoices
For example, a sales order typically has a well-defined lifecycle, from entering the sales order into the system, through processing the shipment, then printing and posting related invoices, as shown in Sales Order Lifecycle.

Sales Order Lifecycle
Using business events you could extract a business object for processing if a quantity value or ship-to location is changed on a line item, or promote the business object into a different workflow stage.
In non-direct data publish source applications, events can be database triggers (raised against a specific database table) or business events (raised against business objects). In DDP source application types, business events are the only event type.
You can configure profiles to receive only the business object messages you want based on the business events raised by a source application. For details, see Modifying Profiles. You also can configure subscribers to receive specific profile messages based on events raised by the source application. For details, see Configuring Subscriber Profiles.