Notifications
Notifications tell you what YouDesign Models is doing in the background — whether a commit is in progress, a data refresh succeeded, or a board save hit an error. They appear as small toast messages that don't block your work.
Where Notifications Appear
Toasts slide in at the bottom-right of the editor window and stack vertically if multiple arrive close together. Each toast contains:
An icon indicating the notification type (info, success, warning, error)
A short header
A message describing what happened
A close (✕) button
When Notifications Fire
Notifications are system-triggered — you don't send them, but you'll see them in response to your actions or background events. Common sources:
Commit workflow — in-progress, successful, and failed messages for both Commit and Reject actions
Data loads — e.g. "Loading Context Map" → "Context Map loaded successfully" or an error with details
Board saves — on successful save or on error
Explorer data refresh — after a commit or when you re-open a board
Dismissing a Notification
Click the close (✕) button on any toast to dismiss it immediately.
Wait — toasts dismiss themselves after about 4 seconds (some may stay longer when the message is critical).
Types of Notifications
Info
Blue
A background task has started (e.g. a commit is in progress)
Success
Green
An action completed
Warning
Amber/orange
Partial success — e.g. some rows committed, some failed
Error
Red
An action failed
Warning notifications for partial failures include the per-row error list so you know exactly what went wrong.
Scope & Persistence
Toasts are per-browser-session and per-user — another user editing the same board doesn't see your toasts.
Toasts don't persist — once dismissed or timed out, they're gone. There's no in-app notification history log.
For durable alerts that show across sessions, YouDesign Models relies on ServiceNow's own notification mechanisms on the underlying records.
Gotchas
A single action can produce multiple notifications — for example, a commit fires both an "in progress" and a "successful/failed" toast. This is expected.
No read-receipt tracking — dismissing a toast doesn't notify anyone; it's purely local.
Critical errors may linger — some error toasts stay visible longer so you don't miss them. You can still dismiss manually.
Related
Commit — the primary source of commit/reject notifications
Realtime Indicators — a separate, durable visual status system driven by data
Last updated