The editor view is the main view of Djeeni. Here you can create, edit and execute Djeeni processes. On top of the editor view, your username and the name of the process that has currently being edited are shown (grey fill).

Edit section

There are three sections in the view. The first section is called 'Edit', where you can see and edit the current process i.e., the ordered list of the process steps and their parameters. Column A ('Step') shows the names of the process steps; columns B and C ('Parameters') show the name/description and the value of each parameter. Each row contains one parameter of a particular process step while each process step can have zero or more parameters. Mandatory parameters that must have a value, have a different cell background and font colour.

Check section

When the Execute button is pressed on the Process Toolbar, Djeeni first evaluates whether the syntax of all the parameter values is correct. In other words, the program checks if the user correctly inserted all the values of all the parameters of all the process steps. In case the parameter value is valid, the program will display “OK” message in the “Check” column and in the same row as the parameter in question.

If something went wrong, however, the message “Error” will be displayed. Clicking on it opens the error popup window with the details about the error.

Log section []

Here the log of execution of every step is shown. It can be accessed by clicking on the log button in the “Editor Panels” section of the ribbon or at the bottom of the process toolbar.

The rows in the first two columns of the log show parameters of the last execution of each step (note that each step can be ran multiple times in the same execution of a process, if loops are used), corresponding to the rows of that particular step in the editor. On the other hand, the values in the third column of the log do not necessarily correspond to rows of process steps in the editor, because they display the parameters during execution of each process step, repeating on loops and skipping some non-logic steps like comments and messages.

(detailed description of the log for each process step pending - after implementation)