{"id":3104,"date":"2019-03-25T17:42:43","date_gmt":"2019-03-25T20:42:43","guid":{"rendered":"http:\/\/xexeu.elipse.com.br\/pt\/automation-in-code-generation-lesson-7-events-for-script-execution\/"},"modified":"2020-04-08T13:55:59","modified_gmt":"2020-04-08T16:55:59","slug":"automation-in-code-generation-lesson-7-events-for-script-execution","status":"publish","type":"post","link":"https:\/\/kb.elipse.com.br\/en\/automation-in-code-generation-lesson-7-events-for-script-execution\/","title":{"rendered":"Automation in code generation: Lesson 7 – Events for script execution."},"content":{"rendered":"
\n

After you have finished the script, all you need to do is to decide in which event it will be executed.<\/p>\n

Since this is an auxiliary code, which will only run once (considering it has already been tested, and is working properly), the script can be executed from a button on any screen. After this process is done, the button can be deleted.<\/p>\n

\"\"<\/div>\n
Fig. 7.1: <\/b>Temporary button for script execution.
\n<\/span><\/div>\n

Another possibility is to leave this and other auxiliary scripts on a specific screen that can only be accessed by the Administrator.<\/p>\n

It is also possible to execute scripts at run time (in Studio), via CustomConfig <\/i>method. You can create an auxiliary XControl or XObject specifically for running the script in this event. Likewise, the object can be deleted by the end of the process.<\/p>\n

To learn more about CustomConfig <\/i>event, we recommend reading the following article:\u00a0 <\/b><\/p>\n

ElipseX’s CustomConfig.<\/a><\/p>\n

NOTE<\/b>: The demo application below demonstrates all the concepts shown in this series of articles. The commands are created via scripts, and they are set up from a
\n“.csv” file.<\/span><\/span><\/p>\n

Related articles<\/h3>\n
\n