Maintain TCT mobility basic customising
Last updated
Was this helpful?
Last updated
Was this helpful?
General settings relevant for voice commands and inputs are maintained under the ‘Display Profile Settings’ node. The main classes for frontend data input/output and ITS template/customising generator are assigned in this table against the Display Profile key. These control all the logic related to voice flow behaviour.
See customising node for EWM under Mobile Data Entry > TCT Mobility > Maintain TCT Mobility Basic Customizing.
Different types of voice commands are available for use in any screen field when configuring the voice flow. The predefined voice command types shown below are mandatory for a VoiceDirect implementation and should not be deleted or changed.
The table below defines all the voice commands available for use in any screen field when configuring the voice flow. These can be standard/mandatory vocabulary or new vocabulary defined.
Please note the following voice commands are mandatory and must not be deleted or modified by the customer:
INT_ENTER – This is not an actual voice command but can be used to automatically send an Enter after a screen field voice input.
INT_FCODE – This is not an actual voice command but can be used to define other voice commands available during a field input that pass an exception code in a logical transaction step.
INT_HELP – This is not an actual voice command but can be used to define the spoken feedback when “talkman help” voice command is invoked for any field.
VRESERVE* – These voice commands are reserved for the standard VoiceDirect vocabulary.
VTCTBASE* – These voice commands are reserved for the standard TCT vocabulary.
The table below defines the different voice input conditions available for use in any screen field when configuring the voice flow. A screen field input is only requested to the user if the associated input condition is true.
ALWAYS – the associated screen field is always prompted, even if the focus is not set on that field.
FOCUS – the associated screen field is prompted if the focus is set on that field.
FOCUS_EMPTY – the associated screen field is prompted if the focus is set on that field, and it is empty.
NEXT_INP_FOCUS – the associated screen field is prompted if it is next in the sequence and the focus is set on this field.
ONCE_PER_VAL - the associated screen field is prompted only the first time, or when its value changes. If no value change occurs, the field is no longer prompted.
The table in the image below defines the different voice input methods available for use in any screen field when configuring the voice flow. These enable the system to react correctly based on the expected input type.
Voice input methods starting with Get* only expect a certain data type.
ReadyPrompt can be used when the expected input for a field prompt is just “ready”.
SpeakPrompt only speaks the required prompt and moves on (i.e. no input is required).
The table below defines extra arguments available for Voice for use in any screen field when configuring the voice flow.
The first three arguments CNF_VAL_PRMT_POS, CNF_VAL_PRMT_PRE and CONF_VALUE are required in a voice flow where it is expected for the system to validate a spoken user input, before passing the input to the RF framework.
Arguments MAX_LENGTH and MIN_LENGTH can be used to ensure VoiceDirect is only expecting a certain length range for a particular input field. This helps in minimising input errors.
