# Script editor ## Script view In the main script view, the selected script version is visible. The side panel contains buttons that allow you to slide out the script parameters, unit tests, and logs panels. The script run button is located in the tab **Parameters**.

Figure 1. Script view with the "Parameters" panel slid out

## Editing a script Working on the script is possible thanks to the Monaco editor (the editor supports JavaScript). Initially, it operates in **read-only**mode. To begin, click the **Edit script** button located at the end of the navigation bar.

Figure 2. Script card

The instruction "how to write a service script" can be found in [Scripts (scriptService)](https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/logika-biznesowa/scriptcode/skrypty-scriptservice) and [ScriptCode best practices](https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/logika-biznesowa/scriptcode/dobre-praktyki-scriptcode). ## Variables in ScriptCode within block scope The Eximee platform requires that variables in ScriptCode be declared within block scope. Failure to declare a variable will cause a script error. ## Parameters Modifying parameters also takes place in Monaco (the editor supports JSON notation). When entering a non-empty script for the first time, the parameters will be automatically deduced (if possible) from the script content itself. Below the editor there is a button that allows you to run the script with parameters provided in the section **Test data.**

Figure 3. Parameters tab

Parameters filled in the section **Test data** are not part of the script itself and will not be saved in that version of it! ## Editing inputs/outputs Here we can add or remove the service script's inputs/outputs. Adding or removing an input will also update the run parameters, so after removing a parameter we will lose its possible mapping at the attachment point.

Figure 4. Input/output edit fields

## Script result An additional window appears at the bottom of the screen. There you will find all information about the script that was run: 1. Script execution time given in ms. 2. Script execution logs in the form: | `[OPERATION_TIME] [OPERATION_TYPE]: Operation text` | | --------------------------------------------------- | For example: | `[14:31:22,976] [GET_DATA]: Called getData("GesCustomComponent1","data") and resulted with data z cc` | | ----------------------------------------------------------------------------------------------------- | 3. The result of calling the script (in the log panel), that is, all values defined as output during service script creation, in the form KEY : VALUE.

Figure 5. Script result card

## Monaco editor The editor used in the project is a full-fledged editor, and thus offers us a set of shortcuts to assist with writing. List of the most commonly used keyboard shortcuts: * **Ctrl + Shift + I** - code formatting. After writing any fragment, it is always worth formatting it, as this increases readability and makes work easier. * **Ctrl + Shift + O** - jump to variable/function. This is search on steroids. When scripts grow to a size where they no longer fit on one page, it is worth using such shortcuts to move around the code faster. * **Ctrl + Shift + K** - delete the entire line. * **Ctrl + F2** - find and replace a specific symbol (function name, variable). * **Ctrl + G** - jump to line. * **Ctrl + Shift + Alt + Up/Down Arrow** - clone the cursor above/below. * **F1** - list of all available shortcuts and editor options. ## Tests The editor allows defining [test scenarios](https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/logika-biznesowa/scriptcode/testy-jednostkowe-skryptow). ### Errors during test execution If the script contains errors, during test execution such an error will be logged in the console below the editor. The message will include the cause and the code location where the error occurred.

Figure 6. Test call error

--- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/logika-biznesowa/scriptcode/skrypty-scriptservice/edytor-skryptow.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.