1 / 17

Customization - Change objects

Customization - Change objects.

cosima
Download Presentation

Customization - Change objects

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Customization -Change objects

  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.

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

  4. Color chart: buffer colors • In thecolorselectionupto 4 colorscanbesaved. • Usetheslidertosetupyourdesiredcolor • Double rightclick on thedotwhereto save thecolor • Later, youcanselectthesavedcolorbyclickingthedot.

  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.

  6. Crtl+Double click on columns • In be.as-screenscolumnpropertiescanbechangedwithCrtl+doubleclick • Title • Fonts: bold, italic, color • Help (Tooltip, Quickinfo) • Conditions • Behaviorwhenchangesarecarried out

  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

  8. Mandatory input • In thetab „conditions“ a fieldcanbedefinedasmandatory. • Select thecolortobedisplayed, ifthefieldisempty • Enable „inputmandatory“ • Optional: enter an errormessage. Ifnoerrormessageisentered, a standarderrormessage will beissued

  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

  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.

  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.

  12. Analysis of source code An if-condition begins with if <value1> <comparison operator> <value2> then // condition applieselse // 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.

  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.

  14. Analysis of source code if<dw_1.item.tl:[dwo-row].value> n<= 4then 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

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

  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.

  17. Thank you for your cooperation!

More Related