|

![]() xTuple ERP 3.0 won the LinuxWorld product excellence award for best Business Application! Read more here!
![]() xTuple has also been recognized as a "Market Leader" by CRM Magazine, for "helping companies streamline business processes, maximize profitability, and provide more value to customers" with the integrated CRM functionality in xTuple ERP.
|
If these terms seem confusing now, they shouldn't by the time you finish reading. The aim of this section is to clarify these definitions with concrete examples showing just how Events work. Perhaps the best way to begin is to imagine a manufacturing scenario. For the purpose of this exercise, let's say we manufacture plastic flowers. One of our bestsellers is Item BOQ-002, whose Bill of Materials appears below: ![]() Bill of Materials for Manufactured Item
Rather than consider all the available Events at once, let's look at one which might affect Item BOQ-002. Let's consider the Event called "WoQtyChanged." This Event occurs, or is triggered, if a user ever changes the quantity of a Work Order. To see this Event in action, we will create a Work Order for 100 units of Item BOQ-002. The following screenshot shows the Work Order we are creating: ![]() Work Order for Manufactured Item
To initiate the Event, we will need to change the Work Order quantity from 100 units to some other quantity. But before we do that, let's make sure our test user is subscribed to this Event within the Work Order's supplying Warehouse (i.e., Warehouse EAST). Users must be subscribed to an Event if they are to be notified when the Event occurs. NoteUsers must be subscribed to an Event if they are to be notified when the Event occurs. We can verify which Events our user is subscribed to by opening the User Preferences screen found in the System Module. On the User Preferences screen, select the EVENTS button. The following screen will appear: ![]() User Event Notification Screen
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|||||