GCX-SCR Sample Questions & Answers

Overview of Scripting · Types of Scripts in Genesys Cloud

• A

  Inbound

• B

  Outbound

• C

  Inbound Email

• D

  Messaging

Variables in Scripts · Custom Script Variables

• A

  Use string manipulation functions to parse the 'Orders.OrderHistory' variable directly.

• B

  Define 'Orders.OrderHistory' as a String variable and use a loop action to iterate through it.

• C

  Declare 'Orders.OrderHistory' as a Dynamic variable type and use the 'Get At' and 'Count' expressions to iterate through the collection.

• D

  Create separate Boolean variables for 'orderId' and 'status' and map the Data Action output to them.

Script Management · Script and Component Templates

• A

  Export all scripts, perform a find-and-replace on the image URL in the JSON files, and re-import them.

• B

  Create a new 'Component Template' containing the updated image, and then manually replace the old image component with the new template in each script.

• C

  If the original logo was implemented using a 'Component Template', update the URL within that single template and republish all affected scripts.

• D

  Write a Platform API script to iterate through all scripts and update the 'Image' component's source property.

Actions in Scripts · Contact List Integration

• A

  Action: 'ContactList.Add'; Prerequisite: The agent must have the 'Contact Center > Add' permission.

• B

  Action: 'Scripter.Invoke Data Action'; Prerequisite: A custom data action that uses the POST /api/v2/outbound/contactlists/{contactListId}/contacts API.

• C

  Action: 'Outbound.CreateContact'; Prerequisite: The contact list must be associated with the script in the script's settings.

• D

  Action: 'Outbound.UpdateContact'; Prerequisite: The script must be designated as an 'Outbound' script type.

Variables in Scripts · Built-in Variables

• A

  {{Scripter.CurrentDateTime}}

• B

  ToString(Now())

• C

  FormatDateTime(Now(), "yyyy-MM-dd HH:mm:ss")

• D

  DateTime.Now.Format("YYYY-MM-DD HH:mm:ss")

Overview of Scripting · Script Design Fundamentals

• A

  Executing multiple, complex Data Actions on the initial 'Page Load' event.

• B

  Embedding numerous large, high-resolution images directly in the script.

• C

  Using component templates for repeatable sections like headers and footers.

• D

  Placing a large number of components and complex logic within a single, monolithic page.

• E

  Defining variables with a global scope to pass data between pages.

Script Editor Interface · Script Validation

• A

  To check for compliance with company branding guidelines.

• B

  To preview how the script will appear to agents.

• C

  To identify configuration errors, such as missing variables or incorrect action properties.

• D

  To run a live debug session of the script with simulated data.

Actions in Scripts · Consult Transfers

• A

  Scripter.Blind Transfer

• B

  Scripter.Consult Transfer

• C

  Scripter.Transfer to Voicemail

• D

  Scripter.Transfer to Architect Flow

Variables in Scripts · Built-in Variables

• A

  Use the expression Right(Scripter.Agent.name, 10) to get the last 10 characters.

• B

  This is not possible; a custom data action is required to parse the name.

• C

  Combine the Substring and Find expressions: Substring(Scripter.Agent.name, Find(Scripter.Agent.name, " ") + 1)

• D

  Use the expression Split(Scripter.Agent.name, " ")[1] to get the second element of the resulting array.

Actions in Scripts · Data Actions and Script Flow

• A

  A 'Text Input' for the MRN. On the 'Page Load' event, trigger a 'Call Data Action' to the EHR. Use 'Text' components to display the results.

• B

  A 'Text Input' for the MRN and a 'Button' labeled 'Find Patient'. The button's 'On Click' event triggers a 'Call Data Action' to the EHR. The action's success path populates 'Text' components and enables a 'Next Page' button.

• C

  A 'Web Browser' component that loads the EHR's web interface. A 'Text Input' field for the MRN which is passed to the web interface.

• D

  A 'Text Input' for the MRN. Use the input's 'On Change' event to trigger the 'Call Data Action' continuously as the agent types.