Virtual Agent: Using custom field in com.glide.cs.portal_url_mapping._default. system property doesn't workIssue When using a custom field in the value for the com.glide.cs.portal_url_mapping._default.* system property, Virtual Agent hangs and the conversation does not return the search results.ReleasePre-Rome releasesCauseThis is due to the use of a custom field. When using the com.glide.cs.portal_url_mapping._default.* system property with a custom field, the custom field is not being used in the URL that is generated.ResolutionThis will be expected behavior. The only supported fields are data.sys_id and data.table_name. This is a limitation on the server side and cannot be changed.