Issue Summary

JSM Cloud Forms (Proforma): AQL filter using hidden field value works for agents but not for customers on portal forms (parity with JSDCLOUD-15971)

Description

This is functionally the same problem as JSDCLOUD-15971, but occurring in JSM Forms (ProForma) instead of the legacy request form configuration.

In a JSM project using Forms, when an Assets custom field on a Form is configured with an AQL filter that depends on another Form field that is hidden/preset, the behaviour differs between agent and customer views:

• In the agent experience, the Assets field correctly uses the hidden field value for filtering and shows the expected options and is also able to create a ticket 
• In customer experience, the Assets field correctly uses the hidden field value for filtering and shows the expected options, BUT THROWS an ERROR when clicking the submit button

This is similar in nature to JSDCLOUD-15971, where hidden fields cannot be used to drive filtering in the portal, but here the field is visible, and throws an error while creating a ticket

Steps to Reproduce

Attached a screen recording depicting the issue

Expected Results

The portal Form should behave consistently with the agent experience in both cases, wherein it should fail for both agents and customers or work for both

Actual Results

The behaviour is not consistent for agent and customer

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available