4.4 Maintenance Summary Screen

This topic provides information about the Maintenance Summary screen used to view, manage, and update summary details related to maintenance activities within the system.

The maintenance summary screen pattern is used when you need a maintenance RSO flow. Each maintenance RSO Screen contains of different stages with each stage containing its own Data Segment.
  1. Step 1: Component Creation

    Creates the base definition of the maintenance summary screen.

    What you do on this screen:

    • Select pattern type as Maintenance Summary Screen.
    • Select product type.
    • Enter name (technical identifier) and label (display name).

    Figure 4-11 Component Creation


    Description of Figure 4-11 follows
    Description of "Figure 4-11 Component Creation"

  2. Step 2: Endpoint Configuration

    Links the design to its runtime data source and defines maintenance-specific component setup.

    What you do on this screen:

    • Endpoint: select the service/data endpoint used to fetch and maintain records.
    • Screen orientation: choose how the maintenance layout is arranged (for example horizontal).

    Figure 4-12 Endpoint Configuration


    Description of Figure 4-12 follows
    Description of "Figure 4-12 Endpoint Configuration"

    Maintenance components

    • Component name: technical identifier for the maintenance component.
    • DTO object: select the DTO/entity used for data binding.
    • Label: display name for the maintenance component.
    • Add components: add additional maintenance component rows if the design requires more than one component.
    • Delete/remove: remove a maintenance component row if not needed.

    Figure 4-13 Maintenance components


    Description of Figure 4-13 follows
    Description of "Figure 4-13 Maintenance components"

  3. Step 3: Template Design

    Builds and refines the maintenance summary UI in the designer.

    What you typically do in the designer for maintenance summary:

    • Configure the display fields for each stage.
    • Add search/criteria fields (if not handled entirely in configuration/summary steps).
    • Define action buttons (for example create, edit, view, delete, drill-down).
    • Configure navigation to a related detail screen (if your implementation supports it).
    • Apply field-level behaviour and validations where required.

    Figure 4-14 Template Design


    Description of Figure 4-14 follows
    Description of "Figure 4-14 Template Design"

  4. Step 4: Summary Screen

    Final review before saving.

    What you do on this screen (as seen in the summary page screenshot):

    • Endpoint: Verify the selected endpoint.
    • Query Params (required): Enter required query parameters expected by the endpoint.
    • Filter configurations: Enable filter/search configuration using the toggle.
    • Template configurations: Review or adjust template-level settings.
    • Save: Save the final design.

      Figure 4-15 Summary


      Description of Figure 4-15 follows
      Description of "Figure 4-15 Summary"

Parent topic: UI Design Patterns Creation