Issue Summary

If you have a JSM Form that contains two Assets Fields, and they leverage Filter Work Item Scope (AQL) fields to reference each other (so that the same value cannot be picked for both fields), within Agent view on the Form the filter doesn't seem to work at all. But the same configuration does work within Agent view not on a Form (just adding the fields to a screen). Within the JSM Portal different results can occur such as the entire Form submission becoming unresponsive and the screen on the browser quitting unexpectedly or the field will just not save at all.

Steps to Reproduce

1. Create two Assets fields that reference the same schema type and Filter scope (AQL) such as "objectType = "People"
2. Update the Filter work item scope (AQL) to filter out what the other field has referenced. For example using something like this: objectId NOT IN (${customfield_xxxxx.id${0}}), of course replacing the xxxxx with ID of the partner field.
3. Add these fields to a JSM Form that is used as a Request Type on the Portal.
4. Also add these fields to another screen for a different Request Type that can be created internally within Agent view not on a Form.
5. Attempt to open the form that is on the Portal, select a value for the first field.
6. Notice the value doesn't save
7. Select the second field and notice there is no filtering.
8. Go back into Agent view and create the other request type that has the fields not on a JSM Form.
9. Select a value in the first field and notice it will save.
10. Select the second field and notice it is filtered correctly

Expected Results

The Filter Work Item Scope (AQL) should function in JSM Forms.

Actual Results

Within Agent view on the Form the filter doesn't seem to work at all. But the same configuration does work within Agent view not on a Form (just adding the fields to a screen). Within the JSM Portal different results can occur such as the entire Form submission becoming unresponsive and the screen on the browser quitting unexpectedly or the field will just not save at all.

Workaround

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