Please enable JavaScript to view this site.

CWT Software Configuration Handbook 4.40

Navigation: Appendices > Ticket layout > Variables

Global Input variables

Scroll Prev Top Next More

The global input variables are used to store up to 30 fields that can be used for collecting data to be send to WebOffice

The Global Input 1 is the first entered input, Global Input 2 is the second entered input etc.

Input key 1 maps to input value 1.

Variable

Function

Variable

Function

@v711

Global Input Key 1

@v741

Global Input Value 1

@v712

Global Input Key 2

@v742

Global Input Value 2

@v713

Global Input Key 3

@v743

Global Input Value 3

@v714

Global Input Key 4

@v746

Global Input Value 4

@v715

Global Input Key 5

@v745

Global Input Value 5

@v740

Global Input Key 30

@v770

Global Input Value 30

Using the global variables

to create a list of field to enter, use the input key to specify the label and use the input value to receive the end-user's input

The keys are translated using the translation.xml. E.g.:

<data key="Id1" value="Name"/>
<data key="Id4" value="Phone"/>
<data key="Id5" value="Email"/>

In the ui.xaml the form is build according the example below:

<TFT:TextBox Name=”GeneralInputEmail” KeyValue="Id1" />
<TFT:TextBox Name=”GeneralInputName” KeyValue="Id4" />
<TFT:TextBox Name=”GeneralInputPhone” KeyValue="Id5" />

After an end-user enter their value the data will look like this:

Name        Olle

Phone        0876090015

Email        [email protected]

The ticket variables are populated as follows:

@v711

Name

@v741

Olle

@v712

Phone

@v742

0876090015

@v713

Email

@v743

[email protected]

The ListView (TFT) has an option to display all the fields. Look for GeneralInput....

To display the labels and values use the GeneralInputKeyXLabeland GeneralInputValueXLabel. replace X with the number of the key id. E.g. 1 for Id1.

The Button click function OnGeneralInputDone stores the inserted data

See the User Interface guide for details

User Interface Example:

This example depicts a panel for ID1. The panel name is GeneralInput1Panel, the button moves the end-user to GeneralInput2Panel and so on until the last field is accepted.

When the end-user want to correct anything, they can go through all fields again and the fields will be populated with the saved values.

Note:
If the purchase is aborted, all data will be lost!

<Style BasedOn="{...Style}" def:Name="GeneralInputDoneButtonStyle">
<StyleProperties>
<PropertyStyle Click="OnGeneralInputDone" />
</StyleProperties>
</Style>
<!-- Input PhoneNo ID1 -->
<TFT:Panel MxStyle="{PanelStyle1}" Name="GeneralInput1Panel">
<Controls>
<!-- Input TextBox for PhoneNo ID1 -->
<TFT:TextBox MxStyle="{InputTextboxStyle}" Name="GeneralInput" KeyValue="ID1"
ReferenceTextBox="TicketForwardingPhoneNumberInput" MinimumLength="1"
MaximumLength="15" Characters="+-()0123456789" />
<!-- Button that stores the key-value pair and opens next input panel -->
<TFT:Button MxStyle="{GeneralInputDoneButtonStyle}" Name="CodeDoneButton"
Click="OnPanelOpenAndCloseCurrentPopup" KeyValue="GeneralInput2Panel"/>
<TFT:Button MxStyle="{RejectButtonStyle}"/>
</Controls>
</TFT:Panel>