One request language
Loading indicators, success feedback, and error handling should feel related across the whole page.
Handle Global Server Connect Events
Handle global Server Connect request events on a page so loading, success, and error feedback stay consistent across components.
Introduction
Section titled “Introduction”Global Server Connect events help a page react to request activity without wiring the same loading, success, and error behavior onto every component separately. The point is not to hide what the page is doing. The point is to centralize request feedback so users get one consistent experience when actions start, complete, or fail.
Useful when pages grow
Global events become more valuable as the page uses multiple Server Connect components or actions.
Treat request feedback as a page concern, not only a component concern.
Keep loading, success, and error states understandable from anywhere on the page.
Use global events to remove repeated glue code and duplicated UI reactions.
Still keep important request-specific behavior explicit where it matters.
Design around the request lifecycle
Section titled “Design around the request lifecycle”The real value comes from deciding what the whole page should do at each phase of a request.
Centralize loading state
Section titled “Centralize loading state”If several requests can start from different controls, users should still see one coherent loading story. A shared spinner, disabled region, or top-level status pattern is easier to trust than scattered micro-indicators.
Shared feedback
The page should communicate request activity in a way users can notice immediately.
Separate success from mere completion
Section titled “Separate success from mere completion”A request finishing is not always the same as the page having achieved its goal. Use global completion events carefully, and reserve celebratory success feedback for outcomes that actually matter to the user.
Meaningful success
Not every completed request deserves the same message or emphasis.
Standardize error handling
Section titled “Standardize error handling”Errors should not feel random from one action to another. Decide what belongs in a shared page-level error pattern and what still needs request-specific messaging.
Predictable failure mode
Users recover faster when error feedback follows a recognizable pattern.
Next steps
Section titled “Next steps”Global request events fit naturally with client-side flows and simple UI state because all three help pages behave consistently as interactions multiply.