Script editor

Script Editor - a custom communication platform application

"Incoplax". The platform executes arbitrary scripts

(IVR and

A script describes what happens to a call or process: that the caller

He hears what he presses, where he is transferred and what is recorded. Editor -

a workplace where administrators assemble a script from components, configure

and save to the server.

This section is about working in the editor itself. What does each component do? its properties and how it behaves on the server side are described in the references

documentation sections; here the components are considered only as what

the administrator puts it on the map and configures it.

What the editor can do

Basics: scenario map, visual assembly of the algorithm from components and connections, assigning properties, renaming components and script, changing

script code, four ways to set a value - constant, variable,

expression, template, - checking expressions on the server, mutual conversion

expressions and templates, working with script variables, loading sound

files and listening to downloaded files (WAV and MP3) without leaving the editor, copying sections between scripts, undoing and redoing actions, searching

throughout the contents of the script.

On top of this - tools that pay off in scenarios more than a dozen

steps.

Branch trace

Shows where the call will go from the selected point and where you can get into it. Everything that is not in the way goes out.

Previous versions and differences

List of saved versions of the script. Any two

are compared, changed components are highlighted on the map, any version

is being restored.

Variables with mention count

You can see how many times each variable used and where exactly. Renaming replaces the name in all occurrences,

which you will mark.

Syntax highlighting

In expression and template editors - code markup,

function tree, variable name substitution.

Switching off components

A section of the scenario is excluded from work, remaining on the map: you don’t have to take it apart and put it back together.

Launching a service script

The service script is launched for execution

directly from the editor, immediately after saving.

Notifications from a running script

The script sends them itself, the editor

shows cards in the corner of the window. The most practical way to debug: you can see where the script is located and what is in its variables.

Search with transitions

Search by property names and values; based on the findings you can

go back and forth, the card itself reaches the next one.

Mini-map

The entire scenario and screen position in the corner of the field.

Light and dark themes: Switch on the fly, including the map. Diagnostic log:: Exchange with server and tab events; uploaded by report

for support, without script content.

Legend

Keys

Typed like this: Ctrl+F, Alt and arrow, Esc. The sign + means

that the keys are pressed together.

Interface elements

The names of tabs, buttons and fields are in italics: tab Properties, Save button, Argument field.

Screenshots

Filmed in a light theme. All examples are from training scenarios,

There is no real data in the pictures. If you have dark theme enabled, the location

The elements are the same, only the colors are different.

Components

The manual does not discuss the types of components - they are described in the reference book:

utility script components. Here the individual components are mentioned appropriately - as an example of what

is being discussed.

1. What does the script consist of ▶