Working with Forms
📄️ Form Designer
The Form Designer is a graphical, drag-and-drop interface within tSM that allows users to build and configure forms for any entity — such as Tickets, Customers, Orders, or custom modules. It empowers both technical and non-technical users to manage UI layouts without code, while still supporting advanced configurations under the hood.
📄️ Widgets Overview
This page introduces the building blocks used in tSM Form Designer — including Data Components, Layout Components, and tSM Widgets — and how they are configured for visual design, data persistence, and advanced behaviors.
📄️ Layout Configuration
Layout configuration in tSM defines how widgets are grouped, arranged, and visually rendered in a form. Layout is expressed in JSON Schema via the layout field and is enhanced with tSM-specific widget and config extensions.
📄️ LOVs & Listings
LOVs (Lists of Values) and Listings are data-driven components in tSM that allow users to select or view records from other entities. They are critical for enabling relationships across modules, such as assigning users, linking customers, or displaying related tickets.
📄️ Common Widget Settings
This chapter describes how to configure validation rules for widget inputs in TSM.
📄️ Success / Error Actions
These actions are used in ButtonComponent (via successActions, errorActions inputs) to trigger specific side effects or state changes after a button operation completes (either successfully or with an error).
🗃️ Form Effects
9 items
🗃️ Advanced Use Cases
6 items
📄️ Runtime Debugger
The Fluent Form Runtime Debugger examines a rendered form with its current data and context. Use it when a field has an unexpected value or validation state, an effect changes another field, or the form cannot be submitted. The Form Logic Editor shows the configured relationships; the runtime debugger shows what happened in this form instance.