# Logical Transactions and Step Header Logical Transactions and Step Header Transaction */TCTM/EWM\_CFG* is provided within the namespace to aid with customising the EWM ITS screens displayed on the client.

Using the ‘Logical Transaction’ and ‘Screen Fields’ nodes allows for further customisation of the information and display layout on the client. Entries in this table can be created manually, or automatically generated, using the ITS Template Generator. Additional configuration fields enable enhanced configuration of each logical step: ### Focus handling When active, the configuration setting will override any automatic cursor setting on the screen. There are two additional options provided: * N - “No focus at all” means no soft keyboard display, so a field must be selected to make an entry. * K - “Focus but suppress keyboard” is beneficial where users are expected to make entries with a scan gun. Focus will be maintained, allowing the user to scan/input without the soft keyboard displaying, but the soft keyboard will pop up if a field is touched on screen. ### Swipe carousel location {% embed url="" %} This allows positioning (where applicable, such as in picking where there are multiple tasks) of the Swipe Carousel. There are 3 options: * T - top. * B - bottom. * Null - swipe carousel is not displayed. * N - disable swipe functionality. ### Setting forward navigation {% embed url="" %} This field allows the standard choice for forward navigation on the display field to be overridden. Standard EWM will consider the functions to define the action of the forward button in the following order: ENTER > ENTERF > NEXT. The first function code in the sequence, which is valid for the step, will be used unless the choice is overridden by this configuration setting. ### Setting backward navigation {% embed url="" %} This field allows the standard choice for back navigation on the display field to be overridden. Standard EWM will consider the functions to define the action of the back button in the following order: BACK > BACKF > UPDBCK. The first function code in the sequence, which is valid for the step, will be used unless the choice is overridden by this configuration setting. Should the back button be missing, in cases where the standard ITS screen uses the function UPDBACK, the following configuration can be maintained to resolve this. In *SPRO*, navigate to the EWM customising node `Mobile Data Entry > Radio Frequency (RF) Framework > Define Steps in Logical Transactions`. Maintain the configuration for function UPDBACK.

Standard configuration adding Back button functionality

## Useful tips for defining a screen layout {% embed url="" %} ### Setting a replacement step/screen title {% embed url="" %} Text entered in this field will display as a header title on the corresponding screen. {% hint style="info" %} **Example** A title of ‘Stock by Bin’ is maintained for the Log. Transaction *INSTBI*, step INSTBS: {% endhint %}

TCT Configuration - Screen/Step title change

--- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.theconfigteam.com/prebilt-ewm/configuration-guide/customising-the-screen-layout/logical-transactions-and-step-header.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.