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
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.
Every definition and declared properties outside the function will be ignored.
If you need additional function, you must declare this INSIDE this function. See compatibility
If you want to see all variables or more details inside a user event, you can define additional debug points in your script
system.debug=mirror // insert all variables in debug window
More see System-> Debug |
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
Here we changed the events from only receipt to 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.
New: Ignore every declaration outside the userevent The system ignore all definition and declared variables outside the userevent
Example: follow was working in past, but not in current version function ReceiptEnd
In past you seen the message, but not in actual version. Reason: The function "test" is declared outside from function "ReceiptEnd" Correct is function ReceiptEnd
New: Every userevent is a Sandbox.
function ReceiptLine Why: This reduce bad mirror effects. |
(<<) StartCalcRoutingPositionBackward
(<<) MiddleCalcRoutingPositionBackward
(<<) EndCalcRoutingPositionBackward
(>>) StartCalcRoutingPositionForward
(>>) MiddleCalcRoutingPositionForward
(>>) EndCalcRoutingPositionForward
fdc
GoodsReceiptPo
Allocation
Transfer
Issue
Receipt
Calc.
manage
time recording