User events

Contents

User events are special events in Beas, like material booking, production control. These events are not window-based and completely run in the background.

In this event you can change or add more functions of the standard solution, for example work order creation, receipt and many more.

Called by

- different windows

- Integration hub

- Beas service layer

Create userevent

1. Open Beas AddOn

2. Open first line

3. Choose User event

4. Choose the event on the 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 the following function:

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 information, 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.

All definitions and declared properties outside the function will be ignored.
If you need additional functions, you must declare this INSIDE this function. See compatibility.

Name of user events changed
In the past the system used other variable names and other user event names

All old names are working. Compatibility > 99%

But the logic of 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.

It is 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 a user event with a function, the function must end with "end function". In the past only "end" was supported. Now the "end function" part is mandatory.

Ignore every declaration outside the user event

The system ignores all definitions and declared variables outside the user event

Example:

function ReceiptEnd
test()
end function
function test
messagebox=Hello world
end function

In the past a message was displayed, but not any more. Reason: The function "test" is declared outside from function "ReceiptEnd"

Correct is

function ReceiptEnd
test()
function test
messagebox=Hello world
end
end function

Note: The end of the sub-function is declared with "end" AND NOT with "end function"

New: Every user event is a Sandbox.
All variables defined with setvar are not visible outside the user event.

Example:

The function ReceiptLine and ReceiptEnd have the same window.
At first, the system executes the ReceiptLine and then the ReceiptEnd function.

function ReceiptLine
setvar=myVariable="Test"
end function
function ReceiptEnd
messagebox=<myVariable>
end function

In old Beas versions the system displayed "myVariable"
In the current version the system displays "<myVariable>", because this is not declared. The "ReceiptLine" is running in a sandbox. The system restores the variables.
You can change only variables, defined in the documentation with "changeable"

StartWorkorderPosition