This update makes day-to-day work in the Nebulas portal a little smoother: when you're confirming a change or updating a form, you'll now see exact, plain-language messages if a confirmation entry doesn't match the original or if you try to save without making any actual change, so you can correct the issue right away instead of facing a generic error or an unexplained failed submission.

Specific messages for confirmation fields and unchanged forms

When you fill in a form that asks you to confirm an entry (for example, retyping a value to verify it), the portal now shows a 'Confirmation does not match' message if what you typed doesn't match the original entry, instead of a generic error. Likewise, if you try to save a form without actually changing anything, you'll see 'At least one change is required', so you know immediately why nothing went through.

  • Confirmation fields that don't match the original entry now show a 'Confirmation does not match' message instead of a generic error.
  • Attempting to save a form with no changes now shows an 'At least one change is required' message, clarifying why nothing was submitted.

01

What changes for you

If you're updating information that requires a double-entry confirmation, you no longer have to guess why saving failed: the message tells you plainly that your confirmation entry doesn't match the original. And if you accidentally try to save a form without changing anything, the portal now tells you clearly instead of leaving you unsure what happened.

02

Why it matters

A generic error message forces you to check every field to figure out what went wrong, which wastes time. With precise feedback, you can spot and fix the issue in seconds, meaning fewer failed attempts and less need to contact support just to understand why a form won't save.