While there are many functions, here is a handy list of properties that should be used whenever a [color=blue]query API[/color] is used to fetch results.

• Empty – Informs whether the result set (of multiple items) is empty. The common mistake is to use Count property just to understand if there are rows that match the query. Do not use Count property if we only want to know if there are rows that match our query in the data set. Relational query performance often improves if you u...

Access the class attributes using the properties instead of getter methods. For example, request.getCookies() could be accessed directly as request.Cookies. This reduces instances of null pointer exceptions. When accessing properties, the .(dot) notation is null safe.

Do not use

new java.util.Date

(OR )

java.util.Calendar.getInstance().Time
Instead use gw.api.util.DateUtil.CurrentDate (or)
java.util.Date.CurrentDate
INCORRECT USAGE :
var currentDate = new java.util.Date() (or)
var currentDate1 = java.util.Calendar.getInstance().Time
CORRECT USAGE :
var currentDate = java.util.Date.CurrentDate // Note that “new” is not used here
var currentDate = gw.api.util.DateUtil.currentDate()

java.util.Date is a Java in-built ...