Script editor overview


The following permissions:

  • Scripter > Script > All
  • Scripter > PublishedScript > Add
  • Scripter > PublishedScript > View

The script editor appears when you create or edit a script. As a script designer, you can use it to compose and maintain script pages. Define script pages, place components on them, and link pages together to create instructions for agents to follow during inbound or outbound calls.

Click ImageClick the image for information about the editor.

The name of the current script.
The name of the page you are currently editing.
Turns preview mode on or off.
Use this menu to save, publish, or create a template from a script. You can also access properties of the script.
Undo or Redo component-level changes.
Cut, Copy, or Paste (clipboard operations)
Vertical stack container—positions components vertically one above another.
Horizontal stack container—positions components horizontally one beside another.
Displays text that the user cannot modify at runtime.
Adds a pushbutton to trigger an action of some sort.
Text input component—accepts alphanumeric text.
Numeric input component—accepts only numeric digits.
Date input component—for selecting a date from a pop-up calendar.
Link component—adds a hyperlink.
Checkbox component—permits the user to make a binary (yes or no) choice.
Radio button—allows the user to choose only one of a predefined set of options.
Drop down menu—allows one value to be selected from a list.
Image component—adds a graphic image to the page.
Web page component—embeds a web page.
Component Template—inserts component(s) from a template.
Manage pages in a script.
Manage actions a script can perform.
Manage variables used in the script.
Component Visibility—lists components whose visibility is bound to a boolean variable.
Validatation—check the script for errors.
Add components—lists components by name, to make them easier to add.
Place components here to layout a page.
Nesting indicators—identify which component is selected in the context of its parent containers.
Page properties—click to open properties of the current page in the properties pane.
Properties panel—displays properties of the page of the currently selected component.
Shows content of the currently selected tab.
Markdown component—allows you to quickly format text

Configure scripts entirely in this editor. The editor helps manage components on a page and pages in a script. It also helps manage any actions that Genesys Cloud takes when a script starts, loads a page, or responds to the agent. Here, define and manage script variables whose values the agent sees using components.

The editor makes it easy to preview and publish scripts. You can save all or part of a script as a template for others to use. The script editor makes all these activities simple. You don’t have to be a programmer or a web developer to create sophisticated and visually appealing scripts for any type of call.

Script development activities

Add script components

You can easily remove components from a page. In addition, you can cut, copy, or paste components.

Scripts can be simple one-page forms, or many linked pages corresponding to stages of a call.

Every script has properties that apply to the script or to the current page. For example, you can rename a script by changing the value of its name property. You can set a page load action, or save the entire script as a template. Other properties indicate how you use the script—whether for outbound dialing, inbound Architect call flows, or Create Callback actions in Architect.

Manage script properties

Variables store values displayed or updated by components. Each variable is globally available to all pages in a script. When you configure a script to use an outbound campaign’s contact list, its contact columns appear as variables to the script. By binding components to variables, you can update the contact list with data collected or updated by agents.

Actions perform work. For example, an action can display a different script page or evaluate the value of a variable at runtime to run a different sequences of steps.