The corresponding Select Event function will open a list of available events, displayed by module, from which you can select your required event.

	This field is only displayed for events containing a parameter entry.

For example: If you select the event Supplier balance > parameter, then an action would be triggered when the supplier's balance exceeds the amount entered at the parameter field.

	This field is limited to 100 characters.

This description is then displayed as a listview column when you select to view the log file.

You can view and report on this log file from within the Event Management Editor by selecting View Log File from the Functions menu.

The From and To dates specify a date range within which the event can be fired.

	These dates are inclusive.

Add and save the new event to the event management file.

Ignore any details captured and return to the listview.

When entering multiple addresses, use a semi-colon (;) to separate recipients.

The e-mail address associated with the buyer is then added to the e-mail list.

	This option is only available for the Inventory event: Goods receipt.

	At least one recipient must be listed in the To field.

When you select this option, the e-mail defined against the requisition user is used, so ensure that this is defined.

	This option is only available for the PO events: Requisition routed to another user (req & receipt) and Requisition routed to another user (req only).

In this scenario, e-mail is sent only when the defined criteria are matched.

	If you do not select this option, then at least one e-mail recipient must be specified at the To field.

	This function applies only for specific Inventory events.

If you select this option, the Event Mail Selections screen is displayed.

Multiple conditional entries for each event are allowed and shall be displayed in this listview.

To add a new entry, select the Add option and enter the appropriate information in the fields requested.

At the Expression prompt you can add the condition under which the email should be sent. This expression can contain keywords such as %wh for warehouse and %oper for the operator code. If multiple keywords are used, separate these with the word AND.

You can select the browse icon to view a list of all programs available for selection.

The NetExpress program that is executed is written automatically to SYSPRO's Job Logging system.

If the program was constructed using standard SYSPRO techniques, then the field LINK-EXTRA will contain the key of the code that triggered the event (e.g. in the case of stock falling to below zero, this would be the stock code itself). For Inventory events, the stock code and the warehouse code are passed to the NetExpress program. The stock code is in position 1-30 and the warehouse code is in position 31-32.

	You can use special reserved words or keywords in this area, which will then be replaced with the corresponding values when the event fires.

To reduce the number of characters used on the command line, you can specify the path to the executable at the Start in field.

This field is limited to 40 characters.

	You can use special reserved words or keywords in this area, which will then be replaced with the corresponding values when the event fires.

This field is optional.

If you do not select this option, then a single message is written to the message inbox irrespective of the number of times the event is activated on the same day.

Activation Point: When the customer's balances are greater than (the customer's credit limit multiplied by the parameter value divided by 100).

For example: Parameter value entered = 90. Customer's credit limit = 10 000. The trigger is then activated when the customer's balance exceeds 9 000 (i.e. 10 000 x 90/100).

	If you are using master/sub accounts, then the credit check is performed against the customer (master or sub account) to which invoices are linked. This event is only fired when the customer's credit limit is exceeded the first time.

Therefore this event is not triggered if the stock on hand for the item is already below minimum and a transaction is processed that further reduces the stock on hand.

Activation points:

Activation points:

Activation point: When the requisition line of a Requisition entry is routed to another user.

	Within the Requisition Entry program you can enable the preference: Trigger event once only when routing consecutive requisition lines to activate this event for each requisition routed to another user, regardless of the number of lines held against the requisition.

When using this event to trigger an email, the keywords %wh and %other are interchangeable within the email body.

If, however, you are defining a conditional email, then the %wh keyword must be used to make the mail conditional on the actual warehouse.

This is because the %other keyword can contain up to 30 characters and will always evaluate the condition on the full 30-characters of the variable.

To make the mail conditional on the stock code, use the %key keyword.

Activation points:

The event is not activated if maintaining an existing line for which the price has already been overridden and the price is changed again. However, the event is activated if the price code is changed.

If an item is receipted into inspection, then the event is activated only when the item is accepted.

Activation point: The event is activated if a failure occurs while printing an invoice and only some lines have been printed, or a failure occurs while the invoice process is in the update phase.