User events

User events  are special events in Beas, like material booking, production control. This events not window based and complete in background.

In this event you can change or can add additional functionality from standard solution, example work order creation, receipt and many more.

 

Called by

- different windows

- Integration hub

- beas service layer

 

 

Here you've the possibility to change the logic or add additional functionality

 

 

Create userevent

1. Open Beas AddOn

2. Open first line

3. Choose Userevent

4. choose the event on right side

5. Insert your script

6. Save (update). The change is active. You don't need a restart. Note: Other machines must be restarted.

 

The system will insert follow function

 
beasscript-logo-small

function CreateWorkOrder
// Script
end function

 

Properties

On right side of the editor you can see all properties, which you can read or write

 

General Note:

If you declare any object, you must destroy it

if you want to read window based informations, you must check, if the function is running inside this user function.

The user event is running in  a Sandbox. Only changeable variables are visible outside this user event.

This reduce bad mirror effects.

 

hmtoggle_plus1Debug

If you want to see all variables or more details inside a user event, you can define additional debug points in your script

 

beasscript-logo-small

system.debug=mirror  //  insert all variables in debug window
system.debug=level=2 // go level 2
system.debug=level=1 // go back to level 1

 

More see System-> Debug
hmtoggle_plus1Compatibility

In past the system used other variable names and other userevent names

All old names are working. Compatibility > 99%

 

But the logic from the program is changed and this can produce trouble

 

Example

Beas 9.1 and older: We'd only single receipt function. It was not possible to receipt more different batch numbers, bin locations or items per document.

 

New:

Now it's possible to make a receipt for more then one batch number, different bin locations or different items
(new PO-Receipt function, new item issue or receipt function, all WEB APPS)

 

Here we changed the events from only receipt to

 
ReceiptStart

ReceiptLine  (same as "receipt")

 

this can produce incompatibility.

 

Problem with "end" and "end function"

If you declare an userevent with  function, the function must end with "end function". In past only "end" was supported. Now the "end function" part is mandatory.