Record Producer Not Creating Record When Used in Workspace (Submit Button Not Working)

[AakankshaB]

I’m working on a Record Producer that functions perfectly in the standard UI—it's creating records in my target table without any issues. However, when I add the same Record Producer to my Workspace using the Catalog Item component(ui builder) , the Submit button not working. The form loads correctly, but clicking Submit does not create a record, and no errors appear on the screen.

Has anyone faced this issue in Workspace (Zürich)?
Why does the Record Producer behave normally in classic UI but fail to generate a record when used inside Workspace?

Any guidance or recommended workaround would be greatly appreciated.

[yashkamde]

Hello @AakankshaB ,

In Short -> This cannot be done

Opening a Record Producer or Catalog Item in Agent Workspace creates a Service Portal view, which doesn’t integrate with Workspace. Redirects then send users to Native or Portal views, not back to Workspace — leaving agents with a clunky Native record view. If no redirect is needed, it’s fine: the agent can just close the tab. But if you do need a redirect, avoid Record Producers.

This can be solved this by customizing the sc_task form logic so agents stayed inside Agent Workspace, making redirects seamless.

If my response helped mark as helpful and accept the solution.

[Tanushree Maiti]

Please refer this links, see if it helps you:

Solved: action redirect in UI Action for workspace - ServiceNow Community

Solved: How to submit a record producer in Workspace? - ServiceNow Community

[Aditya_hublikar]

Hello @AakankshaB ,

As per my understanding, a Record Producer is mainly designed to be used in the Service Portal and the Native UI. It is a type of Catalog Item that allows users to create records in specific tables using a form-like interface.

I don’t think Record Producers work directly in Workspace, as they are primarily supported for Portal-based experiences. If the requirement is for Workspace, we may need to explore alternative approaches such as custom forms, UI Actions, or Workspace components.

Please correct me if I am wrong.

If this helps you then mark it as helpful and accept as solution.

Regards,

Aditya