Data Policy Exception when submitting Service Catalog form without required fields - Known Error

Data Policy Exception when submitting Service Catalog form without required fields Description If a Service Catalog form is created for incidents with numerous fields, an error message stating "Data Policy Exception: The following fields are mandatory: Resolution code, Close notes" may be displayed upon submission. This error message may appear even if the fields mentioned are not present on the form.

There are no Client Scripts, Business rules, or data policies that could cause the error mentioned. Additionally, there are no resolution code or close notes in the record producer. The issue is caused by a variable with the "map to field" option selected. Even though it is not a mandatory field, a multiple-choice option with a radio button for selection is presented. The problem is that "None" is part of the list, but it is not a valid selection, leading to the error message.

Steps to Reproduce

Create or open an existing record producer Add a new variable Turn on "Map to Field" and select type "multiple choice" Select any field, like Active on the Incident table. (you may need to save without map to field first, then go back and edit the record to see the field options) Note that Mandatory need not be set to true Put a question name/question. For example "Multiple choice" question, with name "multiple-choice" In Type specification - ensure 'include none' is ticked. Add some question choices Go back to the record producer, and click on "try it". In the form, fill in the field for any other field as required, but leave the the multiple-choice as --None-- Click Submit The session will move to another page and will show: Record not found Data Policy Exception: The following fields are mandatory: Resolution code, Close notes Workaround This is expected behavior and by design in all currently supported releases.

The situation described is functioning as intended. The issue only arises for the Active field within the Incident field, and this is due to a Business Rule known as "task closer" . This rule sets the state to "Closed" when the "Active" field is set to false. As "Closed" is a specific state, the Incident table has a data policy in place which mandates the inclusion of a Resolution code and Close notes. This is the reason for the error.