Contact usDemo App

Logical transaction and step header

Transaction /TCTM/EWM_CFG is provided for customising of the PreBilt EWM framework. This is based on the logical transactions and steps of the standard EWM RF framework.

TCT Configuration – Logical Transaction
TCT Configuration - Steps

The customisation of the voice flow behaviour for any RF screen is done against the corresponding ‘Logical Transaction’ and ‘Logical Step / Screen’ nodes.

Entries in this table can be added manually but can also be automatically generated using the steps described in Initial Generation of ITS Templates and Customising Voice.

Prerequisite

Prior to configuring entries for any logical transaction / step, a separate Display Profile for VoiceDirect must be generated in the standard RF framework.

Please note the ‘Logical Step / Screen’ configuration node is shared with the PreBilt RF customising, therefore not all fields are relevant for voice customising.

Only the ‘Forward Navigation’ field is relevant for voice.

Setting forward navigation

The PreBilt voice engine has a mechanism to determine and call a standard forward navigation function code (ENTER, ENTERF or NEXT) after the last field in the screen is processed. However, if a different function code is needed in a particular screen, it can be assigned using this configuration setting.

Example

In certain scenarios, the differences screen in picking may not return to the main source/destination data screen, even after inputting the required data. In this case, the function code SAVE can force the system to save after the last field is input, before returning to the previous screen to continue picking.

Assigning a Special Forward Navigation FCODE to a Step

Message overrides

The ‘Message Overrides’ node allows for easy customisation of system messages issued during a particular logical transaction / step. The standard message text (which may not be suitable for spoken feedback/instructions) can be replaced with a more appropriate message for voice-guided operations.

The message class or number is not required. Only the exact original message string and the replacement string are necessary, as shown below.

Message Overrides

Example

A message containing a HU variable is replaced by using the ‘&1’ to represent the variable:

Message Override with Variables

Automatically answer yes or no

The ‘Auto Ans.’ column in the ‘Message Overrides’ node can automatically answer YES or NO to a specific message, if required.

Example

To automatically answer YES to “Carry picked goods to destination before leaving?” and “Do you want to send the rest of work back to the pool (split WO)?” from the Pick HU screen, create the customising entries against the step that calls the message (PIHUIN), not against the RFMSG step:

Automatically Answer Yes/No
PreviousMaintain TCT mobility basic customisingNextDetailed screen field customisation

Last updated

Was this helpful?