Customization - Change objects

17
Customization - Change objects

description

Customization - Change objects. - PowerPoint PPT Presentation

Transcript of Customization - Change objects

Page 1: Customization - Change objects

Customization -Change objects

Page 2: Customization - Change objects

© beas2009 / Page 2

This documentation and training is provided to you by beas group AG. The documents are neither approved nor in any way acknowledged or endorsed by SAP. For SAP Business One, only the documentation and training officially released by SAP shall be binding upon SAP. SAP shall not be responsible for any content of this documentation and training and this documentation and training shall not be binding upon SAP in any way.

The official current SAP Business One documentation and training for SAP Business One is available at http://service.sap.com/sbocustomer/documentation and http://service.sap.com/sbocustomer/training.

Page 3: Customization - Change objects

© beas2009 / Page 3

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.)

Page 4: Customization - Change objects

© beas2009 / Page 4

Color chart: buffer colors

In the color selection up to 4 colors can be saved. 1.Use the slider to set up your desired color2.Double right click on the dot where to save the color

Later, you can select the saved color by clicking the dot.

Page 5: Customization - Change objects

© beas2009 / Page 5

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.

Page 6: Customization - Change objects

© beas2009 / Page 6

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

Page 7: Customization - Change objects

© beas2009 / Page 7

Tooltip

Using this funcion you can store helping notes for important fields.

If the cursor is moved over a field, which currently does not have the focus, the tooltip is displayed in a balloon

Page 8: Customization - Change objects

© beas2009 / Page 8

Mandatory input

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

Page 9: Customization - Change objects

© beas2009 / Page 9

Mandatory input

Mandatory input becomes active after the window is re-opened.A check is only performed when changes have been carried out in the screen.

Update

Page 10: Customization - Change objects

© beas2009 / Page 10

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.

Page 11: Customization - Change objects

© beas2009 / Page 11

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.

Page 12: Customization - Change objects

© beas2009 / Page 12

Analysis of source code

An if-condition begins with

if <value1> <comparison operator> <value2> then // condition applieselse // condition does not applysend 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.

Page 13: Customization - Change objects

© beas2009 / Page 13

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.

Page 14: Customization - Change objects

© beas2009 / Page 14

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 thann<= less or equal n= equal n> greater than

Page 15: Customization - Change objects

© beas2009 / Page 15

Analysis of source code

Field status:

dw_1.item.tl.status=errorThe 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 messageerror = 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

Page 16: Customization - Change objects

© beas2009 / Page 16

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.

Page 17: Customization - Change objects

Thank you for your cooperation!