UX Openings
Introduction:
UX openings help control how users interact with the system, especially in:
- New (creation) screens
- Properties / Information panels
They guide users while entering or updating data by controlling what they can see, edit, and select.
With UX openings, the system can:
- Prevent incorrect or unwanted entries
- Show only relevant fields
- Lock fields when changes are not allowed
- Provide instant messages or warnings before saving
These capabilities work in the background to keep information accurate and aligned with business requirements.
In simple terms: users are guided step-by-step, mistakes are reduced, and data stays clean and reliable.
The screenshots below demonstrate how the system guides users by:
- Displaying warning messages for invalid inputs (without blocking the save action)
- Restricting editing through read-only fields
Scenarios Covered:
This framework is organized into four core scenarios.
Each has its own detailed documentation page with EKL scripts, examples, explanations, screenshots, and demo videos.
| Scenario | What It Ensures | Explore Details |
|---|---|---|
| 1. Read‑Only Enforcement | Locks attributes once populated; attribute conditionally locked. | Read-Only Enforcement |
| 2. Authorized Values | Restricts inputs to predefined lists. | Authorized Values |
| 3. Input Validation & Feedback | Blocks empty/invalid entries; warns on non‑blocking issues. | Input Validation & Feedback |
| 4. Conditional Visibility | Dynamically shows/hides attributes | Conditional Visibility |
Technical Context:
- Version: 2026x GA (On‑Premise) / HotFix 1.32 (Cloud)
- Execution Context: Server
- Trigger Points: Save in dialogs, Information tab, Instance tab, and property value changes in the Properties page
- Licenses Required: TXO, MFN / MGA / RME
Disclaimer:
Licenses mentioned above are as per 2026x documentation.
How the System Works
To make this easier to understand, let’s look at what happens from a user’s perspective:
1. During Creation
- User clicks New / Insert New
- The system prepares the screen (default values, visibility rules)
- As the user enters data:
- Inputs are validated
- Allowed values are enforced
- Messages guide the user
2. During Modification
- User opens the Properties / Information panel
- The system adjusts what can be seen or edited
- When values are changed:
- Validation runs instantly
- Fields may become read-only
- Errors or warnings are displayed
How this openings Trigger:
This diagram shows how user actions automatically trigger system logic to apply validation, control visibility, and enforce rules during creation and modification.
Opening IDs and Their Trigger Conditions:
Opening ID | Description | For more Information, see... |
compute_new_init | Fired when New panel is build | |
ux_init_new_modify | Fired when the user modifies an attribute in New | |
compute_edit_properties_init | Fired when Properties experience is built | |
ux_init_edit_properties_modify | Fired when the user modifies an attribute in Properties |
Limitations:
- Direct table edits in UI → BLs are not triggered when values are changed directly in spreadsheet view.
- Multiple row selection → BLs do not apply when modifying several rows at once.
- Native client → BLs have no effect; changes are not visible in the native client.
