Join the #BuildWithBuildAgent Challenge! Get recognized, earn exclusive swag, and inspire the ServiceNow Community with what you can build using Build Agent.  Join the Challenge.

sarah_bioni
ServiceNow Employee
ServiceNow Employee

So you’ve built a workspace in ServiceNow, added a custom form inside your main tab, and everything looks great — until you try to save the form with a required field left blank. You expect a clear error message to pop up in the body, guiding the user to fix it. But instead, the message shows up inside the tab.

It’s confusing, and definitely not the experience you want your users to have.


🤔 What’s the Issue?

When you create a custom tab from scratch and drop a custom form into it, the error/info messages do not appear in the right place (body). Even if you follow the guidance from KB1585120.


The Real Fix

Here’s the trick: don’t build the form from zero.

Instead, duplicate the out-of-the-box “Details” form that comes with the standard workspace setup. Then move it into your custom tab. This way, you inherit all the internal wiring that makes error and info messages work properly.

If you create a new tab and add a form manually, those connections won’t be there, and the messages won’t render as expected.


🛠️ Step-by-Step

  1. Open your workspace in UI Builder.
  2. Locate the OOTB “Details” form used in the default layout.
  3. Duplicate the form (don’t rebuild it from scratch).
  4. Move the duplicated form into your custom tab.
  5. Customize the content as needed — fields, layout, etc.
  6. Test it: leave a required field empty and hit Save. The error message should now appear in the body, just like it should.

💡 Pro Tips

  • Always start from something that works — duplicating OOTB components saves time and avoids hidden config issues.
  • Test validation behavior early, especially when using tabs or nested layouts.
Version history
Last update:
3 weeks ago
Updated by:
Contributors