Page

Pops a page in the agent application to assist an agent in their interaction. The popped page can display an image, text styled with basic HTML capabilities, or fields for the agent to enter information. You can use multiple Page actions in your script and include a Next button, allowing the agent to manually move along a sequence of pages. Agent scripting often cuts down on training, improves contact handling, and facilitates more control in the way agents handle contacts. The system can be configured to display screens and popups so that agents can be directed to specific steps while they are handling the contact. The agent is transitioned through a series of pages depending on how the contact responds to certain questions. Page actions call the appropriate pages. Common uses of Page are displaying sets of instructions, steps of a script for the agent to speak, and so forth. Double-click the action to launch the configuration editor. Use in conjunction with Onpageopen action and Pageclose action. To preview a page, use the OnPreview action.

Dependencies

• Any variables created or changed by the Page action will lose their values when any event, such as Onrelease, Onsignal, or other similar event, runs in the script. If data needs to be preserved for use after the call ends, an API call or DB insert should be used via iframe before the Page action ends.
• Be sure to use a Pageclose action to conclude a sequence of Page actions. Not closing out a Page may result in "stuck" contacts as an agent may be able to click Next within the popped page even after the interaction is finished.

Supported Script Types

Generic	Email	Chat	Phone	Voicemail	Work Item	SMS

Comparison of Similar Actions

The following actions have similar functions, but with some key differences: 

Runapp: Pops a custom form and submits information through the Ondata branch.

Page: Pops a page in the agent application. Allows you to create a sequence of items that may follow different branches.

Input Properties

These properties define data that the action uses when executing.

Property	Description
Add Caption	Enter a short phrase that uniquely identifies this action in the script. The caption appears on the script canvas under the action icon.
Title	The title of the HTML page that pops in the agent application.
Raw XML	Reserved. Used to store the Page configuration. Not user editable.
Show Next	Select True or False. When True, inserts the Next button on the HTML page.
Show Back	Select True or False. When True, inserts the Back button on the HTML page.
Style Sheet	Insert a link to an external stylesheet. For example, <link REL="stylesheet" type="text/css" href="style.css">.
Branch Key	Reserved. Used by the Page Property editor. Not user-editable.
Branch Options	Reserved. Used by the Page Property editor. Not user-editable.

Result Branch Conditions

Result branch conditions allow you to create branches in your script to handle different outcomes when an action executes.

Condition	Description
Default	Path taken unless the script meets a condition that requires it to take one of the other branches. It is also taken if the action's other branches are not defined.
Next	Path taken when the user clicks the "Next" button.
Add Custom Condition	Paths created and taken when connecting to secondary actions using Variable Branch Conditions. Click the ellipsis to open the ConnectView Collection Editor to customize these branches.

Configure PAGE Actions

Currently, you cannot configure the PAGE action in CXone Studio. To configure the components of this action, you must use Desktop Studio.