Unable to Submit a Service Catalog Item with a Checkbox Variable Through Virtual Agent in ServiceNow

[rachamaa]

Hi Community,

I am facing an issue while trying to submit a Service Catalog Item through Virtual Agent in ServiceNow.

I have a catalog item that contains a Checkbox variable. When I try to submit this catalog item using the Topic Block in Virtual Agent, the submission is not working as expected.

However, other catalog items that do not contain a checkbox variable are being submitted successfully through the same Virtual Agent flow.

I suspect the issue might be related to how the checkbox variable is handled or passed during the catalog item submission process.

My questions are:

1. Is there any specific configuration required to handle checkbox variables when submitting a catalog item through Virtual Agent?
2. Does the checkbox variable require any special handling in the Topic Block or the catalog item submission flow?
3. Is there any known limitation or workaround for submitting catalog items containing checkbox variables through Virtual Agent?

Any suggestions, guidance, or examples of how to handle checkbox variables in Virtual Agent would be greatly appreciated.

Thank you in advance for your help!

[vaishali231]

Hey @rachamaa 

This could be related to how the checkbox variable is handled in Virtual Agent. Please check whether the checkbox response is captured correctly in the Topic Block and whether any client scripts or UI policies are affecting the submission.

As a workaround, you can try using a Yes/No variable instead of a checkbox, if it meets your requirement.

Also, check the Virtual Agent logs to identify the cause of the failure.

Are you using the standard NLU-powered or Now LLM-powered catalog request flow?

*******************************************************************************************************************************

If this response helps, please mark it as Accept as Solution and Helpful.

Doing so helps others in the community and encourages me to keep contributing.

Regards

Vaishali Singh
Linkedin - https://www.linkedin.com/in/vaishali-singh-2273361bb

[VJ_Srivastava]

Hello @rachamaa,

From a platform architecture perspective, this issue highlights the fundamental challenge of "Omnichannel Catalog Design." You are experiencing the friction that occurs when a data model designed for a 2D web form (the Service Portal) is forced into a linear, conversational interface (Virtual Agent).

In standard web architecture, a checkbox is a visual representation of a boolean state. However, in a conversational API, an explicit confirmation is required to advance the node. When the VA engine tries to dynamically render a catalog item, standalone checkboxes introduce ambiguity in the API payload—does skipping the question mean "false," or does it mean the user didn't answer?

To build a scalable, upgrade-safe architecture, your catalog design must be interface-agnostic. I strongly advise standardizing your development guidelines to deprecate standalone checkboxes across your catalog. Transitioning to explicit Select Box or Yes/No Choice variables ensures deterministic data payloads. This guarantees that your catalog items will render and submit perfectly whether they are accessed via the Service Portal, the Now Mobile App, Virtual Agent, or external API integrations, drastically reducing your technical debt.

[NehaG8791370651]

Hi @rachamaa,

This is a well-known quirk with the Conversational Catalog API that powers the Virtual Agent (VA) Topic Blocks. The issue stems from how the VA engine attempts to translate web-based boolean inputs (checkboxes) into a linear conversational flow.

When a standard Checkbox variable is passed into the "Submit Catalog Item" topic block, VA often fails to parse the null or undefined state of the checkbox, causing the background payload submission to crash.

Here is exactly how to handle this and get your item working in Virtual Agent:

1.Group Checkboxes under a Label Variable: 1 min.

Virtual Agent cannot easily process standalone checkboxes. If you have multiple checkboxes, you must create a variable of type Label, and place your Checkbox variables immediately underneath it. VA recognizes this specific structure and automatically translates the grouped checkboxes into a conversational "Multi-select" prompt for the user.

2.Set a Default Value: 1 min.

If a checkbox is left completely untouched in VA, it sometimes passes a null value instead of false, breaking the backend API. Open your Checkbox variable dictionary and ensure the Default Value is explicitly set to false.

3.The Select Box Workaround (Recommended): 2 mins.

If this is just a single, standalone Yes/No question, the most robust technical workaround is to change the variable type from Checkbox to Select Box (with choices: Yes/No) or Multiple Choice. VA handles Choice lists flawlessly, presenting them as clickable buttons in the chat window, which completely eliminates the boolean parsing errors.