Learn how to build the Incident & Maintenance Hub for the Smart Vendor and Procurement System using redSling UI Builder. This detailed tutorial follows the interface-building process from a blank page to a structured screen for searching incident records, reviewing existing issues, and entering a new incident or maintenance requirement.
The module begins with the main page structure. Use the builder’s column-based layout to create separate areas for application navigation and incident-management content. Configure the width and height of each column, then adjust the padding and spacing between the navigation and the main workspace. This establishes the foundation for the page header, search controls, incident table, and reporting form.
Next, create the page header with the title “Incident & Maintenance Hub” and supporting text explaining the purpose of the screen. Position the heading and description on the left and the “Add Issue” button on the right. Refine the dimensions and alignment of the header components so the text and action remain balanced.
Configure the Add Issue button with a green visual treatment to identify it as the primary page action. Adjust its width, height, spacing, and styling through the properties panel before continuing to the search area.
The tutorial then covers building a search section beneath the header. Add input and selection components from the component library and arrange them horizontally within the available space. Position a Search button alongside the filter controls, and refine each component’s dimensions and spacing to create a consistent row.
This part of the walkthrough demonstrates how to select controls, place them into individual columns, and configure their properties directly within the builder. Review the space between the inputs, selections, and Search action so the controls remain clearly separated and aligned between the header and the incident listing.
Continue by adding the incident data table. Place the table within the main content area, open its configuration, and define the fields needed to represent the incident and maintenance records. Adjust the table container’s dimensions so it fits the page and aligns with the sections above it.
Configure sample records to review the table structure and apply an orange header treatment to distinguish the column headings from the data. Check the spacing and presentation of the records, then refine the table width and height to keep the information readable. The listing provides the central area for reviewing existing incidents before moving into the reporting form.
The next section introduces “Report New Incident.” Add supporting text explaining that the form is used to report an issue or maintenance requirement, then begin arranging the information fields in a logical sequence.
Start with Incident Title, giving the input enough width for a meaningful summary of the issue. Add Asset ID and Category together so the user can associate the incident with an asset and classify the type of issue. Follow these with Priority and Location, keeping the fields aligned with the row above.
This arrangement creates a clear progression through the form: identify the incident, associate it with an asset, classify the issue, indicate its urgency, and specify where it occurred.
Next, add the “Detail Description” field using a larger text area. Configure its width, height, and surrounding spacing to provide enough room for a fuller explanation of the incident. Position it beneath the basic information so users can enter the key details first and then describe the issue in context.
Continue with the “Expected Resolution” field below the incident description. Use a larger input area to capture the requester’s expected outcome or additional information about how the issue should be addressed. Refine its dimensions and positioning to maintain consistent alignment with the rest of the form.
The tutorial then covers the form actions. Add a Cancel action and group it with the primary submission action at the bottom of the form. Give the primary action a highlighted treatment and adjust the buttons’ dimensions and spacing so both controls are easy to locate after the user completes the fields.
Review the form’s visual consistency using the available typography, decoration, border, background, dimension, and spacing properties. Select and refine individual components while preserving the surrounding page structure.
Finish by reviewing the complete Incident & Maintenance Hub from top to bottom. Check the relationship between the page heading, Add Issue action, search controls, incident table, and Report New Incident form. Confirm that related fields are grouped clearly and that the page maintains consistent spacing and alignment.
By the end of this module, you’ll understand how to assemble an incident-management interface using columns, inputs, selection controls, tables, text areas, and buttons in redSling UI Builder. The walkthrough focuses on constructing and styling the screen that supports incident search, record review, and new issue reporting.
What you’ll learn