View Source

After adding the controls in the design area, you can set the properties for the controls/elements. For example, setting the properties for the following Data elements.

Screenpop Data (Starting Page):
- First_Name: First Name of the customer
- Last_name: Last Name of the customer
Script Data (Email Consent page):
- sms_const: Text box for adding the mobile number of the customer.
- email_const Text box for adding the email ID of the customer.
- cell_const: Text box for adding the mobile number of the customer.
- cust_cont_yes: Radio button for selecting the Yes button.
- cust_cont_no: Radio button for selecting the Yes button.
Contact Data (Starting Page):
- clientid: Label for adding the customer identification Number from the Contact details fields.

The fields that you created on the Data page appear in the Properties tab when you select the elements/controls in the Design tab.

Settings Properties

The starting page contains four elements/controls: Customer name (first and last name), agent name (first and last name), client ID (contact field), and radio buttons (yes or no). The controls are highlighted in the image below.
Admin Guides (U17, LV19, and Fall 23) > .element properties vU17 > properties.png

To set the properties:

From the Starting page, select the FIRST_NAME label.
Click the Properties tab.
From the Fields drop-down list, select FIRST_NAME.
Follow the same steps and set the LAST_NAME, agent_fname, agent_lname, and clientID elements.
For the radio buttons, select Yes, and from the Properties tab, select the field as cust_available and value as 1. Set the same field for No and the value as 2.
As the radio button is script data, an event must be triggered when selecting this option. For detailed information on setting an event for the radio button, see Setting Events.

Setting Events

Events are added to controls, where you want a certain condition to occur when a control is triggered. For example, the request changes must move to a different page or information when you click the control. For example, create events for the button on the starting page, that is the Yes or No buttons. The event enables you to move to the next page when you trigger these buttons.

You can manually add code to add additional functionality to the script. For more information, see Manually Adding a Code.

The actions that are targeted when you trigger the Yes and No buttons are explained below:

Control

Action

Yes

The action shows more information on the same page.

For this action, the code is modified in the source code area.

No

The action takes you to the call closing page.

To set the event to Yes :

From the Design area, on the Starting page, select Yes.
Click Events.
From the Events drop-down list, select onchange.
From the Function drop-down list, select lvcore.checkActions from the Script Core.
The code is modified to add the highlighted change in the trigger.

To set the event to No:

From the Design area, on the Starting page, select No.
Click Events.
From the Events drop-down list, select onclick.
From the Function drop-down list, from the Script Core drop-down list select lvcore.nextNode.
The Parameter is updated to PageName.
For the Param Type, select Pages and then select Value to the required page from the list.