The Config Team Ltd
Contact usDemo App
PreBiltâ„¢ for EWM
PreBiltâ„¢ for EWM
  • PreBilt for EWM
    • Overview
    • Functionality
    • Frequently asked questions
    • Release notes
      • v4.13 release notes
      • v4.12 release notes
  • Installation
    • Minimum requirements
    • Prerequisites and assumptions
    • Backend installation
    • Frontend installation
    • UI deployment
  • Configuration Guide
    • EWM RFUI requirements
    • Initial generation of EWM ITS screen templates
    • Overview screen of technical information
    • BC sets
    • Customising the screen layout
      • Logical Transactions and Step Header
      • Detailed screen fields customisation
        • Replacement field labels
        • Field type
        • Toggling a drop-down list
        • Hiding field borders
        • Hiding a field from display
        • Hiding a field from display when empty
        • Making a field read-only
        • Setting the display row for a parameter
        • Setting the visual length of a parameter
        • Setting the position of a parameter on the row
        • Maintaining table types for step-loop table functionality
        • Assigning field roles for table types
        • Maintaining a hint text
        • Defaulting a parameter value
        • Setting a parameter label's font style, size and colour
        • Setting a field value font style, size and colour
        • Adding a new screen field
        • Enhanced UoM selection
        • Defining Extra Screen Elements
        • Function code overrides
        • Menu extras
        • Function code extras
        • Exception code extras
        • Extra element types
        • Voice Fields
    • Translations
      • Downloading translations
      • Transforming the data
      • Uploading translations
    • Configuring PreBilt features
      • Communication Hub
      • Gamification
        • Competitions
        • Challenges
        • Game Monitoring
      • Voice
        • EWM RFUI requirements for Voice
        • Functional scope
        • Initial generation of ITS templates and customising for voice
        • Overview screen of technical information
        • Customising the voice flow for a screen
          • Maintain basic configuration
          • Maintain TCT mobility basic customising
          • Logical transaction and step header
          • Detailed screen field customisation
        • Master data
      • Analytics
        • Installation
        • Embedding Analytics into PreBilt
      • Unified Search Configuration
        • Installation
      • Image Capture
  • Using PreBilt
    • Screen elements
    • Process steps
    • Validation messages and troubleshooting
    • Operator messaging
    • Gamification
    • Troubleshooting
Powered by GitBook

Help

  • Can't find what you're looking for? E-mail us.

© The Config Team 1994 - Present Day

On this page
  • Step-Loop (SL) table
  • Full table view
  • Object list view

Was this helpful?

  1. Configuration Guide
  2. Customising the screen layout
  3. Detailed screen fields customisation

Maintaining table types for step-loop table functionality

PreviousSetting the position of a parameter on the rowNextAssigning field roles for table types

Last updated 6 months ago

Was this helpful?

To improve the usability of step-loop tables within PreBilt, table types are used to control how the table is presented within the UI. The table type functionality addresses the challenge of displaying multiple fields within a single row, particularly on mobile devices with limited screen space.

The table type displayed in PreBilt can be controlled either through configuration in transaction /TCTM/EWM_CUST, which manages table types at the display profile level, or in transaction /TCTM/EWM_CFG, where it can be maintained at logical step/field level. This configuration allows for flexible control data presentation based on the specific requirements.

Note

Maintaining table type at screen field level will take priority over anything set at display profile level.

Step-Loop (SL) table

The step-loop table supports Popin functionality, which adjusts the display based on available screen space. If the screen is resized or has limited space, fields will dynamically grow "downwards" into a vertical stack, ensuring no truncation occurs.

In addition to the Step-Loop (SL) table, there are two other table types available for displaying data, each with unique characteristics:

Full table view

This displays all rows at once, removing the need for navigation buttons like "PAGE UP" or "PAGE DOWN."

Fields in this view are read-only, so users cannot edit data.

Example

Table type "TA" (full table) is set for transaction INSTBI, step INSTSB.

Object list view

This displays data in a simplified, vertically growing list format without column headers.

Like the full table view, the object list is non-editable, for scenarios where only viewing is required.

Example

Table type "OL" (object list) is set for transaction INSTBI, step INSTSB.

Maintaining table type for Display Profile
Maintaining table type for Logical Transaction Ste
Popin functionality
Table type configuration
Full table
Table type configuration
Object List