batch

Executes beas script, which is saved on another place

 

Function

Description

batch=file=<folder><filename.src>

 

Example: declare all additional global function

In this way you can use global function from different windows

 

in Project folder myfunctions.src

 
global function myfunction1
endglobal
 
global function myfunction2
endglobal

 

in customizing script from window

global function form_preload
batch=<system.projectfolder>myfunctions.src
endglobal

 

Now all additional global definition are available

batch=filename:function()

 

Example

in workordermanagement.src file, placed in project folder

 

function myfunction
//...
end function

 

Execute this:

batch=workordermanagement:myfunction()

 

the file must be in project folder and postfix must be "src"

the function must be defined as "function" and not as "global function"

beas don't declare this function as instance function. It's not visible after executing

batch=convert=<script>

 

example:

define a script in a variable

#define myscript
messagebox=hello world
#end

 

now you can execute this

batch=convert=myscript

 

Imporant: Define only the variable and not placeholder of this variable, otherwise you can have negative effects

batch=column=<dw_1-columnname>

 

Example:

in column dw_1.item.myscript.value a script is saved

for executing this

 

batch=column=myscript

 

Limitation:

keyword dw_x.item or value not supported

only field from dw_1 - current row

batch=column=textfield

Execute a script, which is saved in a text field object from PSR file