Service Portal Record Producer "400 Bad Request" Error on Submit

Overview

This article describes an issue customers can run into when using a record producer on the Service Portal.

Error seen when submitting a record producer

After pressing Submit, the record producer gets stuck on Submitting... See below:

The Console shows a 400 bad request error, along with an error message for the object. See below:

Most Probable Cause

This issue is seen when any of the variables in the item is set to Mandatory through the variable record, instead of using a UI Policy or the users do not pass the READ ACLs on item_option_new table.

In Jakarta, the SC Catalog Item widget will use the GlideRecordSecure API, which will require modification or ACL creation if you have any variables set directly to 'mandatory'.

Solution

To solve this issue, try one of the following things:

• Uncheck the Mandatory checkbox on all variables on the item, and use a UI Policy instead to make the variables mandatory.

https://docs.servicenow.com/bundle/jakarta-servicenow-platform/page/administer/form-administration/task/t_CreateAUIPolicy.html

• Review READ ACLs on the item_option_new table, and confirm that the users can pass the ACLs. To test, you can create an open-ended READ ACL for all the fields in item_option_new by using a wildcard. See below: