1. Customization

2. Crtl + Double Click in beas
Just like in SBO, now you can carry out modifications directly on the surface by
Crtl-double click. Text and background can be formatted (font, color etc.)

3. Color chart: buffer colors
In the color selection up to 4 colors can be saved.
Use the slider to set up your desired color
Double right click on the dot where to save the color
Later, you can select the saved color by clicking the dot.

4. Restrictions, technology
If the text was changed, it is not translated when switching to another language.
Text change is a customized feature.
be.as converts entries into „beas-script“ and determines previous entries from the automatically generated source code. This code begins with [autoscript] and ends with [/autoscript]. It is stored in the customer specific directory, which need to be distributed to make the changes effective.
An automated distribution is planned for the future. See next topic.

5. Crtl+Double click on columns
In be.as-screens column properties can be changed with Crtl+double click
Title
Fonts: bold, italic, color
Help (Tooltip, Quickinfo)
Conditions
Behavior when changes are carried out

6. Tooltip
Using this funcion you can store helping notes for important fields.
If the cursor is moved over a field, which currently has not the focus, the tooltip as displayed in a balloon

7. Mandatory input
In the tab „conditions“ a field can be defined as mandatory.
Select the color to be displayed, if the field is empty
Enable „input mandatory“
Optional: enter an error message. If no error message is entered, a standard error message will be issued

8. Mandatory input
Mandatory input becomes active after the window is repoened.
A check is only performed when changes have been carried out in the screen.
Update

9. Error status
The program can react immediately to a change, eg. an illegal input. Use the tab „contents changed“ to enter source code. As long there had been no change, an example code is presented. To enter code, remove the „|“ at the beginning of the line.

10. Error status
Example: we want a value >4 to be entered. Therefore, the content of the field (in this case <dw_1.item.tl:[dwo-row].value> is checked for a value <= 4. If this applies, an error is issued, the status is set to „error“, the fields gets the focus again.
// Iddle Time > 4
if <dw_1.item.tl:[dwo-row].value> n<= 4 then
dw_1.item.tl.status=error
message=error$$Please insert a value > 4
dw_1.item.tl.setcolumn
else
dw_1.item.tl.status=ok
end if

11. Analysis of source code
An if-condition begins with if <value1> <comparison operator> <value2> then
// condition applies else
// condition does not applys
end if
Correct systax is important, do not enter too many blanks. Be.as does not check the syntax for accuracy. Variables are in brackets <…> , strings do not need quotation marks. Nested if-commands are not allowed.

12. Analysis of source code
Value in columns:
<dw_1.item.tl:[dwo-row].value>
dw_1 = the form. Up to 6 forms can be stored in one window. dw_1 is the standard-form.
item = An object (item) is to be called in this form.
tl = Object name
:[dwo-row] = urrent row. Mandatory, if the form has more than one row
value = field content, is always converted to a string.

13. Analysis of source code
if <dw_1.item.tl:[dwo-row].value> n<= 4 then
Content of „place holder“ is always of type „string“.
If you want to compare it with a number, use the operator „n“. The left and the right part is converted to a number
n< less than
n<= less or equal
n= equal
n> greater than

14. Analysis of source code
Field status:
dw_1.item.tl.status=error
The status “error” or “ok” can be set. In case of “error” the background color defined under “condition” is used. Saving is not possible.
message=error$id$Please insert a value > 4
message = Command for issueing a message
error = Message type: error. Choose between “error”, “ok”, or “info”
id = unique error message number. It is used, if the message is to be stored in different languages. Keep the field empty if you do not need several languages.
Text: text to be issued

15. Distribute changes
After changes have been carried out, these need to be distributed: Addon – Button „developement“ – „Customer specification“ – „Distribute local changes“: The stored source code is copied to the server. Clients transfer changes after the next start.

16. New concepts for adjustments (BETA)
All source codes are saved in the database
New wizards allow easy adjustment
Distribution becomes more easy
Crystal-Reports and Powerbuilder-forms are stored directly on the server in the directory b1_shr.

17. New concepts for adjustments (BETA)
In each be.as and SBO screen any adjustments can be deposited. These are presented in a list, with the possibilitys to enable/disable them. Using the clipboard, changed can be distributed and summarized to an own Add-On.
Extensions can either be global or referring to a specific window.

18. New concepts for adjustments (BETA)
There are different kinds of extensions: functions, window events, column events, mouse click events, menu entries and much more

19. New concepts for adjustments (BETA)
The stored script can be written in different languages:
SHELL (DOS-Shell or DOS-Batch), Jscript, VBScript, beas-Script. VBScript and Jscript are only recommended to be used for own functions

20. New concepts for adjustments (BETA)
Example: Calculator as button (only possible in beas-screens and right click menu)
Typ: „Right Click and Button“. Text „Right-Click-Text“ and the selected picture is displayed in the popup menu. If under „Button-Text“ a text is inserted, an additional button is added.
Example: call calculator
Script: Shell „calc“

21. New concepts for adjustments (BETA)
Result: A button and a right click menu item is added.
Calling this function, the calculator is started.

22. New concepts for adjustments (BETA)
Under which conditions a function is displayed or hidden can be defined in „visibility“ eg. in an SBO screen only if OK is displayed on a button, or if a certain column is clicked or depending on a script

23. Templates
In some lists templates can be stored. In a template the design, order and conditions of display, color and much more can be defined. Up to 6 additional fields can be defined, presenting any information from the database.
A well known example is the item list with pictures.

24. Template-Administration
Call up template administration by clicking the icon right below. There you can create new templates, delete copy or insert them using the clipboard.

25. Templates - General
On the first page the authorizations (function currently not working) the maximum number of lines to be displayed and a title can be entered. It may contain place holders. Printing the list, the title is printed, too. Example of use: current date

26. Template – additional fields
Up to 6 additional fields can be defined. Enter name, SQL-extension, alignment and format.
As result, a list is displayed with 6 placeholders. These are replaced by the SQL-sequence defined here. Use only available tables. As an alternative, Sub-Select commands can be used. Only „string“ is allowed as output.

27. Filter and Sorting
A template can have a filter or a sorting stored. This can be performed on the SQL-Server or later in the displayed list (Sorting (DW)).
If a list is pre-filtered or sorted, this sorting can be applied by clicking the orange arrow.

28. Design Background color, colors, font etc can be adjusted.
Under „Start Script“ a script can be deposited, which is called before the list is built up, for example to place buttons.

29. Design, Columns
In window settings you can define column color, order of display and visibility. This configuration is assigned to the current template.

30. This was meant as a short introduction to the complex topic of Customization. Thank you for your cooperation!