In a Quest List Form you can save a form without filling out all required fields. For example, If you create a new contact, default values in the required field are being perceived as filled out. In addition, if a required field is left blank, the form still allows the user to save without entering the data.

A CAML filter that references the currently logged on user using the   extended value <CurrentUserID /> as per the documentation does not work.
The filter returns no rows of data.

The documentation states the following:

The CAML Filter in Quest List View and Quest Calendar View may contain the following extended values:

•  <CurrentUserName /> – This element will be replaced with the display name of the current user. For example: John Smith
•  <CurrentLoginName /> – This element will be replaced with the login name of the current user. For example: domain\johnsmith
•  <CurrentUserID /> – This element will be replaced with the ID of the current user. For example: 1
•  <CurrentUserEmail /> – This element will be replaced with the email address of the current user. For example: johnsmith@domain.com

When configuring the list view web part, an attempt is made to set the Site URL of the list to something like https://www.example.com/, but when save is clicked on, the configurator automatically sets the URL to https:/www.example.com/ (notice one of the slashes is missing), and hence the list cannot be found.   Some users would like to be able to use the absolute path since it is more straight forward.

Custom Fields do not work in the SI List View web part. Take the example from the help file below, try and concatenate any two fields using the syntax provided and there is no output at all.

For example, to display a full name, you can concatenate the first name and last name as follows:

<Field Name=CalculatedFullName Title=Full Name CalculatedValue=&amp;lt;%First Name%&amp;gt; &amp;lt;%Last Name%&amp;gt; />